Hey all, I am having rough time with permissions and move within AEM right now.I have the requirement that a editor without delete and publish rights should still be able to sort/reorder the pages (in list view via the dnd-handles).
I was looking and apparently this is considered a move operation. Move operation has been removed though as it requires delete and unpublish permissions.Are you aware of any other way to reorder pages / providing editors with the capabilities without the need of allowing them to delete / publish/unpublish pages?
I am wondering why this is considered a move as I am just changing the order of the nodes of the parent's page. There is no need to adjust any references thus I don't see why deletion and subsequentionally also unpublish rights are required
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi,
By design, the "move" operation consists of copying the node to the new location and then removing the old one. Hence, you cannot perform a move without "delete" permissions.
Some options that come to mind: You could disable the "delete" and "publish" buttons in the UI based on the group. This can be achieved by using granite:renderconditions. Please check this thread: https://jpsoares.medium.com/aem-granite-render-conditions-438c804b1e5a
Another alternative to explore is to use "preprocessors" to manually check if the group can replicate (publish) a resource. Review this link: https://dileepakv.blogspot.com/2018/01/aem-replication-preprocessor.html
Similar thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/what-permissions-does-some...
Hope this helps
Hi,
By design, the "move" operation consists of copying the node to the new location and then removing the old one. Hence, you cannot perform a move without "delete" permissions.
Some options that come to mind: You could disable the "delete" and "publish" buttons in the UI based on the group. This can be achieved by using granite:renderconditions. Please check this thread: https://jpsoares.medium.com/aem-granite-render-conditions-438c804b1e5a
Another alternative to explore is to use "preprocessors" to manually check if the group can replicate (publish) a resource. Review this link: https://dileepakv.blogspot.com/2018/01/aem-replication-preprocessor.html
Similar thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/what-permissions-does-some...
Hope this helps
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies