PUBLIC - Liferay Portal Community Edition
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-15409

Document Library folder permissions are not exporting/importing for Administrators/Owners.

    Details

    • Branch Version/s:
      6.0.x
    • Backported to Branch:
      Committed
    • Similar Issues:
      Show 3 results 

      Description

      1. Create a site template with 1 page and place Document Library portlet on page with 1 folder.
      2. Set permissions on portlet and folder to grant owner, Community Administrator and Community Owner full rights.
      3. Create new community using site template above as private pages
      4. Inspect the permissions on the Document Library portlet in the target community and the Community Administrator and Community Owner roles are missing.

      See attached image for views of the permissions.

      Also, same behavior observed if simply using the portlet export/import facility.

        Activity

        Hide
        Jorge Ferrer added a comment -

        Hi James et al,

        The Community Owner and Community Admin roles are special roles that have all permissions by default. There is no need to assign explicit permissions because the permission system uses shortcuts for performance and won't even check them.

        That's the reason why the UI doesn't show those roles, they already have all permissions and you won't be able to remove them (and administrator of a community wouldn't want a user to put something in the community and hide it from him, right?)

        Considering this, I'm not sure if there is a bug here or not. What's exactly the issue you experience when exporting/importing?

        Show
        Jorge Ferrer added a comment - Hi James et al, The Community Owner and Community Admin roles are special roles that have all permissions by default. There is no need to assign explicit permissions because the permission system uses shortcuts for performance and won't even check them. That's the reason why the UI doesn't show those roles, they already have all permissions and you won't be able to remove them (and administrator of a community wouldn't want a user to put something in the community and hide it from him, right?) Considering this, I'm not sure if there is a bug here or not. What's exactly the issue you experience when exporting/importing?
        Hide
        Juan G added a comment -

        Hi James,

        It seems permissions for those roles can't be modified at all when scope is default (always will have permissions if portlet belongs to the organization/community).

        So IMHO this issue doesn't exist. Perhaps solution could be to change that portlet scope to non-default or change role for that.

        What do you think?

        Show
        Juan G added a comment - Hi James, It seems permissions for those roles can't be modified at all when scope is default (always will have permissions if portlet belongs to the organization/community). So IMHO this issue doesn't exist. Perhaps solution could be to change that portlet scope to non-default or change role for that. What do you think?
        Hide
        James Denmark added a comment -

        Thanks for the explanation Jorge, that makes sense.

        My use case for restricting this was to prevent admins/owners from changing the folder structure we provide in the community templates. That way only the omniadmin could do that. Sounds like I need to create a more restricted community manager role that still has the rights to make announcements, accept/deny membership requests, add portlets etc.

        Presumably the ability to set the these permissions in the site template is still an outstanding bug?

        Also, changing a portlet to page scope is allowing the admin/owner permissions to be changed. Also a bug?

        The main issue still requires a solution: not carrying over the more restricted member permissions settings from the site template.

        Also see http://issues.liferay.com/browse/LPS-17683 for another issue with page scoped permissions and teams.

        Show
        James Denmark added a comment - Thanks for the explanation Jorge, that makes sense. My use case for restricting this was to prevent admins/owners from changing the folder structure we provide in the community templates. That way only the omniadmin could do that. Sounds like I need to create a more restricted community manager role that still has the rights to make announcements, accept/deny membership requests, add portlets etc. Presumably the ability to set the these permissions in the site template is still an outstanding bug? Also, changing a portlet to page scope is allowing the admin/owner permissions to be changed. Also a bug? The main issue still requires a solution: not carrying over the more restricted member permissions settings from the site template. Also see http://issues.liferay.com/browse/LPS-17683 for another issue with page scoped permissions and teams.
        Hide
        Jorge Ferrer added a comment -

        Hi James, Juan,

        I've just committed a fix to trunk (r82023) that makes the portal properly hide those administrator roles from all resources to avoid the confusion. I'm marking the ticket as resolved.

        Show
        Jorge Ferrer added a comment - Hi James, Juan, I've just committed a fix to trunk (r82023) that makes the portal properly hide those administrator roles from all resources to avoid the confusion. I'm marking the ticket as resolved.
        Hide
        Michael Saechang added a comment -

        PASSED Manual Testing using the following steps:

        1. Add Document Library Portlet.
        2. Add Folder.
        3. Edit permissions for folder.
        4. Verify that Community Admin and Community Owner no longer appears.

        Fixed on:
        Tomcat 6.0 + MySQL 5. Firefox 3.6.16. 6.0.x Revision 83034.
        Tomcat 6.0 + MySQL 5. Firefox 3.6.16. 6.1.x Revision 83069.

        Show
        Michael Saechang added a comment - PASSED Manual Testing using the following steps: 1. Add Document Library Portlet. 2. Add Folder. 3. Edit permissions for folder. 4. Verify that Community Admin and Community Owner no longer appears. Fixed on: Tomcat 6.0 + MySQL 5. Firefox 3.6.16. 6.0.x Revision 83034. Tomcat 6.0 + MySQL 5. Firefox 3.6.16. 6.1.x Revision 83069.

          People

          • Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              3 years, 42 weeks, 1 day ago

              Development

                Structure Helper Panel