Adobe Experience Manager Sites

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

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.

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

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

Hey All,Need your expert opinion on an Adobe Target + AEM Cloud setup.Currently, our AEM homepage is built using a single layout container (all components inside it). Because of this, Target (VEC) sees it as one DOM block, making it difficult to: 1. Reorder components 2. Inject experience fragments 3. Run personalisation without custom JS We are considering a few approaches - 1. mBox container for injection 2. Custom JS to reorder components 3. Nested layout containers (split page into sections) 4. Converting sections/components into Experience FragmentsAdditionally, we have three different user types, where the homepage content varies based on the user. One approach I am considering is to create user-specific content as Experience Fragments, export them to Target, and let Target handle the personalisation. On the AEM side, I would provide designated containers on the homepage where Target can inject the relevant content.From an Adobe best practices perspective, what would you recommen

I am trying to create configuraion to purge workflows which are older than 100 days for AEM as clouds service.Documentation -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maintenance Above link says to create a node under /conf where as the link below asks you to create node under /apps for maintenance window.Sample configuration - https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-25921#environment  I'm trying to determine the correct way to create a maintenance window. I used the sample configuration and it worked, but after reviewing the documentation for second time, I realized that the maintenance window is supposed to be created under /conf. So what is correct place to keep this configuration?

This is a weird one.  I created a new component. No problems with it in AEM Local or lowest environment Dev.   It was present in the Design mode. I could enable it on my page. I could then add it to the page in Edit mode. However, in the Stage environment, the new component is simply missing. If I look in crx/de, the component is not there in the menu.Anyone have any idea what might have happened?  Or what sort of error messages might help me debug?thanksFiona

I have a requirment where we have a listing page with restaurants (cards). There is a filter and when end user select single filter example cuisine=french. im able to fetch the data from graphql query and return the CFs which has a tag called french. Now if end user selects multiple filters like french and italian then i need to show all the CFs which has tags french and italian through graphql. I have tried multiple ways but im getting null valuessample query:query getDiningList( $langcode: String,$tag1: [String], $tag2:String,$offset: Int,$limit: Int) {  diningList(    includeVariations: true    _locale:$langcode    offset: $offset    limit: $limit       filter:{        _path:{        _expressions:[          {_operator: STARTS_WITH,value:"/content/dam/test/cfm"}        ]        },      cuisineTag:{         _logOp:OR        _expressions:[{_operator:CONTAINS , values:$tag1}],      }        locationTag:{           _expressions:[{_operator: CONTAINS, value:$tag2}]        }    }  ){     

We’re excited to celebrate Arun Patidar ( ​@arunpatidar ), who has been named the 2025 Community Member of the Year for the Adobe Experience Manager community!   Arun is a big reason why the AEM community is such a helpful and welcoming place. Through his consistent participation, thoughtful responses, and deep product knowledge, he has supported countless community members as they work through challenges and get more value from Adobe Experience Manager.  Whether he’s answering tough technical questions, sharing practical tips, or helping move conversations forward, Arun always shows up with generosity and care. His contributions make a real difference and help strengthen the collective knowledge of the AEM community. The Community Member of the Year recognition celebrates individuals who go above and beyond to support others, and Arun truly embodies that spirit. Please join us in congratulating Arun by sharing your appreciation in the comments below. We’re grateful for everything he d

Hi everyone,I’m facing an issue with one of our Content Fragment Models in AEM where a few text fields were intentionally disabled using disabled=true and renderReadOnly=false at the field node level under /conf/<project>/settings/dam/cfm/models/<model-name>/jcr:content/model/cq:dialog/content/items/textfield. In the old Content Fragment Editor (Granite UI), these fields appear correctly disabled and are not editable, but after moving to the new Content Fragment Editor (which is React-based and built on Adobe React Spectrum), the same fields appear editable and authors are able to modify them. It seems the new editor doesn’t respect the traditional disabled or renderReadOnly properties that used to work in the old UI. Could someone please guide me on how to make these fields appear disabled or read-only in the new React Spectrum–based Content Fragment Editor? Any official documentation or best practice would be really helpful. Thanks,Abhishek A.

Hi all, Kindly point me a to a tutorial for each of a simple Content Fragment and an Experience Fragment (with just two fields, say name and address)Creation of Content/Experience Fragment Model Creation of Content/Experience Fragment from it and populating the fields with values. Process of Exposing it via GraphQL API Any Sling Model required ? If so its Code. Usage in AEM Front End (Sighly) with code.. I want to follow along this tutorial along and see this working. A similar tutorial for Experience Fragment also will help. Appreciate all your responses. Thanks,RK.