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. | Community
Skip to main content
S
Seema1
Level 2
June 17, 2022
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.

  • 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

5 replies

S
Seema1Author
Level 2
June 17, 2022

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

    U
    user1576Accepted solution
    Level 3
    June 17, 2022

    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

      S
      skumari1
      Level 3
      July 8, 2022

      Hi @user1576 

      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.

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        June 17, 2022

        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
          Level 2
          June 21, 2022

          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.

           

            joerghoh
            Adobe Employee
            joerghohAdobe Employee
            Adobe Employee
            June 25, 2022

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

              Siva_Sogalapalli
              Community Advisor
              Siva_SogalapalliCommunity Advisor
              Community Advisor
              June 17, 2022

              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 

               

                ShaileshBassi
                Community Advisor
                ShaileshBassiCommunity Advisor
                Community Advisor
                June 17, 2022

                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
                  Level 2
                  June 21, 2022

                  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.

                    Terms & ConditionsAccessibility statement

                    Loading footer...