How can we verify ?Check Content Fragment Configuration: Ensure that content fragments are properly configured in your AEM instance. Make sure they are enabled and allowed to be included in launches. You can check the configuration in the "Content Fragment Models" console. having similar issue - my ...

Thank you @Jineet_Vora @EstebanBustamante will try the suggestions and update here.

While working a website on AEM 6.5 (SP 6.5.19) ,We have the default Sitemap working as https://domain.com/sitemap.xml A requirement was to create custom sitemap url's and not the default ones as:https://domain.com/sitemap-cards.xml (show all pages from the path https://domain.com/cards.html )andhttp...

This has been resolved with Adobe tech support help.1. Adobe support worked with the engineering team to clear the cache and set the CM_DISABLE_BUILD_REUSE (https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/getting-started/project-creation/project-setup.html) so that a...

Not a solution/answer yet, I have a support ticket with Adobe, working through this issue. Will post the solution the sooner we are able to solve this.

Thanks @Shashi_Mulugu 1. I did add the dependency in "/project-root/all/pom.xml"2. Earlier tried placing "repository" folder in the project root, but think Maven when using ${project.basedir} is referring to "/project-root/all" so moved "repository" under "/project-root/all".

Having similar issue to this https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cloud-manager-deployment-content-package-not-getting-deployed/m-p/411723  We need to integrate Phrase for our site translations. And have configured as instructed by Phrase here https://support.phr...

  Re this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/where-is-the-i18n-translator-ui-for-aem-cloud/td-p/400530 assuming Translator (<sever>/libs/cq/i18n/translator.html) is deprecated/not-to-be-used.   We have a component where we need to use i18n strings for name on ...

Thanks @arunpatidar  We are using Core Components XF. And that should have picked the correct ones.   The issue for us is that we were using custom site properties to pick the Header, Footer and other XF's. Now it is resolved for us.

How can we make a particular language copy of the main site refers/use the respective Experience Fragments in a similar language/folder structure? Docs here https://experienceleague.adobe.com/docs/experience-manager-core-components/using/get-started/localization.html?lang=en#example states they are ...