Adobe Experience Manager

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for March 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:W

Check out the list of AEM User Group meetings happening in April:🌷 [VIRTUAL] April 15 @ 12pm ET: "Adobe Summit Prep 2026: Know Before You Go" with AEM - Midwest Chapter🌷 [VIRTUAL] April 28 @ 10am ET: "Adobe Summit 2026 Recap – focused on AEM Assets" with the AEM - Global DAM Chapter🌷 [VIRTUAL] April 30 @ 2pm IST: "AEM APAC Office Hours: Adobe Summit 2026 Recap" with AEM Champion Office Hours👉 See you there!: https://aem-augs.adobe.com/events/#/list

Adobe's MCP servers are great. But what if you could build AI tools designed exactly for your business or development use-case?In my latest article, I show how to custom-build MCP integrations in TypeScript so AI tools like Claude or Cursor can:🗂️ Find and act on expiring DAM assets in plain language⚡ Bulk update metadata without juggling the UI🔍 Query logs with natural prompts like “show errors from the last 4 hours”🔗 Chain multiple operations in one smart prompt And the best part? It works for on-prem, AMS, and AEMaaCS setups - all tailored to your deployment, letting AI do the heavy lifting while keeping you in control 🎯 Check the article here: https://medium.com/@vorajineet/aem-mcp-your-way-design-business-specific-ai-tools-for-any-aem-deployment-ff66c3fde22dLink to Github: https://github.com/vorajineet/aem-mcp-server

Adobe photoshop is failing and wont reinstall

trying to execute "aio login" and result is:Visit this url to log in: https://aio-login.adobeioruntime.net/api/v1/web/default/applogin?id=********&port=*****&redirect_uri=https%3A%2F%2Faio-login.adobeioruntime.net%2Fapi%2Fv1%2Fweb%2Fdefault%2Fapplogin%2Flogin-success - Waiting for browser loginnode:events:497 throw er; // Unhandled 'error' event ^ Error: spawn undefined\System32\WindowsPowerShell\v1.0\powershell ENOENT at ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) Emitted 'error' event on ChildProcess instance at: at ChildProcess._handle.onexit (node:internal/child_process:291:12) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { errno: -4058, code: 'ENOENT', syscall: 'spawn undefined\\System32\\WindowsPower

I have a repeatable panel in an Adaptive form built on core components, with a remove button inside the panel and an add button outside. When I use the rule editor to configure the remove button to delete a panel instance, it consistently removes the panel below the one I selected. For example, if I add three panels and try to delete panel 2, panel 3 gets deleted instead. While this could have been resolved using the Code editor, that option isn't available to me. My constraints are that we're working within a headless delivery model, so I can't use guidebridge, and custom JS functions aren't feasible because they would require passing the SOM expression, making the JS form-specific. Given these limitations, I would appreciate any suggestions on how to address this issue. 

How do I create a custom API on AEM so that any external system (ex: postman, curl) can access the API via some authentication(OAUTH/SAML). Once the handshake is done external system needs to send AEM some data, AEM will do some business process and pass a response.

Edge Delivery Services has changed the game for Lighthouse scores, but the authoring experience is now the big conversation. I’m looking to gather some real-world perspectives on the best 'flavor' of authoring for AEM Edge Delivery Services (EDS).​i see we have three distinct paths and I'd love to hear from anyone who has moved between them:​Pure Document Authoring (Google Drive/SharePoint): The speed is unmatched, but how are you handling complex governance at scale?​DA.live (Document Authoring): Is this the 'Goldilocks' zone for asset integration, or does it add an unnecessary layer?​Universal Editor with AEM Sites: For those who need MSM and heavy localization, does the performance of EDS still feel 'magical' when coming from a full AEM Cloud Service backend?​Which combination have you found offers the best balance of author velocity and developer sanity? Looking forward to your insights!" 

We are running an EDS implementation using document-based authoring via da.live with Fastly CDN. Our blog section uses three custom blocks:blog-grid — paginated card listing with category filtering, tag colour mapping, and authorDate sorting page-list — sidebar block surfacing the most recent posts for the current category cards — category navigation iconsContent is authored in da.live and published through the standard EDS content bus. The query index URL is resolved dynamically at runtime via /config.json using getConfigValue('query-index').The Problem:All three blocks render entirely client-side via JavaScript. On the initial HTTP response, the page shell delivered to crawlers looks like this:html<div class="blog-grid"> <div><div>Pagination-limit</div><div>10</div></div> <div><div>Title</div><div>Category Name</div></div> <div><div>Guides</div><div>bg-guides</div></div&g

Hi All, I am trying to set up universal editor in my local and usinig AEM Cloud Service SDK (aem-sdk-2025.9.22758.20250928T092442Z-250900) for local development.I have done below set upAEM - http running on port 4502AEM - https running on port 8443Local universal editor service running on port 8000Trusted the local certificate in the browser for self signed certificatesThe problem I am facing is,when I try to load AEM page running on https (port 8443) inside universal editor, it gives this error "Blocked autofocusing on a <input> element in a cross-origin subframe." I followed whats mentioned in this document - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/developer-overview?lang=en for same site cookie settings but it doesn't help and I continue getting the cross origin error. Has anyone come across the same issueThere is no Universal editor service related configuration available

I am running my AEMaaCS local SDK and I keep getting ERROR likecom.adobe.aem.wcm.dataplane.rewriter.MetaTagExternalPageIdTransformer authorSourceLocator is null. AEM_SERVICE env var is missing or malformedI am starting the AEM instance with java -jar aem-author-dev-p4502.jar -r author,dev,localI tried setting AEM_SERVICE = “author”environment variable (in addition to other vars I am setting), but it does not helpIt may be harmless, but its polluting my logs and is annoying when trying to find real errors.Whats the proper value to set, to silence this? 

