Hi @smckinley,
Mostly likely becuse of stores the reference metadata.
Here is what you can do:
1. Check if the path actually changed
Go to CRXDE Lite or use Developer Mode -> Inspect the component.
Look for the property that references your CF (usually something like fragmentPath or fileReference)...
Hi @NageshRaja,
Seems like RepoInit executes before ui.content
RepoInit scripts run during the provisioning of the OSGi container, before your content packages (like ui.content) are installed.
That means your /content/myApp/... nodes don’t exist yet when RepoInit tries to set ACLs -> hence the Pat...
Hi @TronWi,
It looks like this issue is non AEM. You’ll get more targeted help by posting this question under the Adobe Acrobat community: https://community.adobe.com/t5/acrobat/ct-p/ct-acrobat?page=1&sort=latest_replies&filter=all&lang=all&tabid=discussions
Hi @CedricHuesler,
Amazing to see this rolling out so quickly.
For AEM on-prem or hybrid customers, is there a roadmap for extending LLM Optimizer capabilities beyond Cloud Service and AMS, or guidance on partial adoption through APIs or connectors?
Also, as we start thinking about “agentic website ...
Hi @Mahesh_Gunaje,
In addition to @giuseppebaglio I’d like to add a few best practices that can make managing a large number of Content Fragment Models even more scalable and easier to maintain.
When dealing with 40–50 CFMs, it’s helpful to think not just about folder structure but also about reusa...
Hi @Mahesh_Gunaje,
You could do this in 2 ways:
1. Check the active CF model path before running your JS
When a Content Fragment opens in the editor, AEM passes the model path in the page’s URL or in the editor’s internal data.You can use that to conditionally execute your script.
(function(document...
@Mahesh_Gunaje
Your Content Fragment Model’s “content reference” field (Logo) is returning a GraphQL type of ImageRef, and in AEM, that type does not include _metadata or metadata fields.
Only Content Fragments have a _metadata property exposed through GraphQL.Assets (images, PDFs, etc.) reference...
Hi @Mahesh_Gunaje,
The GraphQL capabilities are limited to Content Fragments, not Assets.That’s why you’re able to expose metadata and tags for a Content Fragment but not directly for a DAM asset.
Ideally, when you create a GraphQL endpoint, it only exposes:
Content Fragment fields (and references)...
Hi @Karishma_begumSh,
Stemap - make sure your pages output metadata that Coveo can read - easiest via sitemap.
In sitemap XML, include custom metadata:
<url>
<loc>https://www.example.com/mypage.html</loc>
<coveo:metadata>
<title><![CDATA[Page Title]]></title>
<description><![CDATA[Meta ...