May 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3468) Node's external link values are not persisted after exporting site

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3468?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3468. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done Merged to master https://github.com/gatein/gatein-portal/commit/86687984fb2c92b2adc3eebf17... > Node's external link values are not persisted after exporting site > ------------------------------------------------------------------ > > Key: GTNPORTAL-3468 > URL: https://issues.jboss.org/browse/GTNPORTAL-3468 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > > Description of problem: > According to: https://bugzilla.redhat.com/show_bug.cgi?id=1032937 > When you create external link for a node in navigation.xml, after import/export it is not persisted. > Steps to Reproduce: > 1. Export site > 2. Enter some property values into navigation.xml inside <node> element: > {code:xml} > <properties> > <entry key="externalURI">http://google.com</entry> > <entry key="openInNewWindow">true</entry> > </properties> > {code} > 3. Import site into portal > 4. When you are exporting the same site again - property values are not persisted. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3467) Add navigation node properties to gatein_objects XSD

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3467?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3467. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done Merged to master https://github.com/gatein/gatein-portal/commit/d5d3e47147e1d70b68e13d6a4f... and the new XSD was published http://www.gatein.org/xml/ns/gatein_objects_1_7 > Add navigation node properties to gatein_objects XSD > ---------------------------------------------------- > > Key: GTNPORTAL-3467 > URL: https://issues.jboss.org/browse/GTNPORTAL-3467 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > > Properties like the following should be possible on navigation nodes: > {code:xml} > <properties> > <entry key="externalURI">http://google.com</entry> > <entry key="openInNewWindow">true</entry> > </properties> > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3456) Update copyright text to use 2014 year

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3456?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3456: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1089944|https://bugzilla.redhat.com/show_bug.cgi?id=1089944] from POST to MODIFIED > Update copyright text to use 2014 year > -------------------------------------- > > Key: GTNPORTAL-3456 > URL: https://issues.jboss.org/browse/GTNPORTAL-3456 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3459) Permissions Move Apps, Move Containers are not inherited to a newly created page

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3459?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3459: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1090875|https://bugzilla.redhat.com/show_bug.cgi?id=1090875] from ASSIGNED to CLOSED > Permissions Move Apps, Move Containers are not inherited to a newly created page > --------------------------------------------------------------------------------- > > Key: GTNPORTAL-3459 > URL: https://issues.jboss.org/browse/GTNPORTAL-3459 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.8.0.Final > Reporter: Peter Palaga > Assignee: Peter Palaga > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1090875 > When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. > Steps to reproduce: > 1. Create new portal site, set some permissions > 2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3470?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3470: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094154 > Make permission defaults in page creation forms consistent > ---------------------------------------------------------- > > Key: GTNPORTAL-3470 > URL: https://issues.jboss.org/browse/GTNPORTAL-3470 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions. > The page creation forms for which this applies: > I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page > II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page > III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page > For each of them, the defaults should be set as follows: > (1) For portal pages the access and edit permissions should be taken from the parent site. > (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service. > (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used. > In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3459) Permissions Move Apps, Move Containers are not inherited to a newly created page

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3459?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3459: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Won't Fix This cannot be fixed as suggested in the description because there already are defaults applied from the selected page template. I have created GTNPORTAL-3470 to fix some small inconsistencies in all page creation forms. > Permissions Move Apps, Move Containers are not inherited to a newly created page > --------------------------------------------------------------------------------- > > Key: GTNPORTAL-3459 > URL: https://issues.jboss.org/browse/GTNPORTAL-3459 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.8.0.Final > Reporter: Peter Palaga > Assignee: Peter Palaga > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1090875 > When creating new portal site, there are 4 permissions to set - Access, Edit, Move Apps, Move Containers. When I create new portal and set some permissions, then create new page in this portal, the owner of the new page is the newly created portal, and Access and Edit permissions are inherited or "copied" into the permissions of the new page. But Move Apps, Move Containers permissions are set to "Everyone". This permissions should probably also inherit the permissions from the owning portal. > Steps to reproduce: > 1. Create new portal site, set some permissions > 2. Go to this new portal site, create new page. On the 3rd step of creating the page, in View Page Properties, Permissions tab are inherited only Access and Edit permissions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNWCM-33) Localize aux tags for WCM Editor portlet

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNWCM-33?page=com.atlassian.jira.plugin.... ] Lucas Ponce closed GTNWCM-33. ----------------------------- Fix Version/s: 2.x Resolution: Done Support for english and spanish. Also code is prepared to add new languages adding new *.properties files. > Localize aux tags for WCM Editor portlet > ---------------------------------------- > > Key: GTNWCM-33 > URL: https://issues.jboss.org/browse/GTNWCM-33 > Project: GateIn WCM > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 2.x > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3470?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3470: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/850 > Make permission defaults in page creation forms consistent > ---------------------------------------------------------- > > Key: GTNPORTAL-3470 > URL: https://issues.jboss.org/browse/GTNPORTAL-3470 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions. > The page creation forms for which this applies: > I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page > II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page > III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page > For each of them, the defaults should be set as follows: > (1) For portal pages the access and edit permissions should be taken from the parent site. > (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service. > (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used. > In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3470) Make permission defaults in page creation forms consistent

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3470: --------------------------------------- Summary: Make permission defaults in page creation forms consistent Key: GTNPORTAL-3470 URL: https://issues.jboss.org/browse/GTNPORTAL-3470 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Peter Palaga Assignee: Peter Palaga This is a followup of the rejected GTNPORTAL-3459 which asked for applying move*Permission defaults from parent site. The present aim is to ensure for all page creation forms, that they use consistent defaults for all kinds of permissions. The page creation forms for which this applies: I. Page Creation Wizard accessible via Toolbar > Site Editor > Add New Page II. New Page accessible via Toolbar > Group > Administration > Page Management > Add New Page III. Create Page accessible via Toolbar > Manage Sites > Edit Navigation > Create Node > Page Selector > Create Page For each of them, the defaults should be set as follows: (1) For portal pages the access and edit permissions should be taken from the parent site. (2) For group pages, the the default access permissions should be set to all group members and edit should be set only to the given group's members with the membership type defined in {{navigation.creator.membership.type}} configuration parameter of {{UserACL}} service. (3) For any kind of page (portal, group, etc.), the move*Permissions form defaults are taken over form the {{page.xml}} template chosen in the given form. If the given form offers no page template choice, the {{empty}} template should be used. In the present implementation, the named requirements are mostly met, however the code is spread over several classes, and is not always 100% consistent, which should hereby be fixed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3469) PortalSetupCommand does not ensure that initialpassword is written on a new line

by Peter Palaga (JIRA)

Peter Palaga created GTNPORTAL-3469: --------------------------------------- Summary: PortalSetupCommand does not ensure that initialpassword is written on a new line Key: GTNPORTAL-3469 URL: https://issues.jboss.org/browse/GTNPORTAL-3469 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Peter Palaga Assignee: Peter Palaga Steps to reproduce: (1) Ensure that {{$JBOSS_HOME/standalone/configuration/gatein/configuration.properties}} do not contain gatein.portal.setup.initialpassword.root in any form: commented or active. (2) Ensure that the last key value pair is not terminated with a new line character (3) run {{$JBOSS_HOME/bin/portal-setup.sh" -p "secret"}} Not OK: The {{configuration.properties}} file ends with {code:plain} # Logged user keep alive gatein.webui.keepalive.enabled=true gatein.webui.keepalive.interval=60000gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh {code} Expected: {code:plain} # Logged user keep alive gatein.webui.keepalive.enabled=true gatein.webui.keepalive.interval=60000 gatein.portal.setup.initialpassword.root=6MSyXIj3kkQ= # Modified by portal-setup.sh {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues May 2014