Hi,   I’m not familiar with the "journal component." Could you add a screenshot of it? From the GitHub link you shared, it looks like you’re not using the AEM Embed Core Component, which is the preferred method for embedding YouTube videos on any AEM page. There's an out-of-the-box (OOTB) YouTube Em...

Hi @NafNaf    This is a community focused on Adobe Experience Manager which is a different Adobe product. You may receive better support by posting your question here: https://community.adobe.com/t5/fireworks/ct-p/ct-fireworks?page=1&sort=latest_replies&filter=all&lang=all&tabid=discussions. Additio...

Hi, Did you publish your changes after adding the extensions? Try publishing the latest version—it might help identify any conflicts with the extension versions or other issues that Launch can provide more insight on.

Hi @bhap    You are right. This appears to be a bug that should be reported to Adobe. As a temporary solution, you can extend the clientlib and add the missing function so it works correctly until Adobe releases a hotfix.  

Hi,   I don't think there's anything that directly updates the dispatcher files, if that’s what you're asking. These are two separate areas for the sake of all of us. What is typically done is using Sling servlets to inject headers, but this is specifically for adding extra headers to a request. Thi...

Hi,  There might be missing clientlibs required for those functions to work. In any case, is there anything preventing you from using vanilla JS to achieve the same result? Using vanilla JS is preferable, so something like this should work:   fetch('/apps/ax.json') .then(response => response.json(...

Hi,   I'm not sure it makes sense to adapt the core component to leverage this "AMP" framework. You would need to update the markup and JS with the necessary AMP-specific markup, styles, and behavior. It might be easier to just create a new custom component and integrate AMP there. In any case, you ...

Hi,  You should follow this guide; https://experienceleague.adobe.com/en/docs/experience-manager-screens/user-guide/administering/dispatcher-configurations-aem-screens what issue are you seeing in the logs? Are you sure this is issued in the dispatcher layer? 

Hi, Are you running this into AEM 6.5? Can you try with the latest version of the BPA ?

Hi,    I’m not sure if I understood correctly, but the legacy configs are meant to store data in nodes under a specific path. So, you can definitely create your own new UI and store the data wherever you need. You can check out these examples on how to do that:   https://medium.com/@vsr061/create-cu...