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.
AEM 6.3: resourceSuperType parsys using newpar.js not loading list of components in edit mode.
I've been using a custom component 'grid-row' that has 'wcm/foundation/components/parsys' as a supertype
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0"
xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:description="Grid Row"
jcr:primaryType="cq:Component"
jcr:title="Grid Row"
sling:resourceSuperType="wcm/foundation/components/parsys"
allowedParents="[*/*parsys]"
componentGroup=".hidden"/>
In the 'grid-row.html' I do the following:
<sly data-sly-use.parsysComponent="parsys.js" data-sly-list.paragraph="${parsysComponent.renderInfo}">
<div class="grid-12 grid-row" data-sly-test="${!paragraph.columns && paragraph.resourceType && paragraph.cssClasses}">
<div data-sly-test="${!paragraph.columns && paragraph.resourceType && paragraph.cssClasses}" class="${paragraph.cssClasses}" data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType, decorationTagName=''}"></div>
</div>
<div class="grid-12 grid-row" data-sly-test="${!paragraph.columns && paragraph.resourceType && !paragraph.cssClasses}">
<sly data-sly-test="${!paragraph.columns && paragraph.resourceType && !paragraph.cssClasses}" data-sly-resource="${paragraph.resourcePath @ resourceType=paragraph.resourceType, decorationTagName='div'}" />
</div>
</sly>
As you can see this code is really similar that that of the '/libs/wcm/foundation/components/parsys/parsys.html'.
I'have also overridden the newpar folder inside my grid row, but those files did not change any bit from 6.1 -> 6.3
newpar > .content.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0"
xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:primaryType="cq:Component"
jcr:title="New Paragraph - Sightly"
sling:resourceType="wcm/foundation/components/parsys/newpar"
componentGroup=".hidden"/>
Now here is my issue, in AEM 6.1 this was was all I had to do to make this work the content author could just drag new components into the 'grid-row'. In AEM 6.3 the list of components doesn't seem to load until there is a 'wcm/foundation/components/parsys' somewhere on the page.
How do I know this? Some of the already existing pages have also have the 'grid-row' and inside components that include a 'wcm/foundation/components/parsys' in their html, If I remove that line the list of components is just empty.
This is the html rendered within the ContentWrapper element, I am not sure if it is helpful:
<div class="grid-12 grid-row">
<div class="new section cq-Editable-dom">
<!--cq{"decorated":true,"type":"/apps/platform-company/components/layout/grid-row/newpar","path":"/content/platform-blueprints/company/nl/pages/testing/jcr:content/top_page_parsys/*","selectors":null,"servlet":"Script /apps/platform-company/components/layout/grid-row/newpar/newpar.html","totalTime":1,"selfTime":1}-->
<cq data-path="/content/platform-blueprints/company/nl/pages/testing/jcr:content/top_page_parsys/*"
data-config="{"path":"/content/platform-blueprints/company/nl/pages/testing/jcr:content/top_page_parsys/*",
"slingPath":"/content/platform-blueprints/company/nl/pages/testing/jcr:content/top_page_parsys/*.html",
"type":"wcm/foundation/components/parsys/newpar",
"isResponsiveGrid":false,
"csp":"general|base|page/top_page_parsys|grid-row|parsys/*|newpar",
"editConfig":{"actions":[CQ.wcm.EditBase.INSERT],
"disableTargeting":true}}">
</cq>
</div>
</div>
Is somebody else also experiencing this problem or am I doing something wrong? Thanks in advance!
I am not trying to create a custom grid component really :S I am just trying to get my custom parsys to work on page level:
My example - General page:
....
<sly data-sly-resource="${'content' @ resourceType='/apps/company/components/layout/grid-row'}" data-sly-unwrap></sly>
...
It seems that the above is not enough for AEM to load the possible components:
Once I replace it by the following it does load my components:
...
<sly data-sly-resource="${'content' @ resourceType='wcm/foundation/components/parsys'}" data-sly-unwrap></sly>
...
I don't thinks this has anything to do with a custom column component but just with AEM not recognizing my grid-row as a valid parsys in wich components can be dragged into. I have no idea what changed between 6.1 > 6.3 that caused this to stop working.
