Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

AEM 5.6.1 embedded client libraries compilation issue.

Avatar

Level 2

Hi Guys,

We currently have an issue with embedded client libraries often breaking when changes to CSS or JS have been made, and also when deploying packages to publish.

We have a workaround, which is to rename the client library and rename it back. This gets it to recompile and work.

Is there a known cause for this?

Something which we can do differently to prevent the need for this fix.

We have had this issue since 5.4, and even the adobe help desk did not come up with an answer.

Thanks

Damian.

1 Accepted Solution

Avatar

Correct answer by
Level 10

Seems like custom issue or related to less. File an support ticket by attaching "com.day.cq.widget" to Loglevel DEBUG & repeating test case.

View solution in original post

5 Replies

Avatar

Employee Advisor

Hi Damian,

so you change a single CSS or Javascript file, and this change isn't reflected in the respective clientlib? Do you see any suspicius messages when you set "com.day.cq.widget" to Loglevel DEBUG?

kind regards,
Jörg

Avatar

Level 2

Hi Guys.

 

We are running "5.6.1", but have had this issue since "5.4".

I am assuming it is caused by changes to JS and CSS that are embedded. It happens from time to time in auth, and almost always in publish when we deploy.

It's not that the client library is not reflecting the changes, it's that it stops working altogether. We have to get it to recompile by renaming and renaming it back.

Thanks.

-Damian

Avatar

Correct answer by
Level 10

Seems like custom issue or related to less. File an support ticket by attaching "com.day.cq.widget" to Loglevel DEBUG & repeating test case.