Custom WIdgets not working in AEM 6.0 | Community

Level 4

Solved

Custom WIdgets not working in AEM 6.0

Forum|Forum|10 years ago
October 16, 2015
6 replies
2037 views

Hi Everyone,

We are migrating cq5.61. to AEM 6.0.

After upgrading, Any of the dialogs which uses custom widgets (custom multi fields) are not opening and gets the below error.

uncaught exception: cannot create Component: xtype 'ejstcustom' not found and no default supplied

Please help!!!

Thanks in Advance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by smacdonald2008

See this community article - it explains how to use custom xtypes in AEM 6:

http://helpx.adobe.com/experience-manager/using/creating-touchui-xtypes.html

Adobe Employee

What is the category of the client library in which your custom widget is defined?

Level 10

Hi There,

Thank you for reaching out to Adobe Community,

See if the below forum thread helps:

Error in creating a custom widget in dialog

Thanks!

smacdonald2008Accepted solution

Level 10

See this community article - it explains how to use custom xtypes in AEM 6:

http://helpx.adobe.com/experience-manager/using/creating-touchui-xtypes.html

Level 4

Hi Shekhar,

Thanks for the quick reply. I have gone through the link.

I have implemented the same way. My custom multifields works well in classic ui. But does not work in touch ui.

Level 4

Am using the Custom category. But i have dependency as cq:widgets.

Do i need to have cq:widgets as category????

Will it not work in above case cq:widgets as dependency????

Adobe Employee

In the TouchUI, the compatiblity iframe into which an ExtJS dialog is rendered has these client library categories loaded (amongst others, but these are the most "popular":

cq.wcm.edit
cq.widgets
cq.security
cq.tagging
cq.cloudserviceconfigs
cq.dam.scene7

This compatibility iframe doesn't know anything about your custom category.

See /libs/cq/gui/components/authoring/compat/components/dialogwrapper/html.jsp for the implementation details.

Regards,

Justin