-
Bug
-
Resolution: Fixed
-
Neutral
-
5.3.10, 5.4.2
-
-
Empty show more show less
-
Yes
-
Yes
-
Saigon 43
-
8
Tasks which are resolved can only be achieved by users with superuser role.
But this does not fit reality in projects...
The customer needs to be able to decide, who can archive successful pulse tasks.
It is a 'no go' to give somebody complete superuser rights just to be able to archive pulse tasks.
A valid situation would be:
- Let also publishers archive their tasks.
- Or, let an explicit role archive tasks.
In 5.4.x its line 143 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:
User user = MgnlContext.getUser();
// TODO ideally context menu action availability should use the same mechanism and rules defined in the messageView config
// but as this is not straightforward, for the time being we hack it like this
if (user.getAllRoles().contains("superuser")) {
addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");
}
In 5.3.x its line 153 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:
User user = MgnlContext.getUser();
// TODO ideally context menu action availability should use the same mechanism and rules defined in the messageView config
// but as this is not straightforward, for the time being we hack it like this
if (user.getAllRoles().contains("superuser")) {
addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");
}
In my opinion, an implementation like this is exactly what the comment says: "we hack it like this"...
- is causing
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
MGNLUI-3638 Resurrect the DefaultAvailabilityChecker and use that one in pulse-context
-
- Closed
-
