Adobe Experience Manager Sites

Describe the bugAfter deploying Asset Share Commons (ASC) and the sample content package to the DEV environment, all assets (both sample and custom) appear in search results and the pages render correctly.However, asset thumbnails are not loading.All other functionality — search, filters, pagination, and design — works as expected.⸻Environment• AEM Version: AEM 6.5.21• Asset Share Commons Version: 3.11.4• Environment Type: Author and Publish⸻To Reproduce1. Install Asset Share Commons package on AEM DEV environment.2. Install the official ASC sample content package.3. Open /content/asset-share-commons/en/light.html (or similar page).4. Observe that all assets are listed properly.5. Notice that the thumbnail images are missing — broken image icons are shown.⸻Expected behaviorAsset thumbnails (from DAM renditions such as cq5dam.thumbnail.319.319.png) should display properly in the search results and asset cards, just like on the local AEM instance.Additional context• The issue occurs for

<enableCollasableText jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/form/checkbox" class="cq-dialog-checkbox-showhide" cq-dialog-checkbox-showhide-target=".button-option-enable-showhide-target-three" name="./show" text="Show Below Conatiner" uncheckedValue="false" value="true"/><collasableTextContainer jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/container" class="hidden button-option-enable-showhide-target-three" showhidetargetvalue="true"> <items jcr:primaryType="nt:unstructured"> <showFirstName jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="First Name" name="./firstName"/> <showLastName jcr:primaryType="nt:unstructured"

Hi, I’ve been trying to create a custom plugin for all the RichText XML configurations in my AEM components, but I haven’t been able to get it working. I’ve followed several guides, but I still can’t make it work. Any help? It would just be a simple select with options and a text field.We’ve added custom fields to components like the link plugin — that was quite easy by modifying only the JS. But in this case we would be creating a completely new property. https://www.bounteous.com/insights/2022/01/06/custom-rich-text-editor-plugins-adobe-experience-manager/#create_new_clientlib_provide_categories https://medium.com/globant/build-a-custom-rte-plugin-with-chatgpt-for-aem-4e373487a6fe 

I created a new AEM SPA project using archetypeVersion=36 with absolutely no custom code — it’s a completely clean, out-of-the-box project.The pages render correctly, but the AEM error log keeps showing this warning: GET /content/demoproject/us/en.model.json HTTP/1.1]org.apache.sling.models.impl.via.ResourceSuperTypeViaProviderCould not determine forced resource type for JcrNodeResource,type=nt:unstructured, superType=null,path=/conf/demoproject/settings/wcm/templates/spa-page-template/structure/jcr:content/cq:responsiveusing via value Is there any way to fix this warning or prevent it from appearing?

I want to trigger listener which which further sends email whenever any async job is completed on AEM Cloud.But whatever event I am trying is not hitting the listenerorg/apache/sling/event/notification/job/FINISHED Orcom/adobe/granite/async/job/SUCCEEDED. or I have the 2nd approach where I can check /var/asyncjobs where if any new node creates I can trigger listener but in that node I see no property to differentiate between jobs( like I only want for assetimport or zip unarchive). can someone please help here.  

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

Hello, I am trying to integrate the Adobe web SDK via the AEM; however, alloy calls are encountered, indicating that the currently configured Datastream ID does not exist. How do I enable the data stream ID for my AEM?

Currently, if I update metadata that already exists in the standard path /jcr:content/metadata, everything works correctly with this payload:json{ "class": "asset", "properties": { "metadata": { "pruebanumber": 22, "singleline": "Value from API" } } }The ProblemThe problem occurs when I try to update metadata that belongs to a child node named default, whose path would be:/jcr:content/metadata/default/myFieldIf that node does not already exist in the asset, the API returns a 403 Forbidden error.Example of the payload that fails when the default node does not yet exist:json{ "class": "asset", "properties": { "metadata": { "pruebanumber": 22, "pruebasingleline": "Value from API", "default": { "indefault": 1234 } } } }If I manually create the node or update a field from the asset's Properties in the UI, the defau

We are currently evaluating migrating our AEM 6.5 implementation to the Cloud Service. However, we’ve encountered a few issues and would appreciate input from organizations that have gone through similar transitions: 1. AMS and Cloud Service - Tech Parity Adobe is recommending AMS, but it means additional operational and development costs.  AMS has not received new features at the same pace as AEM Cloud. If our organization wants to adopt new features, especially at a global scale, AMS would not have tech parity. So, features may not be available for China. Has anyone faced this situation? How did your organization overcome these limitations? 2. Asset Share Commons and Content Hub User Limits Currently, we use Asset Share Commons (ASC) with no user limits. Migrating to Content Hub imposes a 250-user limit, which seems highly restrictive. For those who migrated from ASC to Content Hub, what other challenges did you face besides the user limit? Any advice on scaling Content

Hello, as per my organization policy i can not use my company mail id so i am trying to login via my personal mail id and it is showing that "It seems that your Adobe ID is not linked with your Adobe Experience Cloud solution accounts.Please get in touch with your Org Administrator or Adobe Enterprise Support." Please help me with the solution. 

Hi everyone, I hope you're all doing well.Context: I'm managing groups and permissions in AEM. Each group has its own access to specific folders in the DAM. The problem I'm currently having is that if a new folder is created, it becomes visible to all users. My question is: is there a way to automate permission assignment? For example, if I create a "promo" folder and it's assigned to specific users, or if I create a folder in a specific location, could I use workflows to specify that the folder is for a specific group? Thanks for your input.

