Enable/Disable Rebuild Client Libraries Option | Community
Skip to main content
Sady_Rifat
Community Advisor
Sady_RifatCommunity Advisor
Community Advisor
July 24, 2023
Solved

Enable/Disable Rebuild Client Libraries Option

  • July 24, 2023
  • 2 replies
  • 1700 views

Hello Community members,

In AEM there is a option for clientlibs: http://localhost:4502/libs/granite/ui/content/dumplibs.rebuild.html 

Where we can rebuild/invalidate the cache of clientlibs.

 

By default, it's always enabled. Now my query-> is there any option where I can enable or disable this option? I prefer an OSGI Config option that makes it enable or disable (OOTB).

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 nitesh_kumar-1

Hi @sady_rifat ,

 

AFAIK, you cannot control this through OSGi configuration, since the logic is through JSP and some interdependent services.

 

One way could be by overlaying /libs/granite/ui/components/dumplibs, but I won't recommend it because it's granite:InternalArea.

 

Another way would be to enable/disable the path "/libs/granite/ui/components/dumplibs" using the ACL, so that specific folks can access this path, and you can enable and disable it for them.

 

Hope that helps!

 

Regards,

Nitesh

2 replies

nitesh_kumar-1
Adobe Employee
nitesh_kumar-1Adobe EmployeeAccepted solution
Adobe Employee
July 24, 2023

Hi @sady_rifat ,

 

AFAIK, you cannot control this through OSGi configuration, since the logic is through JSP and some interdependent services.

 

One way could be by overlaying /libs/granite/ui/components/dumplibs, but I won't recommend it because it's granite:InternalArea.

 

Another way would be to enable/disable the path "/libs/granite/ui/components/dumplibs" using the ACL, so that specific folks can access this path, and you can enable and disable it for them.

 

Hope that helps!

 

Regards,

Nitesh

    yuriy_shestakov
    yuriy_shestakov
    Level 3
    July 24, 2023

    One or two years ago I experienced the situation when the rebuilding client libraries broke the authoring interface so we had to take some activities to fix it. However, usually issues like that should not happen, so if you rebuild all libraries and something broke, let Adobe know if you have problems when you click that rebuild button.

    This mechanism should exist as there's no other way to rebuild a library when you "repo put" some content to that library, I don't remember which - JS/CSS files or the clientlib configuration (updated js.txt, css.txt or .content.xml file) - updating some of those ones doesn't update the resulting client library file. 

    If you want to disable it on your environments' author for usual users, just set up the dispatcher access for the author instance and forbid it on the dispatcher. Allow direct access to that server (without dispatcher) only for developer IP addresses (we use VPN to achieve this).

    Another way, for both remote and local AEMs, you can try to setup ACL in useradmin to disable the whole path /libs/granite/ui/content/dumplibs, but I am not sure it will help you 😞

    Also, you can try to write Sling Servlet Filter for that path (a service that implements javax.servlet.Filter, you can find samples in ACS Commons code or in WCM Core Components code), where you won't pass the processing to another filter in the chain or return another response.

      Terms & ConditionsAccessibility statement

      Loading footer...