Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Hi Team, I have a requirement in my project where I need to disable 'save and close' button for some users in content page properties.

Avatar

Level 2
 
1 Accepted Solution

Avatar

Correct answer by
Level 3

Can you please check 

/libs/wcm/core/content/sites/properties

/libs/cq/gui/components/siteadmin/admin/properties/clientlibs/properties/js/properties.js

 

.I will add if found something more

View solution in original post

12 Replies

Avatar

Level 2

Or it will be helpful if anyone can tell me where this save and close' button stored in aem.

Avatar

Correct answer by
Level 3

Can you please check 

/libs/wcm/core/content/sites/properties

/libs/cq/gui/components/siteadmin/admin/properties/clientlibs/properties/js/properties.js

 

.I will add if found something more

Avatar

Level 3

Hi @sanketd27011989 

Not get the exact location of save and close button but only got the properties.jsp file inside "libs/granite/ui/components/shell/propertiespage/propertiespage.jsp" where it is defined but even after omitting it it not got disappeared from content page.

Avatar

Employee Advisor

Do you want to that these users should not be able to update page properties? If that's the case you can achieve this with proper permissions on the page itself (only read permissions).

Avatar

Level 2

Hi @Jörg_Hoh 

We have one reviewer group and for this group we want to hide the save and close' button in page properties. That means that group members can open the page properties, see the details but can not save the changes as "save and close" will be either invisible aur not responsive for them.

 

Avatar

Employee Advisor

This is the default behavior if you don't have write access on that page, but only read permissions.

Avatar

Level 3

Hi @Jörg_Hoh 

The requirement is to create a custom group having "deny access for save and close button from properties tab" which should be placed in group.yml file like below:-

skumari1_0-1657092048189.png

Can we achieve the requirement like this?

Avatar

Employee Advisor

The question is if the users must not have write access to page properties but to the components on the page, or if the whole page should be write protected.

Should they be able to move/delete pages?

 

In any case you should look into https://github.com/Netcentric/accesscontroltool/blob/develop/docs/AdvancedFeatures.md and the Oak documentation (https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html, search for the "rep:glob" examples).

Avatar

Community Advisor

As @Jörg_Hoh replied, you can simply achieve through user admin console in AEM. 

Eg: 

1. Go to the user admin console http://localhost:4502/useradmin 

2. Select the user & just enable read access

Siva_Sogalapalli_0-1655474384855.png

 

Please refer below for more info: 

https://experienceleague.adobe.com/docs/experience-manager-64/administering/security/security.html?l... 

 

Avatar

Level 8

Hi @Seema1 As John suggested, you should achieve it via the permissions.

As if there is any change in the specified OOTB clientlibs in the upcoming Service Pack or in the next AEM version, then it will be a bottleneck.
Plus some of the overlay are not allowed in AEMaaCS.

 

So if the above use case is not met by the permission, in that case create your own clientLibs and get it loaded  via the category "cq.siteadmin.admin.properties" and you can perform hide/show.

Thanks

Avatar

Level 2

Hi @shaileshbassi 

I have suggested the above method to my team and waiting for their reply.

Will reply back in some time.

Thanks for the all comments.