Blaiirrr

Re: EAEM Edit-In-Fullscreen script causing errors - Adobe Experience Manager 07-07-2021

@kchaurasiya - I'm using v6.5.5.0. The Configure (wrench) icon has been disabled/removed so the only way to edit is the Edit (pencil) icon, and since the script in question bypasses the 'normal' editing screen the only option I have is the full-screen editor.

226

Re: EAEM Edit-In-Fullscreen script causing errors - Adobe Experience Manager 07-07-2021

Hi @kchaurasiya - I don't see anything in error.log related to editing the Text component. There's only the error in the browser console.

243

EAEM Edit-In-Fullscreen script causing errors - Adobe Experience Manager 07-07-2021

Hi all - I recently implemented the 'fix' for opening the RTE in full-screen mode by default, by following these instructions - http://experience-aem.blogspot.com/2016/07/aem-62-touch-ui-rich-text-editor-inplace-editing-open-in-fullscreen-editing-start-event.html - but it seems to be causing issues with the 'system' code that loads font styles (and possibly other functionality).If I edit a Text component (via the 'pencil' icon) without this script in place (then click the Fullscreen icon) I see ...

265

Re: Proxy component throwing error (Uncaught TypeError: window.CQ.CoreComponents is undefined) - Adobe Experience Manager 01-07-2021

Thanks for posting @jordanl32063034 - are you working with a 'webpack setup' too?Yes, this is basically what I experienced. I had eventually tracked down the initial error related to the deep-linking function and 'disabled' it so I could continue testing (knowing that I would need to re-enable it later), but there were simply more CQ errors found in the other (editor/editorhook) scripts.For now, a colleague has found a fix for a basic third-party Accordion component so am moving forward with tha...

717

Re: Proxy component throwing error (Uncaught TypeError: w... - Adobe Experience Manager 24-06-2021

Hi @Ritesh_Mittal - thank you for your response. I'm trying to keep the proxy component as clean and simple as possible. I get the 'CQ' JS errors in both editor and preview (see my other response to vmdala), and am just hoping to get the OOB component working as intended - then I may look into customizing the HTML and CSS (and possibly JS).I think all of our other components are custom (created by the third party) so have not seen any other proxy/core components working or otherwise.I've just ru...

782

Re: Proxy component throwing error (Uncaught TypeError: w... - Adobe Experience Manager 24-06-2021

Thanks @vmadala - I haven't added any files besides webpack.include.js (which I notice none of the Adobe 'proxy component' documentation mentions). As I mentioned, even just creating the single node (below) produces the 'CQ' JS errors in editor and preview - when it seems like this should basically work straight away. I'm pretty sure I just need to find a way to get the OOB JS to load/run correctly in our 'webpack' environment - note that I don't even really know what this means since I'm new(is...

787

Proxy component throwing error (Uncaught TypeError: window.CQ.CoreComponents is undefined) - Adobe Experience Manager 23-06-2021

Hi - I've been struggling with my proxy Accordion component for a few days now. I've tested many different scenarios with varying degrees of success. From the simplest setup with only the single component node (allowing everything from /libs to be referenced), to copying all files (from GitHub) to my proxy component - I'm always getting JS errors in my browser console (depending on the scenario, the errors are related to window.CQ, CQ.CoreComponents, or Coral being undefined). Note that I can su...

850

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe