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.

A console error while adding/updating policies of component in template

Avatar

Level 4

I have a template (Header n footer) and added a component to it through page component.

When I tried to open structure of the template and add/change a policies of that component, on save it is throwing below error (in the back-end the policies are updated) and not redirected template’s ‘structure’ page.

 

 

Uncaught TypeError: Cannot read properties of undefined (reading 'slingPath')

    at self.readParagraph (core.min.5963ca087d6aad66e2a1b3d7a4af39db.js:460:33)

    at process (core.min.5963ca087d6aad66e2a1b3d7a4af39db.js:716:216)

    at constructor.doRefresh [as execute] (core.min.5963ca087d6aad66e2a1b3d7a4af39db.js:716:364)

    at ns.design.Dialog.onSuccess (template.min.d9e4586a03daaf05c6948c1604ac28be.js:25:431)

    at execute (core.min.5963ca087d6aad66e2a1b3d7a4af39db.js:675:165)

    at HTMLDocument.handleDialogSuccess (core.min.5963ca087d6aad66e2a1b3d7a4af39db.js:674:386)

    at HTMLDocument.dispatch (jquery.min.3e24d4d067ac58228b5004abb50344ef.js:124:359)

    at k.handle (jquery.min.3e24d4d067ac58228b5004abb50344ef.js:118:65)

    at Object.trigger (jquery.min.3e24d4d067ac58228b5004abb50344ef.js:122:489)

    at HTMLDocument.<anonymous> (jquery.min.3e24d4d067ac58228b5004abb50344ef.js:137:230)

 

 

I tried multiple things, changing the template resource type, checking with different components ..etc, none of them helped.

Anyone help me to understand that what am I miss configured here?

3 Replies

Avatar

Level 6

Hi @Rajumuddana can you share the part of the code as well where slingPath is coming undefined?

Avatar

Level 4

Hi All,

 

Thanks for your responses.

In this use case, I was including my resource in html like below,

<div class=“para”>
                <sly data-sly-resource="${@path=‘para’, resourceType=‘abc/components/content/paragraph'}"/>
            </div>

But if I move this inclusion to template structure, the issue is fixed.

Screenshot 2024-07-22 at 07.41.34.png

 

so, as per my understanding, we should follow the second way(though first approach also rendering components properly) to include component to avoid further complications.