Details

    • Similar Issues:
      Show 5 results 

      Description

      Currently, it is not possible to define permissions to a custom role be able to post an announcements in the general scope.

      In "entry_select_scope.jspf" in the Announcements portlet, there is the following permission check:

      <c:if test="<%= permissionChecker.isOmniadmin() %>">
      <aui:option label="general" selected="<%= (classNameId == 0) && (classPK == 0) %>" value="0,0" />

      In consulting with our development team, they have also found that the OmniAdmin check happens in these files:

      entry_select_scope.jspf (Line 18)
      view_manage_entries.jspf (Line 30)
      AnnouncementsEntryServiceImpl.java (Line 60)

      Is it possible to add in a permission so that we can define this access for custom roles without having to give them the administrator role.

        Activity

        Hide
        Randy Zhu added a comment -

        In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.

        Show
        Randy Zhu added a comment - In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.
        Hide
        Raymond Auge added a comment -

        I think this issue can be closed as "Reorganized under LPS-34139".

        By allowing to manage announcements for Guest and User roles, the need for finer permissions on the "General" scope is no longer necessary.

        Show
        Raymond Auge added a comment - I think this issue can be closed as "Reorganized under LPS-34139 ". By allowing to manage announcements for Guest and User roles, the need for finer permissions on the "General" scope is no longer necessary.
        Hide
        Scott Palmer added a comment - - edited

        I'm not sure how 'allowing to manage announcements for Guest and User roles' is a solution.

        Think of this scenario:
        The portal admin wants general users (user role) to be able to add announcements (because they go through a workflow). The people who read these announcements are not logged in (Guest role). So the hard part is actually creating a role that gives the permission for a user who isn't an admin to create an announcement that guest users can see (which is what the general scope does - but it's not permissionable from what I can tell as it's not a community, user group or role and does not have a checkbox anywhere in the current permission scheme).

        How do we get that working? Giving users admin isn't an option and giving guests power user status or elevated privileges isn't an option either. What we want is to give a role permission to post to the general scope.

        Edit: it is possible to give them the Roles>Manage Announcements permission but that's not a very clean user experience as they see all the roles and only 'guest' is relevant. having a single 'General' option would be much more user friendly.
        Edit2: I take it back. That's not a solution at all because then when you login the announcement vanishes. It seems like General is still the only one that fits the bill.

        Show
        Scott Palmer added a comment - - edited I'm not sure how 'allowing to manage announcements for Guest and User roles' is a solution. Think of this scenario: The portal admin wants general users (user role) to be able to add announcements (because they go through a workflow). The people who read these announcements are not logged in (Guest role). So the hard part is actually creating a role that gives the permission for a user who isn't an admin to create an announcement that guest users can see (which is what the general scope does - but it's not permissionable from what I can tell as it's not a community, user group or role and does not have a checkbox anywhere in the current permission scheme). How do we get that working? Giving users admin isn't an option and giving guests power user status or elevated privileges isn't an option either. What we want is to give a role permission to post to the general scope. Edit: it is possible to give them the Roles>Manage Announcements permission but that's not a very clean user experience as they see all the roles and only 'guest' is relevant. having a single 'General' option would be much more user friendly. Edit2: I take it back. That's not a solution at all because then when you login the announcement vanishes. It seems like General is still the only one that fits the bill.
        Hide
        Scott Palmer added a comment -

        Where's the contributed solution? Isn't this still open?

        Show
        Scott Palmer added a comment - Where's the contributed solution? Isn't this still open?
        Hide
        Scott Palmer added a comment -

        This is not a feature request. It's is a bug. You already have the feature built into the asset publisher but it is missing the associated permissions to provide the feature to anyone other than an Portal Admin. The only available workaround is to make everyone a Portal Admin. We have already patched the bug and will provide the fix. Please correct the ticket type.

        Show
        Scott Palmer added a comment - This is not a feature request. It's is a bug. You already have the feature built into the asset publisher but it is missing the associated permissions to provide the feature to anyone other than an Portal Admin. The only available workaround is to make everyone a Portal Admin. We have already patched the bug and will provide the fix. Please correct the ticket type.
        Hide
        Vicki Tsang added a comment -

        This may have already been fixed under LPS-41361.

        Show
        Vicki Tsang added a comment - This may have already been fixed under LPS-41361 .

          People

          • Votes:
            4 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Days since last comment:
              39 weeks, 5 days ago

              Development

                Structure Helper Panel