Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Editconfig listeners of nested components do not fire correctly

Avatar

Level 2

Summary

Example setup: I have two very simple components, components A and B. Component A contains 3 instances of component B. Component A uses a _cq_template to set some default properties for it and its children when it is dragged onto a parsys.

Issue: When a user drags component A onto a parsys, I expect the cq:listeners in its _cq_editConfig to fire, and they do not. The listeners do fire for the last the instance of component B, but not all of them nor for component A. In addition to that, when I drag component A into a parsys, it does not allow me to edit it (there is no blue border around it when I place my mouse cursor over it). This is also the case for the B components, with the exception of the one who's editConfig listeners fired.

How to reproduce

In order to reproduce this issue, create two simple components as described (one of them must contain instances of the other, and they must use cq:template to set default values). Dragging your component into a parsys will demonstrate the issue as described above.

1 Accepted Solution

Avatar

Correct answer by
Level 10

http://stackoverflow.com/questions/7260134/extjs-4-event-handling-tutorials

This will point you in the direction on where to learn more about Ext-JS events. This is the library that CQ widgets are based. 

View solution in original post

3 Replies

Avatar

Level 10

can you put some screenshots with your listeners

Avatar

Correct answer by
Level 10

http://stackoverflow.com/questions/7260134/extjs-4-event-handling-tutorials

This will point you in the direction on where to learn more about Ext-JS events. This is the library that CQ widgets are based. 

Avatar

Level 2

You mean screenshots of the code?