Expand my Community achievements bar.

SOLVED

Hide Manage publication from sites console, hide Request publication and Request unpublication from Page information tab in

Avatar

Level 2

I'm using AEMasCloud, I have a specific group for authors(xyz-authors) where I have added workflow users to its group, Now, for its members, when they select a page I want to hide Manage publication option from sites console, also, hide Request publication and Request unpublication options from Page information tab. I have tried the below code. 

"set ACL for xyz-author \n deny crx:replicate on /content/xyz \nend",
"set ACL for xyz-author \n deny jcr:read on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication \nend"

It is not working.  

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @tejaswi_aem 

You are doing right, just try with different syntax

set ACL on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication
  deny jcr:read for xyz-author
end
Arun Patidar

AEM LinksLinkedIn

View solution in original post

2 Replies

Avatar

Community Advisor

Hi @tejaswi_aem,

You’ll need to add a clientlib under apps that injects JS in the sites console and page editor context menus, checks if the current user is in xyz-authors, and then hides those actions.

1. Create clientlib - Path:/apps/yourproject/clientlibs/authoring/hide-publicationcq:ClientLibraryFolder with:

categories = ["cq.authoring.page"]
dependencies = ["cq.authoring.siteadmin.admin"]

2. Add JS logiclike  hide-publication.js:

3. Include clientlib

Add this clientlib to author by overlaying /libs/cq/gui/components/authoring/editors/clientlibs/core with:

<yourproject
    jcr:primaryType="nt:unstructured"
    categories="[cq.authoring.page]"
    dependencies="[cq.authoring.siteadmin.admin]"
    embed="[yourproject.clientlibs.authoring.hide-publication]"/>

 


Santosh Sai

AEM BlogsLinkedIn


Avatar

Correct answer by
Community Advisor

Hi @tejaswi_aem 

You are doing right, just try with different syntax

set ACL on /libs/wcm/core/content/sites/jcr:content/actions/selection/managepublication
  deny jcr:read for xyz-author
end
Arun Patidar

AEM LinksLinkedIn