Hi AEM Community, I'm working on migration project , migrating from classic UI to touch UI. we have one button on siteadmin navigation bar called "start workflow" when clicked content tree dialog will open first where user where dialog will open with selected page(s) will show along next and cancel button if user selects next button then workflow model screen will load where model will be prepopulated. To achieve same in touch UI I have create a button at /apps/wcm/core/content/sites/jcr:content/actions/secondary/wokflow-button and below is xml<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:granite="http://www.adobe.com/jcr/granite/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"jcr:primaryType="cq:Page"><jcr:content jcr:primaryType="nt:unstructured"><actions jcr:primaryType="nt:unstructured"><secondary jcr:primaryTy

Hi community,I need to retrieve all metadata fields that start with a specific prefix (e.g., nameMetadata_) from all metadata schemas in AEM.Current situation:I'm currently using this endpoint to get fields from a specific schema:{{Instance}}/conf/global/settings/dam/adminui-extension/metadataschema/default.infinity.jsonWith a script, I can process the JSON and filter the metadata fields I need, but this endpoint only points to the default schema. What I've tried:I know I can use:/conf/global/settings/dam/adminui-extension/metadataschema.infinity.jsonThis endpoint returns all schemas, but it requires iterating through each one and querying their fields individually.My question:Is there a more direct endpoint or method that allows me to:Retrieve in a single JSON all metadata fields from all schemas (even those not currently in use)?Or alternatively, is there a way to filter directly by field name (e.g., nameMetadata_*) through a query parameter or selector?Basically, I'm looking to

Thank you so much to Andrea Hardeman and Warren Barton for sharing their expertise on the Assets View UI and how it can enhance your workflows!     If you missed the event, we’re including the recording and slides below. The deck, in particular, outlines some different use cases for Admin View UI (Touch UI) and the Assets View UI. Andrea talks through these at the beginning of the event and then Warren offers an insightful demo!    There were tons of great questions – we're working on getting those compiled, answered, and we’ll be posting those here when they’re ready. Stay tuned!    Slide deck  Webinar recording    Update: the Q&A has been posted below (I broke them into 6 comments to help space them out a bit). HUGE thanks to Andrea and Warren for tracking down answers on all 60 questions!!

I'm facing same issue, currently migrating AEM Forms repository from TFS to GitLab using the following command:git push --mirror GitLaberror: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413It seems to fail due to a HTTP 413 (Request Entity Too Large) error, possibly because of the repository size.Has anyone encountered a similar issue when pushing large repositories to GitLab?What's the best way to resolve this?Regards,Nagendra

deleted

Session Details Live from Basel! Legacy CMS platforms weren’t built for the AI era. See how Adobe Experience Manager’s Agents modernize enterprise websites—migrating legacy infrastructure into agent-optimized environments built for AI-native content discovery. Learn how AI agents automatically migrate, enrich, and standardize content for generative engines, handling block implementation and design generation to reduce time-to-launch. Through live demos, explore how developers can collaborate with AI agents using natural language to generate optimized, modern experiences in minutes—freeing teams to focus on innovation and business value. Schedule November 11, 2025 — 10:25 AM – 10:45 AM (CET) Speakers Giorgia Fiscaletti — Cloud Reliability Engineer, Adobe Moderators Adobe Products AEM Full Schedule View Here Q&A Use this thread for related questions.

Is it possible to link my Adobe ID with my Adobe Experience Cloud solution accounts as a frelancer AEM Developer? I would install it in a cloud service to learn/experiment installation process.

Hi Community, We recently deployed a code package to our Cloud production environment, but unfortunately the deployment contained a bug that is now impacting users. We raised a P1 ticket with Adobe Support, and their recommendation was to revert to the previous working code.However, Adobe has also mentioned that we must redeploy - either by fixing the issue and deploying a corrected version, or by redeploying the last known stable code.Could someone please clarify the proper way to revert code in AEM Cloud Service?Is there an Adobe-recommended method to roll back to a previously deployed version? Thanks in advance!

I have to pull tags from page properties and add into dialog tagfield while dialog is loading using js.i wrote below script for the same but its adding single field (last index) not all which are in loop.if i directly set array without loop, it will show in single field in dialog while loading.Can someone help me here? $(document).on("dialog-loaded", function (e) {         let currentPagePath = window.location.pathname.replace("editor.html/","").replace(".html","");        $dialog = e.dialog;        var $dialogContent = $dialog.find(dialogContentSelector);        var dialogContent = $dialogContent.length > 0 ? $dialogContent[0] : undefined;         if (dialogContent) {retrieveLocationData(currentPagePath);            for (let i = 0; i < locationTags.length; i++) {    $dialog.find(locationsTagsDialog).adaptTo("foundation-field")

Are you planning your AEM Assets & Workfront native connector integration? Or maybe you're just looking to refine your current implementation? Join Adobe Champion Autumn Earle and Workfront expert John Lemme next week on Thursday, November 13th to learn from your peers who have already done the work.  On this webinar, Autumn and John will share step-by-step processes, including detailed in-product screenshots and videos, to help you avoid common pitfalls in the implementation process so that you can get the native connector live and operational smoothly. You'll also get access to a number of valuable planning resources that will help you align stakeholders, refine your integration strategy, and get to value more quickly. What You’ll Learn: A step-by-step overview of the integration implementation process Best practices for metadata field mapping between AEM and Workfront Key roles and personas needed for a successful rollout ____ This webinar will soon be available on-demand

Hi all,Some component folders under /apps/myproject/components aren’t getting deployed even though they exist in ui.apps/src/main/content/jcr_root/apps/myproject/components.Here’s my filter.xml:<workspaceFilter version="1.0"> <filter root="/apps/myproject"/> <filter root="/content/myproject"/> </workspaceFilter>I rebuilt (mvn clean install) and redeployed to local + Cloud, but still missing those folders.Could this be due to how filter.xml handles subpaths or exclusions?Do I need to explicitly include those component paths or adjust filters to fix it?