[JBoss JIRA] (GTNPORTAL-2899) The membership type "*" is not interpreted
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2899?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2899:
----------------------------------
Sprint: Sprint 80
> The membership type "*" is not interpreted
> -------------------------------------------
>
> Key: GTNPORTAL-2899
> URL: https://issues.jboss.org/browse/GTNPORTAL-2899
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.3.Final
> Environment: eXo Platform 4.0.0-Beta2
> Reporter: Hela Zekri
> Assignee: Trong Tran
> Priority: Blocker
> Labels: portal-s71, worked
> Fix For: 3.7.0.Final
>
>
> {color:red}
> In eXo Platform, we have the membership type "*". If user has this membership type in a group, it means that he has all membership types in this group.
> {color}
> *Please try this scenario :*
> Add a user that has the membership type "manager" in "/platform/administrators" group and the membership type "*" in "/platform/users" group.
> When this user clicks "add page" in "Page Management", he has the possibility to choose the owner type "group" or "portal". If he chooses "group", the expected output is that he gets as "Owner Id", a selectbox that contains all groups in which he has the membership type "manager".
> (!) The membership type "manager" is set in "portal-configuration.xml" as value-param to UserACL component :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>manager</value>
> </value-param>
> {code}
> In this case, user should get as "Owner Id" a selectbox that contains "/platform/administrators" and "/platform/users" groups(The membership type "*" includes "manager" membership type).
> But the current behavior is that the selectbox of "Owner Id" contains only the group "/platform/administator". This is due to the fact that the relationship "*" is considered as a String and not interpreted.
> *There are two possible solutions to this problem :*
> 1- Set the possibility to put many values for "navigation.creator.membership.type" value-param. So that we could do for example :
> {code:xml}
> <value-param>
> <name>navigation.creator.membership.type</name>
> <description>specific membership type have full permission with group navigation</description>
> <value>*,manager</value>
> </value-param>
> {code}
> 2- In "_findRoles_" method in "_org.picketlink.idm.impl.api.session.managers.RoleManagerImpl_" class :
> In the code bellow, each relationship of a user is compared to roleType ("manager"). If it is equal, it will be added to the list that will be returned. So even "*" is compared to "manager", it is not equal, so it won't be added.
> {code}
> for (IdentityObjectRelationship relationship : relationships)
> {
> if (roleType != null)
> {
> if (roleType.getName().equals(relationship.getName()))
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> else
> {
> roles.add(new SimpleRole(new SimpleRoleType(relationship.getName()), createUser(relationship.getToIdentityObject()), createGroup(relationship.getFromIdentityObject())));
> }
> }
> {code}
> We created [https://issues.jboss.org/browse/PLIDM-40] in which we propose a patch that adds a test on "*" value.
> In the patch, we changed :
> {code}
> if (roleType.getName().equals(relationship.getName()))
> {code}
> to :
> {code}
> if ((roleType.getName().equals(relationship.getName())) || relationship.getName().equals("*"))
> {code}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3273) It restores all pre-defined configuration when re-creating a site config with the same name
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3273?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3273:
----------------------------------
Sprint: Sprint 80
> It restores all pre-defined configuration when re-creating a site config with the same name
> -------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3273
> URL: https://issues.jboss.org/browse/GTNPORTAL-3273
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.6.Final, 3.6.1.Final
> Reporter: Trong Tran
> Fix For: 3.7.0.Final
>
>
> Steps to reproduce:
> - Login with root
> - Edit the home page layout to add the Organization Porltet
> - In Organization portlet, go to delete the pre-defined group /organization/management/executive-board. You will notice that it also deletes all data (navigation nodes, pages) belonging to that group
> - Then re-create a group with the same name under /organization/management/.
> ===> Now you will see that all pre-defined data is restored as the first initializing time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ]
Peter Palaga resolved GTNPORTAL-3250.
-------------------------------------
Fix Version/s: 3.6.4.Final
3.7.0.Final
Resolution: Done
Accepting that the observed error is due to the independent issue GTNWSRP-371.
> The portlets cannot be displayed after a portal reload
> ------------------------------------------------------
>
> Key: GTNPORTAL-3250
> URL: https://issues.jboss.org/browse/GTNPORTAL-3250
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: PC integration
> Affects Versions: 3.6.1.Final
> Reporter: Nicolas Filotto
> Assignee: Marko Strukelj
> Fix For: 3.6.4.Final, 3.7.0.Final
>
> Attachments: GTNPORTAL-3250.patch
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406.
> Here are the steps to reproduce:
> * Start GateIn with ./standalone.sh -Dexo.product.developing=true
> * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}}
> * Once the command is over, go to http://localhost:8080/portal/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-2394) The GadgetDeployer should unregister itself as WebAppListener in the stop method
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2394?page=com.atlassian.jira.pl... ]
Peter Palaga resolved GTNPORTAL-2394.
-------------------------------------
Fix Version/s: 3.6.4.Final
3.7.0.Final
Resolution: Done
> The GadgetDeployer should unregister itself as WebAppListener in the stop method
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2394
> URL: https://issues.jboss.org/browse/GTNPORTAL-2394
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.1.0-GA
> Reporter: Nicolas Filotto
> Labels: gadget
> Fix For: 3.6.4.Final, 3.7.0.Final
>
> Attachments: GTNPORTAL-2394.patch
>
>
> Up to now, when the application tries to stop the component instead of unregistering itself it registers itself another time. Indeed the current code is:
> {code}
> public void stop()
> {
> DefaultServletContainerFactory.getInstance().getServletContainer().addWebAppListener(this);
> }
> {code}
> But should be:
> {code}
> public void stop()
> {
> DefaultServletContainerFactory.getInstance().getServletContainer().removeWebAppListener(this);
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3044) Inconsistency in html elements of shared layout/user bar portlets
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3044?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3044:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.7.0.Final
Resolution: Done
> Inconsistency in html elements of shared layout/user bar portlets
> -----------------------------------------------------------------
>
> Key: GTNPORTAL-3044
> URL: https://issues.jboss.org/browse/GTNPORTAL-3044
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta02
> Environment: jboss-jpp-6.1.0.ER1-prod-17052013.zip
> Reporter: Vlastislav Ramik
> Assignee: Tuyen Nguyen The
> Labels: JPP61-Test-dev
> Fix For: 3.7.0.Final
>
> Original Estimate: 6 hours
> Time Spent: 1 day
> Remaining Estimate: 0 minutes
>
> Shared layout/user bar portlets (ie the bar that appears at the top of the page when you are a logged-in user) has following inconsistency:
> Portal Actions (that with the redhat icon): {noformat}<li title="Portal Actions" style="width: 62px" class="UITab portlet-menu-item">{noformat} The is also empty link as a child of the <li> but it has zero length.
> Site: {noformat}<a title="Sites" class="SitesIcon TBIcon" href="javascript:;">Site</a>{noformat}
> Group: {noformat}<span title="Group" class="GroupIcon TBIcon">Group</span>{noformat}
> Dashboard: If the user does not have any dashboard pages there is a link. If the user has a dashboard page there is a span. This is correct in my opinion.
> Site/Group/Dashboard Editor: {noformat}<a title="Site/Group/Dashboard Editor" href="#" class="EditorIcon TBIcon">Site/Group/Dashboard Editor</a>{noformat}
> All this leads to different looking cursors when you hovering the portlet.
> Portal Actions: arrow cursor
> Site: link cursor and text is highlighted
> Group:
> - arrow cursor when you are hovering that "people" icon
> - text cursor when you are hovering Group text
> Dashboard:
> - in case of none dashboard pages - it behaves the same as Site
> - in case on any dashboard pages - it behaves the same as Group
> Site/Group/Dashboard Editor: link cursor and text is highlighted
> The solution can be using css cursor (e.g. cursor: pointer; ) but cleaner solution would be probably unify it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3273) It restores all pre-defined configuration when re-creating a site config with the same name
by Trong Tran (JIRA)
Trong Tran created GTNPORTAL-3273:
-------------------------------------
Summary: It restores all pre-defined configuration when re-creating a site config with the same name
Key: GTNPORTAL-3273
URL: https://issues.jboss.org/browse/GTNPORTAL-3273
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.1.Final, 3.5.6.Final
Reporter: Trong Tran
Fix For: 3.7.0.Final
Steps to reproduce:
- Login with root
- Edit the home page layout to add the Organization Porltet
- In Organization portlet, go to delete the pre-defined group /organization/management/executive-board. You will notice that it also deletes all data (navigation nodes, pages) belonging to that group
- Then re-create a group with the same name under /organization/management/.
===> Now you will see that all pre-defined data is restored as the first initializing time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload
by Marko Strukelj (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ]
Marko Strukelj commented on GTNPORTAL-3250:
-------------------------------------------
This is another issue manifesting itself: https://issues.jboss.org/browse/GTNWSRP-371
In order to avoid it just remove gatein-wsrp-integration.ear from gatein/extensions.
> The portlets cannot be displayed after a portal reload
> ------------------------------------------------------
>
> Key: GTNPORTAL-3250
> URL: https://issues.jboss.org/browse/GTNPORTAL-3250
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: PC integration
> Affects Versions: 3.6.1.Final
> Reporter: Nicolas Filotto
> Assignee: Marko Strukelj
> Attachments: GTNPORTAL-3250.patch
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406.
> Here are the steps to reproduce:
> * Start GateIn with ./standalone.sh -Dexo.product.developing=true
> * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}}
> * Once the command is over, go to http://localhost:8080/portal/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months