Clientlib not reflecting changes in real time!!

Avatar

Avatar
Boost 1
Level 1
hs06
Level 1

Likes

2 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Give Back
Ignite 1
Validate 1
View profile

Avatar
Boost 1
Level 1
hs06
Level 1

Likes

2 likes

Total Posts

11 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Give Back
Ignite 1
Validate 1
View profile
hs06
Level 1

27-06-2021

Hi,

I am using AEM 6.5 in local. While creating components using CRXDE Lite I am using clientlib for storing js and css files, but the clientlib is not reflecting changes made in the stylesheet and script in real time. It is taking time approximately 30 to 60 minutes to load into the page. I have tried disabling cache but that didn't solved the problem.

 

Please guide to resolve the problem. 

Thanks in advance!!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

139 likes

Total Posts

125 posts

Correct reply

59 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile

Avatar
Affirm 50
Employee
markus_bulla_adobe
Employee

Likes

139 likes

Total Posts

125 posts

Correct reply

59 solutions
Top badges earned
Affirm 50
Boost 100
Applaud 25
Affirm 25
Boost 50
View profile
markus_bulla_adobe
Employee

28-06-2021

Hi @hs06!

 

There are several levels where this behavior could be caused:

  • Please check if the ClientLib is cached in your browser. Trying to hard-reload the clientlib file in your browser (shift+r/cmd+r) or disabling your browser cache (through developer tools) may help here.
  • Are you using the dispatcher? Could the ClientLib be cached in the dispatcher? Please try to directly load the clientlib from your instance and/or clear your dispatcher cache in this case.
  • Please check if the ClientLib is regenerated server-side after code changes. If this is not happening, please try to also touch (e. g. adding a blank/new line) the according .txt files of the clientlib (js.txt and/or css.txt).
  • Using versioned ClientLibs from ACS AEM Commons may also help and is in general a good idea for most non-cloud setups.
  • You may also want to check the internal ClientLib debugger, see /libs/granite/ui/content/dumplibs.html on your local instance. It gives some insights into ClientLib categories and composition and provides features for output testing, validation and rebuilding of clientlibs.

Screenshot 2021-06-28 at 10.11.12.png

 

 

 

 

Hope that helps!

Answers (1)

Answers (1)

Avatar

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

76 posts

Correct reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

76 posts

Correct reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile
Bimmi_Soi
Level 4

28-06-2021

Hi @hs06 ,

 

Have you tried checking in incognito after making the changes.

Check this link too

Versioned ClientLibs (adobe-consulting-services.github.io)

This was implemented to handle this issue. This issue is not related to AEM but is just the way css is cached by the browser.

 

Thanks