?debugClientLibs=true in author page | Community
Skip to main content
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 sam_stange

It can be especially helpful for debugging javascript files because AEM will combine multiple .js files and in some cases, minify the js making it very difficult to troubleshoot/debug. Here is a good post of some url tricks for AEM: http://blogs.adobe.com/experiencedelivers/experience-management/cq_developer_tricks/

Hope this helps!

Sam

7 replies

askdctmAuthor
Level 9
October 16, 2015

Hi Feike,

Will check on this and get back to you.

Feike_Visser1
Adobe Employee
Adobe Employee
October 16, 2015

Do you see in your HTML-source the js/css-files separately?

askdctmAuthor
Level 9
October 16, 2015

Hi Feike,

Thank you for your reply.

I did remove the cf# from the url and try. However, could not notice any difference. I guess I am doing something wrong here.

Feike_Visser1
Adobe Employee
Adobe Employee
October 16, 2015

Remove the /cf# in your url

Krishna_C
Level 3
October 16, 2015

AEM merges all the java script files within a Client Library into a single js file.

Using  ?debugClientLibs=true will download all the js files individually making debugging easier. 

 

Krishna

sam_stangeAccepted solution
October 16, 2015

It can be especially helpful for debugging javascript files because AEM will combine multiple .js files and in some cases, minify the js making it very difficult to troubleshoot/debug. Here is a good post of some url tricks for AEM: http://blogs.adobe.com/experiencedelivers/experience-management/cq_developer_tricks/

Hope this helps!

Sam

September 27, 2019

Hi

I tried debugClientLib=true on publish page path, And its trying to load the clientlibs from /apps directory and not able to load due to access restriction while it should load it from /etc.clientlibs path.

Any suggestion?