Adobe Experience Manager Sites

In my dispatcher_httpderror log, I keep getting the following messages. Fri Oct 10 23:59:24.646793 2025 [managed_rewrite_maps:debug] [pid 123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check in progressFri Oct 10 23:59:24.650947 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] No managed rewrite maps configuredFri Oct 10 23:59:24.655150 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check DONEFri Oct 10 23:59:24.659466 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Waiting for 30 seconds for next managed rewrite maps check I am not using any Apache RewriteMap directive on my setup.These errors pollute my log and have no value, how can I get rid of them?And I want to keep the debug level, so that I can see the REAL errors 

dialog  I add checkout  ，I expect to have initial values when the component is not edited<boutiqueCheckoutjcr:primaryType="nt:unstructured"sling:resourceType="granite/ui/components/coral/foundation/form/checkbox"uncheckedValue="true"name="./boutiqueCheckout"text="Open in new window"value="{Boolean}false"/> html 中我打印<div>232323========${properties.boutiqueCheckout}</div> Output results on the final page<div>232323========</div>  How should I renovate it,

Hi everyone, I’m currently preparing for the Adobe Experience Manager Architect Master certification and I’d like to get some clarity on the level of depth needed around Cloud Manager and DevOps practices. My background is mainly in solution architecture and implementation design, but I’m not always the person configuring pipelines or managing deployment environments directly. For those who have taken the AD0-E117 exam, how in-depth does it expect you to go regarding: Pipeline setup & quality gate configurationEnvironment sizing / scaling considerationsDeployment strategies and Cloud Manager best practicesShould I focus on conceptual knowledge and design-level reasoning, or is a hands-on understanding of specific pipeline configuration steps expected? Any guidance or study approach tips would be greatly appreciated. Thanks!

I’m running AEM 6.5.21 (on-premise) and have fully configured IMS via Tools > Security > Adobe IMS Configurations - the setup is healthy and shows connected.However, the “Sign in with Adobe” button is missing from the login page. I have tried digging into the documentation, but found very less about it. So I need your guidance to implement this.

Hello Team, Is there any latest blogs/articles about the certification course: AD0-E117AEM Sites Architect Master exam I was going through this articlehttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-architect-certification-preparation-ad0-e117/m-p/652522#M163451 cc @arunpatidar @sureshdhulipudi @kautuk_sahni @lukasz-m @aanchal-sikka  @raja_reddy  Thanks in advance 

 Unable to successfully add type='module', expected the following result   

Hello Community, We're encountering an issue affecting a specific user group. These users already have Read, Modify, Create, and Delete permissions for the page. They can edit and update components authored on the page and add new components as well. However, when trying to update the page properties, none of the fields or tabs in the page properties are editable. When attempting to save the page, the users receive the following error: org.apache.sling.api.resource.PersistenceException: Unable to commit changes to session. This issue does not occur for admin users. Granting additional ACL privileges resolves the issue, but we are not supposed to grant such permissions to this group. Additionally, users are able to update the page properties of child pages without any issues, and those child pages use the same template and permissions. The root page is not locked, and users with the same permission level have previously been able to update the page without any problems.&n

When to Use Content Fragments vs Experience Fragments in AEM? by @daniel-strmecki   Introduction In Adobe Experience Manager (AEM), reusability is key to creating scalable and efficient digital experiences. Many teams begin by focusing on components, but components alone can only go so far. They define layout and functionality, but often blend content with design. This makes it difficult to reuse information consistently across multiple channels, websites, regions, or campaigns. That’s where Content Fragments and Experience Fragments come in. These two tools let us separate content from presentation in complementary ways. When used correctly, they help deliver consistent brand experiences faster, reduce duplication, and make content easier to manage across all digital channels. Understanding when to use each is essential for building flexible authoring workflows and omnichannel experiences.  Choosing the wrong fragment type for the wrong purpose, however, can

Hi everyone,I’ve noticed that our AEM site has a very low AI visibility score (around 6%). Could this be happening because most of the content is rendered client-side ?If so, what are the recommended approaches in AEM to overcome this issue and make page content more accessible to AI crawlers and indexing tools (e.g., using server-side rendering or prerendering)?zThanks,L

I have a requirement involving two variations: Variation 1 and Variation 2.When the Variation 1 radio button is selected, the Variation 1 items such as isiTitle and isiDescription (multifield) should be displayed, and all other variation items should be hidden.When the Variation 2 radio button is selected, the Variation 1 items should be hidden, and only Variation 2 fields should be visible.like isiTitle1 , isibuttonlabel and isiDescriptionIn another tab, contentDescription should be visible by default.I have the dialog configuration and Sling model ready. Can you please verify and guide me on how to implement this functionality.. Can you please guide me on how to achieve this scenario? I want to implement the radio button show/hide behavior for the variations in the dialog.If you have already worked on this scenario, could you mention where the issue might be fixed and provide the replaced or updated code that I can use?<?xml version="1.0" encoding="UTF-8"?><jcr:root

