Hello @Sanjay_Bangar,Thanks for your responseAlthough I'm not sure I follow, do you mean to put those rules into a specific path context?The rules I was referring to are the following:<assetNode assetReferenceAttribute="fragmentAReference" resourceType="resourceTypeC"/> <assetNode assetReferenceAttr...

Hello everyone, We are facing an issue while creating a language copy via a translation project with a page which references two different content fragments.Scenario:AEM 6.5.8In Page C properties there are two references to two different content fragments.Content Fragment A and Content Fragment B. T...

Hi,You could use the list component from AEM Sites Core Components as an example.It has a conditional rendering depending on the source selected.https://github.com/adobe/aem-core-wcm-components/tree/master/content/src/content/jcr_root/apps/core/wcm/components/list/v2/list

Hi,Agree with Karl515-ZrIyBv​ on providing more details.Supposing that reference component has a backend side, for example a sling model, you could decide if, the path property of the component is empty, use a default path instead.

Hello,As an idea, If you are using editable templates the header and the footer experience fragments could be added on the template using the experience fragment component.That component should be extended and customised in a way that is capable of, depending on the page language, retrieve the local...

HelloIf you already have everything needed on AEM (templates, page component(s), components), you could generate a JSON file (as an example http://localhost:4502/content/we-retail/us/en/experience.infinity.json) with the data you want to migrate placed on the AEM counterpart components.Then using th...

HiThe problem seems to happen only when the inline edit mode is used1. Open inline edit mode2. Launch fullscreen view3. All plugins should be shown4. Minimize fullscreen view5. Cancel edition6. Open inline edit mode again7. Launch fullscreen view8. Some of the plugins are missingOtherwise if in the ...