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 s...

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 c...

Ahh, I see its down to being an anonymous user which explains why it works in auth. Thanks alot guys.

Thanks, I'll update that. It does work in our auth environment though, and there is the other issue so I'm not sure it's the root cause.

Yes, it seems to complain about that in most cases. However it does seem to complain about pageHelper.getClasses(currentPage). Which is why i moved my investigation from templates to the currentPage object.

Hi,I hope you can help.We are currently in the middle of upgrading from 5.4 to 5.6.1 and its all gone quite smoothly with the testing in the authoring environment. However, when the components are deployed to the publish server there are a lot of exceptions thrown. On referring back to the code all ...

Hi I hope somebody can shed light on an issue i am having in CQ 5.6.1.I have an issue referencing images in the DAM from client libraries stored in components. The URL path is incorrectly altered when the client library is generated.The URLS are of the format.url("/content/dam/company/emea/sprites/h...