Hi @rampai ,   You can allow all origins by replacing the domain with * but generally this is not recommended as it is not too secure. You can try this approach to find the domain from the request and add that domain in the response. With .htaccess you can do it like this: # -----------------------...

Hi @Michael118.,   If this is working in local and not in another AEM environment, then can you please check error logs, is there is any error. Also, Please share more information on the code which you think is not working.   Thanks, Chitra

Hi @MukeshAEM,   By default any unauthenticated user can analyze GrapQL schema using Introspection. Introspection allows us to get information about all the Requests, Mutations, Subscriptions, and Data Types and all other things that are made available to the clients making requests. This informatio...

Hi @Nadia_Mac ,   Please check if this helps - https://experienceleague.adobe.com/docs/experience-manager-learn/sites/integrations/analytics/track-clicked-component.html?lang=en   Thanks, Chitra

Hi @kevingtan,   You cannot include sightly tags in a jsp, however you can include a jsp component in sightly, for example   <sly data-sly-resource="${'par1' @ resourceType='projectname/components/content/foldername/componentname'}"/> where projectname/components/content/foldername/componentname po...

Hi @shaijuseb ,   I was able to clone https://github.com/adobe/aem-guides-wknd.git and build successfully in my local using mvn clean install.   Can you please which version are you trying to build?   Thanks, Chitra 

Hi @SDusane ,   Not sure, if you're still facing this issue. Did you try to see the metadata on your DAM assets, does it still have old tags references?   If the reference is still there, I would suggest to try to re-upload the same asset again and see if the reference gets deleted? By this time, I ...

Hi @Unnikrishnankv,   Please go through below page if this helps https://experienceleague.adobe.com/docs/experience-manager-64/assets/dynamic/troubleshoot-dms7.html?lang=en   And if not, please enable logging as suggested in above article and share some more logs please.   Thanks, Chitra

Hi @kroyal12 ,   In this case, you should reach out to your Technical Account Manager from Adobe or create an Adobe support ticket.

Hi @robertol6836527 ,   In the referred documentation, when it says "exact production environment needs to be duplicated",  the implicit meaning being that the upgraded environment should have the code, content, configs, users and customisations as your existing production environment so that there ...