December 2010 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1298) Conflict between Dashboard Tab and site pages url

by Khalil AISSAOUI (JIRA)

Conflict between Dashboard Tab and site pages url ------------------------------------------------- Key: GTNPORTAL-1298 URL: https://jira.jboss.org/browse/GTNPORTAL-1298 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-CR01 Reporter: Khalil AISSAOUI Fix For: 3.1.0-GA To reproduce the problem you have to: * Launch GateIn * Connect as "root" * Click on "Dashboard" * Rename "Tab_0" to "home" ==> Redirected to home page and can't add, delete, modify your dashboard. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1311) Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively

by Minh Hoang TO (JIRA)

Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively ----------------------------------------------------------------------------------------------------------------- Key: GTNPORTAL-1311 URL: https://jira.jboss.org/browse/GTNPORTAL-1311 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Minh Hoang TO Assignee: Minh Hoang TO In legacy code, both UINavigationPortlet and UISitemapPortlet use UIPortalNavigation to handle the underlying navigations. That was logical in the past as before navigation portlet showed all PageNavigations as UISitemap did. Now, the methods declared in UIPortalNavigaton belongs to two independent groups, one group consists of methods used in sitemap portlet. The other consists of methods used in navigation portlet. On the other hand, using UIPortalNavigation in sitemap portlet requires storing template name in the PortletPreference. Hence, it 's better to split UIPortalNavigation into two classes now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
11
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1605) Merging PageNavigations should also merge child PageNodes

by Matt Wringe (JIRA)

Merging PageNavigations should also merge child PageNodes --------------------------------------------------------- Key: GTNPORTAL-1605 URL: https://jira.jboss.org/browse/GTNPORTAL-1605 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe The PageNavigation.merge command only merges in top level PageNodes, if a PageNode with the same name already exists, it will overwrite the previous node with a new one. This prevents being able to add a new page node to a subnode which already exists. For example, the administration node by default contains the app-registry and page-management PageNodes. I cannot use the extension mechanism to add an extra PageNode here, since the PageNavigation.merge will delete the current administration node and overwrite it with the one I specify in the extension. In this situation I am stuck adding it to another top level location, which is not ideal. What should happen is that the child PageNodes get merged together, so that I can add extra nodes anywhere in the PageNode tree. This will however change the behaviour of how extensions work. What this means is that you can no longer overwrite or remove PageNodes using the extension mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1737) Can't loogin to portal when input ULR with sepecial case

by Hang Nguyen (JIRA)

Can't loogin to portal when input ULR with sepecial case -------------------------------------------------------- Key: GTNPORTAL-1737 URL: https://issues.jboss.org/browse/GTNPORTAL-1737 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Input URL on adress barby: http://localhost:8080/portal/private/classic/groupnavigation?portal:compo... - Input user name and pass - Click Sign in => can't login to portal and Return to public mode Expected output: After input user and pass and click Sign In => Login in successfully -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1609) Can't do any action after open 3 Popup Windown

by Hang Nguyen (JIRA)

Can't do any action after open 3 Popup Windown ---------------------------------------------- Key: GTNPORTAL-1609 URL: https://jira.jboss.org/browse/GTNPORTAL-1609 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Hang Nguyen - Go to group Navigation - Click Edit navigation - Add new node -> Add new node appear - Choose Page Selector - Click Search and Select page - Input page name which does not exits in list - Click Search => show message -> OK - Close all popup window => Can't do any action after open 3 Popup Windown -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1720) Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler

by Minh Hoang TO (JIRA)

Rename the confusing methods setFullRender/getFullRender in PortalRequestHandler --------------------------------------------------------------------------------- Key: GTNPORTAL-1720 URL: https://jira.jboss.org/browse/GTNPORTAL-1720 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Minh Hoang TO {code:java} /** * Sets a boolean value to force whether portal will be fully rendered * and it is only effective to an Ajax request.<p/> * * if the value is set to <code>true</code>, it means :<br/> * * 1) Only portal ui components are rendered <br/> * 2) Portlets will be fully rendered if are inner of the portal ui components being updated * * @param forceFullUpdate */ final public void setFullRender(boolean forceFullUpdate) { this.forceFullUpdate = forceFullUpdate; } {code} As mentioned in the Javadoc, while AJAX update is used, the forceFullUpdate decide whether only component of portal (ie: The components outside portlet window UIPortlet such as UIMaskWorkspace, UIWorkingWorkspace,...) The name of method is very confusing. If we wish to update only components of portal, we have to call setFullRender(true) (I'm sure that most developers think of setFullRender(false) ) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
11
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1734) Edit CAS section in reference guide document

by Khoi Nguyen (JIRA)

Edit CAS section in reference guide document -------------------------------------------- Key: GTNPORTAL-1734 URL: https://issues.jboss.org/browse/GTNPORTAL-1734 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen Fix For: 3.2.0-GA In section http://docs.jboss.com/gatein/portal/3.1.0-FINAL/reference-guide/en-US/htm... , we guide to edit the jaas.conf file in Tomcat server seems incorrect. We must change to org.gatein.sso.agent.login.SSOLoginModule required; org.exoplatform.services.security.j2ee.TomcatLoginModule required portalContainerName=portal realmName=gatein-domain; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
6
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1558) Have an option to set the default value for "Show Info Bar" and make it disable by default

by Thomas Heute (JIRA)

Have an option to set the default value for "Show Info Bar" and make it disable by default ------------------------------------------------------------------------------------------ Key: GTNPORTAL-1558 URL: https://jira.jboss.org/browse/GTNPORTAL-1558 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Heute >From training field, it seems that most common use cases is to remove the info bar from portlets, so it should probably be made as default. But there should be a way to set the default to be the former behavior -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
16
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1502) DateTimeValidator validates incorrect with particular languages

by Khoi Nguyen (JIRA)

DateTimeValidator validates incorrect with particular languages --------------------------------------------------------------- Key: GTNPORTAL-1502 URL: https://jira.jboss.org/browse/GTNPORTAL-1502 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Khoi Nguyen With a particular language, French for example, if value of UIFormDateTimeInput field having day value > 12, DateTimeValidator would return false. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
9
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1450) Priority for skin modules

by Patrice Lamarque (JIRA)

Priority for skin modules ------------------------- Key: GTNPORTAL-1450 URL: https://jira.jboss.org/browse/GTNPORTAL-1450 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 3.1.0-GA Reporter: Patrice Lamarque The css stylesheets declared in gatein-resources.xml files get merged in no specific order. Sometimes, it is useful to control the order in which the resulting css markup appears in the merged file in order to apply css overrides. This is typically the kind of things you would like to do in an extension. By implementing a priority on skin module we should be able to give more control to the overrides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

7
20
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues December 2010