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.

Forum|Forum|3 years ago
June 17, 2022
5 replies
2250 views

No text available

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by user1576

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

ShaileshBassi

New Participant

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

S

Seema1Author

New Participant

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.

Siva_Sogalapalli

New Participant

As @joerghoh 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

Please refer below for more info:

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

joerghoh

Employee

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).

S

Seema1Author

New Participant

Hi @joerghoh

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.