Lightbox issues with the DAM - not working on publish

[scott_kilmer]

Hey everyone, I've got a clean version of AEM 6.0 installed as a DAM server with author and publish instances running. Unfortunately, I've run into an issue where the lightbox action works fine in author but is dead as a doornail (Halloween reference) in publish.  Any thoughts on what might be causing the disruption?

Many thanks in advance!

-Scott

[Mshaji]

Have you checked for any errors in firebug or chrome developer? If you find any error, it will be good.

Make sure you have code and content in publish as activate. Else explain more what you are doing with code snippets and where it is failing

[Lokesh_Shivalingaiah · Accepted solution]

In most of the cases, if a functionality is working in author and not in publish will lead to a check on the package published from author to publish. In case of Lightbox which works mainly with JS, there might be two reasons

1. clientlibs might not be pushed to publish instance. Even its pushed, replicate once more just to make sure there is no cache.

2. conflict with the multiple version of js. You should be able to find if you debug.

[AmitVishwakarma]

To resolve the lightbox issue with DAM not working on the publish instance:

1. Replication: Ensure that the assets from the Author instance are properly replicated to the Publish instance. You can check replication logs for any errors.
2. DAM Permissions: Verify that the permissions for assets on the Publish instance are correctly set up. The assets might not be accessible if they haven't been replicated or if there are permission issues.
3. Dispatcher Cache: Clear the dispatcher cache on the Publish instance, as the lightbox functionality might be cached incorrectly.
4. Check URL Mappings: Ensure the correct URLs for the assets are being generated on the Publish instance. Sometimes, links may resolve to Author URLs which do not work in the Publish environment.
5. Debug Logs: Check the logs for any errors related to the lightbox component or DAM resources on the Publish server.

If these steps don't resolve the issue, consider verifying the setup and configurations across both instances and performing a thorough review of how assets are being handled between Author and Publish.