Resource dumped by HtmlRendererServlet error while moving the Parsys Component

[swapnan73983825]

Hi Community,

We are getting the below error when we are trying to move the custom parsys component (which has other components configured inside this parsys ) to another parsys.  It is an intermittent issue.  When we are trying to move the parsys, sling:resourceType- foundation/components/parsys property is not getting copied to the moved node. Since the resourcetype is not found the sling is throwing the below error.

Resource dumped by HtmlRendererServlet
Resource path: /content/xx/yy/en_us/testing/Alpha/jcr:content/page_par/pagesection_1735347292Resource metadata: {sling.modificationTime=-1, sling.characterEncoding=null, sling.contentType=null, sling.creationTime=-1, sling.contentLength=-1, sling.resolutionPath=/content/xx/yy/en_us/testing/Alpha/jcr:content/page_par/pagesection_1735347292} 

Resource type: nt:unstructured 

Resource super type: -

But why all the properties are not getting copied when we are trying to move the parsys ?

Please suggest.

Thanks,

Swapna

[smacdonald2008]

Can you please show a screenshot of what components you are trying to move within an AEM page.

[swapnan73983825]

Hi Scott,

Please find the attached screenshots of the error and the components.

We are getting this error only for the component which has resourcesuperType as /libs/foundation/components/parsys, and we are trying to move that component multiple times inside other parsys.

Thanks,

Swapna

[kautuk_sahni · Accepted solution]

Hi Swapna

Please have a look at this community article covering Implementation of nested Paragraph system :-

Link:- http://www.citytechinc.com/us/en/blog/2013/02/limitations_of_the_cq_parsys.html

Examples:- https://gist.github.com/kand/4999238

Thanks and Regards

Kautuk Sahni

[goursing]

above link is not valid , can you provide updated link

[swapnan73983825]

Thanks Kautuk. Will have a look into the links.

[anay_sinha]

Even I am getting the same error. @swapna- Is it solved for you?

[swapnan73983825]

Hi Anay,

Ya, the issue is solved.

We have created custom parsys component. We will get the HTMLRendererServlet if we try to drag and drop the parsys component inside another parsys component. There are few restrictions for parsys component. So in the design mode of custom parsys we have restricted the same custom parsys to be dragged and dropped (Click on Desgin mode from side kick -> Edit the custom parys component -> Uncheck the parsys component from the opened window). This makes sure that the parsys component cannot be added in another parsys component. These changes has solved the issue. Hope this helps you out.

Please refer to the below links mentioned by Kautuk.

Link:- http://www.citytechinc.com/us/en/blog/2013/02/limitations_of_the_cq_parsys.html

Examples:- https://gist.github.com/kand/4999238

Thanks,

Swapna