Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Blaiirrr
Community profile Blaiirrr Level 2
Front End Web Developer
New Zealand
8 BADGES
Level 2

Level 2

Learn more
Joined the community 04-05-2020 4:03:45 PM
Offline
Top badges earned by Blaiirrr
Customize the badges you want to showcase on your profile
Re: EAEM Edit-In-Fullscreen script causing errors
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
@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.

Views

147

Like

1

Replies

0
Re: EAEM Edit-In-Fullscreen script causing errors
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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.

Views

164

Like

1

Replies

0
EAEM Edit-In-Fullscreen script causing errors
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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 ...

Views

186

Likes

0

Replies

4
Re: Proxy component throwing error (Uncaught TypeError: window.CQ.CoreComponents is undefined)
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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...

Views

348

Likes

0

Replies

2
Re: Proxy component throwing error (Uncaught TypeError: w...
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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...

Views

413

Like

1

Replies

0
Re: Proxy component throwing error (Uncaught TypeError: w...
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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...

Views

418

Like

1

Replies

0
Proxy component throwing error (Uncaught TypeError: window.CQ.CoreComponents is undefined)
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
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...

Views

481

Likes

0

Replies

8
Betreff: Hi - total noob here (and hope I'm asking this question i...
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
Well - color me stupid! It looks like I did miss a step because I didn't even have a .m2/settings.xml file. I've created it as instructed and now my build errors are no more 🙂, and I see my Hello World component updates too. Many thanks for your responses, and I apologize for wasting your time.

Views

6.4K

Like

1

Replies

1
Betreff: Hi - total noob here (and hope I'm asking this question i...
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
Yes - all steps up to that point went well. My response is a little different to the documentation, but 'adobe-public' is there. C:\Users\bmackint\.m2\repository adobe-public-releases Adobe Public Releases https://repo.adobe.com/nexus/content/groups/public never false adobe-public-releases Adobe Public Repository https://repo.adobe.com/nexus/content/groups/public never false adobe-public-releases Adobe Public Repository https://repo.adobe.com/nexus/content/groups/public adob...

Views

6.4K

Like

1

Replies

3
Hi - total noob here (and hope I'm asking this question i...
Avatar
Boost 5
Level 2
Blaiirrr
Level 2

Likes

7 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Boost 5
Give Back 5
Ignite 1
Establish
Give Back 3
View profile
Blaiirrr
- Adobe Experience Manager
Hi - total noob here (and hope I'm asking this question in the right place). Just working my way though the WKND setup and am getting a Build Error when running "mvn -PautoInstallBundle clean install" in the /core folder:[ERROR] Failed to execute goal on project aem-guides-wknd.core: Could not resolve dependencies for project com.adobe.aem.guides:aem-guides-wknd.core:jar:0.0.2:The following artifacts could not be resolved: com.adobe.aem:uber-jar:jar:apis:6.5.0, org.apache.commons:commons-imaging...

Views

6.5K

Like

1

Replies

5
Likes given to
Likes from