I have a container-like component that has a parsys and it is often nested several deep on my 6.3 site that is migrating to 6.4.8. However, when I have a page that has four of these nested components, the 6.4 touch ui doesn't let me add any components to the parsys of the inner-most component. I can nest four of these components on a page but I can't nest anything inside the fourth one. My pages use /etc/designs and aren't yet using policies under /conf. The sling:resourceSuperType of this component is "foundation/components/parbase". It appears 6.4 has some kind of parsys nesting limit. Is there a way to override or control this nesting limit in 6.4?
Views
Replies
Total Likes
Our short term solution to this problem was to take the AEM 6.3 version of /libs/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js and install it as an overlay at /apps/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js in 6.4. Its hasPlaceholder method was refactored in 6.4 but was misinterpreting the DOM structure of our pages. We were told by Adobe day care this issue is fixed in 6.5.
Views
Replies
Total Likes
Views
Replies
Total Likes
Our short term solution to this problem was to take the AEM 6.3 version of /libs/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js and install it as an overlay at /apps/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js in 6.4. Its hasPlaceholder method was refactored in 6.4 but was misinterpreting the DOM structure of our pages. We were told by Adobe day care this issue is fixed in 6.5.
Views
Replies
Total Likes
Views
Likes
Replies