As learned from this topic, the Javascript and CSS available in the af.customwidgets are automatically included at runtime, Adobe Experience Manager Help | Create custom appearances for adaptive form fields​ But if multiple sites are sharing the same environment, all would have redundant libraries i...

Hi all, there was a search function of my application, and it works well on AEM 6.1, however, after I upgrade the instance to 6.2, it doesn't work, from the recent request, it stucks at PageSearchServletBelow is the request detail, but strange thing is there isn't any update in the error.log0 TIMER_...

Hi SakshiMy intention is not only to change the appearance of existing AEM Form component, moreover, it should be a new component with different usage.May I know is there any reference document for how to register custom component with $.widget? Cheers

An update for this issue, as collaborated with daycare support, finally they find the root cause and problem is due to heavy computation of the Cell Search Path (CSP). So they provided us an hot-fix for this particular issue, and it is solved now.

An update for this issue, as collaborated with daycare support, finally they find the root cause and problem is due to heavy computation of the Cell Search Path (CSP). So they provided us an hot-fix for this particular issue, and it is solved now.

I've followed this instruction, however, the rendering of widget seems doesn't work, and the $userControl also couldn't be applied.

Hi Guys,I've copied and created a new component based on the numeric stepper, the new component is already registered with $.widget, however, most of the features are there except the rule editor not work, and the value is not submitted when submit the form.I've attached the source code of the new c...

It seems the issue only happened when we nested put particular components together, like we have one component "grid-control-2" and another one "grid-control-3" which are used for controlling page layout to generate two / three grids in one container / section and it was truly built in accordance wi...

Thanks for your help, I checked that we did not use AEM's version of jQuery, so after I included "cq.jquery" in our template, the CSRF error disappeared.So from your advise, it would be better to use AEM's version of jQuery rather than others, isn't it? Cheers,

Dear all,Recently we upgraded our AEM servers from 6.1SP1 to 6.2, and we have a component to build a multiple form container, it is normally on 6.1, however after we upgrade the instance to 6.2, the page always crashed in editor mode.I have analyzed and found the reason is following marked with bold...