The user sync between publisher pods is handled out-of-the-box (OOTB) in AEM as a Cloud Service, but this configuration is not enabled by default. Please raise a support ticket to enable the user sync between publish pods. Regards,Albin https://myprofile.albinsblog.com

I assume you are referring to enabling the login for the publisher (live sites). Please refer to the post below for more details. Enable User Authentication for AEM Websites — Azure AD B2C | SAML Application with Azure AD B2C | by Albin Issac | Tech Learnings | Medium Enable User Authentication for ...

If you are looking for a solution within AEM, you may follow the below steps. Create a separate client library; refer to this blog for more details https://medium.com/tech-learnings/multi-tenancy-theme-support-for-ui-frontend-module-adobe-experience-manager-aem-256921313c9dCreate a page-level Proper...

Maybe you can explore this option. Create a placeholder component in AEM with required dialogs - this component will only have a DIV, and the dialog data is added to the DIV as an attributes.Create a wrapper component in AEM that uses the external component and renders through the data stored in the...

@MarkEv You should be able to achieve this through Dispatcher(Vhost) configurations and Sling Mapping; refer to the following post for more details - Configure Sling Mappings for Resource Resolution in Adobe Experience Manager(AEM) — Deep Dive | by Albin Issac | Medium Regards Albin www.albinsblog.c...

Thanks, @Martin_Buergi_Adobe for the response

H @kautuk_sahni  Thanks for the gems session; very informative and helpful.I have a quick question on adopting the react commerce frontend components while integrating AEM with the SAP Commerce Cloud (Hybris).In my understanding, the Front end commerce components are built based on Magento-specific ...

Please refer to the following URL to get more details on enabling Anchor - https://youtu.be/EVXOqv6b3lURegardsAlbin Iwww.albinsblog.com

One option to add the resource type as cq/Page so the servlet can be accessed directly on page nodes, in this case, the servlet will be invoked for all the pages irrespective of the page resource type specified in jcr:content node.RegardsAlbin Iwww.albinsblog.com

Thanks, @Sandeep6 for the feedback, the resource type is tagged to the jcr:content node of the cq:page so the _jcr_content should be included to invoke the servlet. Anyhow the HTML extension is invoking the servlet without adding the _jcr_content to the request path. Let me know if you need any furt...