Hi all,I’m trying to understand how frontend pipelines deploy changes in a cloud environment. Specifically:What is the typical flow of deploying frontend code to the cloud?How are build and deployment steps generally handled?Any explanations, examples, or diagrams would be greatly appreciated.Thanks!

 Hello team, I'm working on an EDS (blocks) based project.In my project, we need to include a color selection plugin that the content author can use when creating the text component (RTE).How can I implement this functionality and include it in the RTE toolbar?

If we add some style for list, then markup is generating as below.<ol><li> <span class = "note"> Sample Text </span></li><li> Sample Text </li></ol>My requirement is to insert the class in <li class = "note">. If we add some style to whole list , then markup should generate as below <ol class = "note"><li> Sample Text </li><li> Sample Text </li></ol>How can i achieve this in RTE? Thanks in advance.

Hi Everyone,I've setup a local Dispatcher for AEM 6.5 using the Adobe generic configuration, and it's working fine. Now I want to switch to using my project-specific Dispatcher configuration folder(which already exists in my project repository) instead of the generic one.I followed this link:- https://medium.com/@toimrank/aem-dispatcher-setup-9dd2cc8cf253 to do generic setup.Could someone please guide me on the proper step to:1. Point the local Dispatcher setup to my project's Dispatcher configuration folder.2. Structure and organize the project Dispatcher files(vhosts, filters, cache, etc.,) correctly3.Integrate it smoothly with the existing AEM 6.5 local env.4. Any best practices or references for project-level Dispatcher setups.I just want to make sure I'm following the right approach before making the switch.This is how my project dispatcher folder structure looks like:Thanks in advance for your guidance!Regards,Gangadhar P 

Hello, We are implementing custom robots.txt which will be maintainable by content authors. the file is located in: "/content/dam/mycompany/config/robots.txt" We implemented following Dispatcher changes and deployed to AEMaaCS env: 1. filters.any# Allow robots.txt /0104 { /type "allow" /url "/content/dam/mycompany/config/robots.txt" /extension "txt"} /0105 { /type "allow" /url "/robots.txt" /extension "txt"} 2. To open file inline, rather than downloading it: in dispatcher/src/conf.d/available_vhosts<LocationMatch "^/content/.*/robots\.txt$"> Header unset "Content-Disposition" Header set Content-Disposition inline </LocationMatch 3. rewrite.rules:RewriteCond %{REQUEST_URI} ^/robots\.txt$ RewriteRule .* /content/dam/mycompany/config/robots.txt [PT,L] Still, the Adobe default robots.file is shown, not our custom one.what seems to be missing? Appreciate your help!Regards,Shruti 

Hi everyone,I am facing an issue with AEM - Dynamic Media (Scene7) integration in our AEM as a Cloud Service environment.Our Dynamic Media configuration under Tools -> Cloud Services -> Dynamic Media Configuration is set to “Publish assets to Dynamic Media server: Immediate”, meaning assets should be uploaded to DM as soon as they’re added to AEM DAM.However, we’re noticing the following behavior:Problem DescriptionWhen we upload assets manually via the AEM DAM UI, everything works fine.The asset syncs to Dynamic Media immediately.Scene7 renditions and public URLs are generated successfully.When we upload assets programmatically (via custom backend code) - using APIs such as: initiateUpload.json(Upload API)AssetManager.createAsset(...) resourceResolver.commit(); the asset gets stored correctly in AEM DAM,but it does NOT trigger the Dynamic Media upload process.As a result, assets uploaded via the backend do not appear in Scene7,and DM renditions/public URLs are missing.

Why Your Sling Filters Don’t Affect Asset Headers in AEMaaCS? by @daniel-strmecki   Introduction When we make a request to fetch an asset from AEM as a Cloud Service (AEMaaCS), our request doesn’t go straight to the AEM Publish instance. Instead, it’s handled by Adobe’s OOTB CDN, which sits in front of AEM Publisher and serves cacheable content directly from the edge. If the asset isn’t already cached, the CDN may fetch it from the cloud storage backend where AEM Assets binaries are stored. This storage layer behaves like a blob store and is fully managed by Adobe. Once retrieved, the response is cached at the CDN and served directly from there. Therefore, AEM Publisher is no longer involved in most asset delivery requests. Because of this new cloud architecture, Sling Filters or Servlets that modify response headers don’t affect CDN-served assets. We can still implement response.setHeader() inside AEM, but unless the CDN explicitly allows that header to be forwarde