@jsmsrinivas Did you find a solution to this issue? I am facing the same issue now.

Currently using AEM Core components v2.18.0I am trying to leverage the OOTB functionality for generating the Alternate Languages for page meta tags. I see the OOTB code under /apps/core/wcm/components/page/v2/page/head.links.htmlBelow is the piece of code which is responsible for generating it.<link...

We are in the process of migrating from AEM foundation form component to new Core components. We have lot of constraint validation like Alphanumeric Validation and few Validation which involves DB calls.Is it possible to create a Server side validation on AEM Core Forms components like form Input te...

Hi, I have a component with has a parsys inside it.Now on breaking the  inheritance on a page for this component works flawlessly as expected. Now for a different requirement i am provided a path, but i need to check if the provided path's inheritance is broken or on. How to achieve that?FYI: I have...

Hi,We are in the process of upgrading from AEM 6.2 to AEM 6.4 (SP4) We use OOTB forms (The old forms - /libs/foundation/forms). We used to have links in the validation message to direct users to our support if forms fail to submit but now it is showing the HTML instead of the link.Anyone else faced ...

Hi Scott,This is the below code i am using private Session session = null;private ResourceResolver resourceResolver = null;try {resourceResolver = resolverFactory.getServiceResourceResolver(null);session = resourceResolver.adaptTo(Session.class);//do some processing} catch (Exception ex) {} finally ...

Hi, Did you find a solution for this?

Hi,We have upgraded our instance to AEM 6.4.3, After the upgrade, any component which has more than 1 xtype:tags throws the below exception in the console.Anyone encountered it? Attached the screenshot of the error

Hi,We recently upgraded from AEM 6.2 to 6.4, We noticed that there is a lot of repository restructuring required for AEM 6.4One such restructuring included moving /etc/designs/<site> to /apps/settings/wcm/designs/<site>In 6.2 we used to store few static images under /etc/designs/<site>/img/, since w...

We are in the process of converting all the dialogs to Touch.We noticed that in the classic UI: We could use /bin/wcm/foundation/forms/constraints.jsonSample:<constraintType                    jcr:primaryType="cq:Widget"                    fieldLabel="Constraint"                    name="./constrain...