Hi @SwathiKr3, One way to approach this is by looking at how image profiles are assigned. Since image profiles can be applied at the folder level, the simplest option is to keep the assets with the specific profile in a dedicated folder and then give your user group modify/replicate rights only ther...

No, option 1 (request attribute) won’t persist across multiple publishers.If you need the value available across requests regardless of which publisher is hit, you’ll need to rely on the cookie itself (or another mechanism that goes back through the client and load balancer).

Hi @MeasurableBusinessResults, I think, for your case you don’t really need to duplicate page templates - you can solve it in two main ways: Use Context-Aware Config (CAC):Put a config at the site/language root that says where the header/footer XF should live. Then, when the page renders, the compo...

Hi @vashishth47, In your dispatcher config, the wildcard *.adobeaemcloud.com is not being matched. The RDE validator doesn’t allow unrestricted wildcards. You need to explicitly list the exact hostnames that Cloud Manager assigns to your RDE Publish service. Example: ServerAlias publish-p124507-e12...

Hi @SanaQu, Yes as you mentioned on a Cloud you can’t edit indexes directly - everything has to be deployed through code, and only Lucene indexes are supported. The right way to do this is: Define your custom index under /oak:index in your codebase (set type=lucene). If you need to change it later...

Hi @Neha_Jadhav, You can use AEM’s Query Builder or JCR-SQL2 to search for components within pages.Example Query Builder JSON: { "type": "nt:unstructured", "path": "/content", "property": "sling:resourceType", "property.value": "myproject/components/xyz" } This will give you all nodes where...

Hi @jayv25585659, It depends on why you need the updated cookie during the same request: Store the updated value in a request attributeAfter you update the cookie on the response, also do: request.setAttribute("cookieXUpdatedValue", "ABC,DEF"); Then, in your Sling Model (or later code in the sam...

Hi @SanaQu, A few other areas might be worth looking into: Dispatcher cache - Quite often XF rendering issues are related to stale or inconsistent cache at the dispatcher. If you flush the cache for the XF path or the page where it’s embedded, does it render correctly afterward? That might explain ...

Hi @NageshRaja, The aemanalyser-maven-plugin resolves against the latest available SDK API unless pinned. If you’re using the default plugin configuration, Maven may be pulling the newest version from Adobe’s repo, not the one in your property. Another dependency (e.g., uber-jar, project BOM, or p...

The message is basically saying that AEM isn’t finding any valid offers inside the experience when it tries to sync to Target. In other words, the campaign object it builds ends up empty, so it skips the sync. Since you’ve already confirmed the XF is mapped, published, and bundles are the same acros...