Hi all,I hope you are doing well! This is continution to while upgrading to AEM 6.5 LTS i’m facing challenges with guava library replacement/alternatives.as per the LTS analyzer guidance, “The `15.0.0.0002` bundle version of Guava is no longer available out of the box in AEM 6.5 LTS due to critical security vulnerabilities. Please update and use latest non-vulnerable version of guava.”, so started with using latest versions with no vulnerabilities.<!-- Source: https://mvnrepository.com/artifact/com.google.guava/guava --><dependency>    <groupId>com.google.guava</groupId>    <artifactId>guava</artifactId>    <version>33.5.0-jre</version>    <scope>compile</scope></dependency> This is working at Java side but not at AEM instance, because there is no such library provided by Adobe runtime, so we need to embed this ourselves in our application generated bundle, this is failed because ‘com.google.guava’ bundle is a multi-rele

We are using Universal Editor with Edge Delivery Service, I would like to know how to customise the OOTB text styles available in Text Default content type. For this particular example I would like to add more options to add alignments.  It's not possible to apply any customisations inside RTE fields through the json model.Could you advise on the problem?

Hi everyone,I’m currently working on setting up an Edge Delivery Services (EDS) site using an Adobe repository and would appreciate some guidance.My goal is to: Set up a new EDS project using the official Adobe repository Configure the required integrations to create and load the website using AEM Sites authoring Create pipelines, deploy the site, and preview content I’ve gone through the documentation, but most of the references are based on using a public GitHub repository. In my case, I’m working with a private repository (Adobe repo).At the moment, I’m facing an issue with site ownership verification. Even after adding the required verification file, the verification is not successful. Currently, my repository only contains this verification file and does not yet include files like fstab.yaml or other standard EDS configuration files.It would be really helpful to understand the correct approach for private repository setups, EDS site creation, especially around ownership verifi

Hi everyone,I am working on extending the AEM Rich Text Editor (RTE) to add custom functionality for tables. Specifically, I want to add two buttons to the table toolbar: Cell Background Color (origintable#cellbg) Cell CSS Class (origintable#cellclass) I have implemented a custom Plugin and Command using CUI.rte.plugins.Plugin and CUI.rte.commands.Command. While the current implementation works using window.prompt, I would like to know if this approach is considered "best practice" or if there are more "AEM-native" ways to handle this (e.g., using Coral UI dialogs instead of browser prompts).Current Implementation Details: Plugin Registration: Using CUI.rte.plugins.PluginRegistry.register. UI Initialization: Adding elements to the tableEditOptions toolbar via tbGenerator.addElement. Data Persistence: Manually triggering the change event on the editable container after updating the DOM via jQuery. Code Snippets:1. Plugin Logic (cell-bg-plugin.js):(function ($, CUI) { 'use stric

Some of our authors reporting intermittent issue (like once a month per user behavior) while authoring pages in our internal prod author.Issue is that they are not able to save component dialogs in middle of authoring work even though they are able to login and navigate through pages. They get error failed to submit form. Upon clearing cache for all time and logging in again only is fixing this issue. Same time they are able to edit and save using other browser.upon checking HAR file we see that the csrf token request is giving 403 response (I think only post calls are not getting authenticated) and on further checking their login-token cookie is missing in the browser. This issue is not getting solved until they clear cache for all time and force login back.Is there any reason why the login-token OOTB cookie get dropped or not being set for a logged in session (even though the user is logged in and can navigate through pages and even can see component edit dialogs)?Below are some log

Hello Everyone, We have observed an inconsistency between the Content Fragment Editor and the Universal Editor regarding enforcement of Content Fragment model constraints.A multi-value field  in our Content Fragment model is configured with Maximum number of items = 3.In the Content Fragment Editor, this constraint is respected and authors are prevented from adding more than three entries. In the Universal Editor, the same field allows adding a fourth item, and the value is persisted without any validation error. After saving from the Universal Editor, reopening the fragment shows all four values stored in the repository.This suggests that the Universal Editor does not currently enforce the max items constraint defined in the Content Fragment model.Please confirm:Whether this behavior is expected or a known issue If there are plans to align Universal Editor validation with Content Fragment model constraints Whether any server-side validation or configuration is recommended to prevent t

Hi, To resolve "Deprecated Service User Mapping Detected", I created the following file under the osgiconf of the ui.config"org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.cfg.json"Following are its sample content. {   "user.mapping": [        "com.adobe.acs.acs-aem-commons-bundle:twitter-updater=[serviceuser--com.adobe.acs.acs-aem-commons-bundle--twitter-updater]",         "aem-precompiled-scripts:scene7-asset-reader-service=[serviceuser--aem-precompiled-scripts--scene7-asset-reader-service]"     ]}Does it look good to resolve the "Deprecated Service User Mapping Detected"? Or is there anything more to do?  

It would be extremely helpful if the Adobe Cloud Manager UI displayed clear information on which user initiated a pipeline execution as well as which user approved or rejected the pipeline in the approval step.Today, identifying who triggered or approved a pipeline often requires navigating through logs or API calls, which is not intuitive. Having this information surfaced directly in the Cloud Manager interface would provide:Better traceability – Quickly identify the person responsible for starting a deployment or making an approval decision. Improved auditability – Essential for teams that must comply with governance, security, or compliance standards. Faster troubleshooting – When a deployment causes issues, teams can easily see who initiated or approved the pipeline and follow up with the appropriate individual. Enhanced collaboration – Team members and stakeholders can more effectively coordinate by knowing who has taken action at each stage.Displaying the triggering user and the