Adobe Experience Manager

Hi everyone,We originally worked with Teaser v1 for a while now, and only upgraded to v2 to included smart cropping image features. Now I need to extend the Teaser component to support external URLs in the linkURL field, similar to how v1 handled it. In v2, the getTargetPage() method in TeaserImpl is stricter. It attempts to resolve the linkURL to a Page using PageManager, and if it can't, it falls back to the current page or an action CTA. Here's the current implementation in core AEM:@9944223 @126844 protected Optional<Page> getTargetPage() { if (this.targetPage == null) { String linkURL = resource.getValueMap().get(ImageResource.PN_LINK_URL, String.class); if (StringUtils.isNotEmpty(linkURL)) { this.targetPage = Optional.ofNullable(this.resource.getValueMap().get(ImageResource.PN_LINK_URL, String.class)) .map(this.pageManager::getPage).orElse(null); } else if (actionsEnabled &

Hi everyone, I’m working with Adobe Experience Manager Storefront Delivery Services and need to customize my URL structure for categories and products to be cleaner and more SEO-friendly. Right now, my URLs look like this: Categories:https://example.com/categories/maquillaje Products:https://example.com/products/toleriane-purifying-foaming-face-wash-for-oily-skin/ULT0011 The client’s requirement is to remove those prefixes so the URLs become: Categories:https://example.com/maquillaje Products:https://example.com/toleriane-purifying-foaming-face-wash-for-oily-skin/ULT0011 What I’ve tried: Edited fstab.yaml to add redirects from /categories/* and /products/* to the root, but accessing the new paths returns 404.Reviewed the StorefrontRouter and rewrite rules in the archetype, but I’m unsure which configuration files take precedence in Edge Delivery.Checked Adobe docs on URL rewrites, but didn’t find a clear example for removing both prefixes. S

I am trying to build my aem project for a local setup but keep getting this error:"Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm (npm ci) on project com.adobe.cq.cloud.testing.ui.cypress.tests: Failed to run task: 'npm ci' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)" Tried downloading the specific version required for cypress, tried deleting the node-modules folder as well but unable to remove this error. Kindly refer the below screenshots for more information on the exact error:  I am currently using the AEM cloud version, archetype 51 was used to build the project, npm version is 10.9.2 and node version v22.13.1. Kindly provide suggestions on what can be done to remove this error as I have tried with WKND as well as standalone project too. 

Hi everyone,I'm working on a project in Adobe Experience Manager as a Cloud Service, where I have a large number of Content Fragments (CFs) stored in the DAM. I need to copy them into other language nodes, but I'm facing an issue: when I use the language copy feature on the root folder, it also brings over unpublished content and other data that I don't actually need.My goal is to copy only the specific CFs, for which I already have the paths, into the target language folder—without including any unrelated content.So my question is:Is there a way to trigger the copy of these specific CFs via REST API, using their paths, in AEM as a Cloud Service?Or is there a recommended alternative approach to achieve this in a clean and efficient way?Thanks in advance for any suggestions!

I am new to AEM DAM Assets . I am looking for i should apply custom validation to tag fields that i should allow only one tag in selection and show error in dialog. help me out how should i do custom validation.Thanks in advance for your response.

Hi all,We are using AEM as a Cloud Service and have configured an Image Processing Profile that calls an App Builder to perform some Photoshop action against some images to generate a specific rendition (e.g., photoshopped.psd, rendition.png) when assets are uploaded into a designated folder.Now, we have a requirement where:Assets are already available in the DAM (in any folder).Authors should be able to manually run a workflow on a selected asset.The workflow should:Trigger the processing profile to generate the rendition (even though the asset is not newly uploaded).Once the rendition is available, separate it as a new asset (this post-processing logic already exists).I want to know:Is there a supported way to invoke a Processing Profile from a workflow step?What’s the best practice for such manual reprocessing scenarios?Appreciate any guidance or experience around this! Thanks in advance.  Regards,Bhavani Bharanidharan

Couldn't edit the pages. All pages facing same issue 

Hello Team, I am using AEM as a cloud service. Created a tag.Created a content fragment. In this, I have few fields along with tag field. I have used the above tag in this CF. Consider that, I have used the tags in few more content fragment as well. Now, I wanted to delete the tags. At that time, it shows that "Total x references for tag "...." Please confirm the action for the tag(s).  Still, I have deleted the tag.Now, when I open the content fragment(in this, I have referred the tag, that is now deleted), this shows error message. "Field contains invalid tag".  Note: Content fragment opened in Content fragment editor UINote: Still, I can modify the tag field or any other fields, which is present in content fragment. Wanted to know, is this expected behavior ?As per my assumption,1: If I try to delete the tags and if this tag has references, it should be deleted from that CF. Or else, author should not be able to delete the tags that has some references.

I am currently installed this workbench version(6.5.0.20220219.1.12345) on local. Also installed both 32-bit and 64-bit versions of the Microsoft Visual C++ Redistributable packages as prerequisite.Seeing below error while opening AEM forms designer post workbench installation. Chatgpt provides following root cause for this issue. The error code "0x000007b" typically indicates a problem with the application trying to start, often related to issues with system libraries or dependencies. This error can occur if there are mismatches between 32-bit and 64-bit versions of libraries or if required components are missing. Has anyone encountered this similar issue ?

Hi team, I need to update supported language for tag so was trying to add it thru code for cq:Tag node but that did not work and then try to add it thru package installation it is also not working can anyone guide me to do this? Thank you Umesh Thakur

Hi, I was hoping someone can help clarify the support levels for this integration, specifically which versions it's supported on? Does that include both on-prem and AEMaaCS (including and after 6.5.19+)?  We had some conflicting messaging from Adobe Support and the published documentation located (linked below), while Adobe Support (on a current ticket) has indicated that this is not supported on-premise.  Can someone provide clarity?  Configuring the Submit action | Adobe Experience Manager Additional reference here: Solved: Help with SharePoint Integration in AEM 6.5.19 - Adobe Experience League Community - 644749Thank you in advance!-Martin

Hi Team, Currently I am working on a AEM cloud based project. In my project we are currently using a customized text component which had a color picker plugin using which content author is able to use while authoring the text (RTE) component. Currently the color picker is visible only when the RTE dialog is maximized view (refer image-1). But the new requirement is to make the color picker should be visible when the RTE is normal view (refer image-2). Please find the attached screenshot and let me know. Thanks & best regardsTapas                                                                                                                                  &

I’m facing an issue in AEM 6.5.19 where only the first 50 Content Fragment Models (CFMs) are indexed and available for GraphQL persistent queries.   My project currently includes 53 CFMs, but the last 3 models are not indexed after a Maven-based deployment. As a temporary workaround, I manually publish the missing CFMs, which triggers their indexing. However, this solution is not sustainable, as the issue reappears after every deployment.   Has anyone else encountered this limitation? Is there a way to configure AEM to index all CFMs (more than 50) automatically after deployment? Any suggestions or proven solutions would be appreciated.

Requirement is to get list of pages published in last week only from a specific workflow  only .  To get list of all completed workflows , I am referring JSP code present here -- /libs/cq/workflow/admin/console/components/datasource/workflowinstancedatasource/workflowinstancedatasource.jsp . "resource" (used at line 43 ) is getting injected here by Sling script engine during rendering but how can we get this "resource" in a Sling Job consumer service class ?  

Hi, I'm trying to run the aio cloudmanager:org:list command, it returns a blank response — no organizations are listed. C:\>aio cloudmanager:org:list Org Id Org Name Roles Active ────── ──────── ───── ────── Additionally, when I try to use workspace-related commands like aio console workspace:select or aio console project:select, I get a 403 Forbidden error. This is the example error it's throwing. C:\>aio console project:select » Error: [CoreConsoleAPISDK:ERROR_GET_PROJECTS_BY_ORG_ID] 403 - Forbidden » ({"id":"1234jsd-123md-123-456-asei122","messages":[{"template":"ERR_MSG_OPERATION_NOT_ALLOWED","message":"User XYZ@AdobeID » is not allowed to access resources of org 123"}]}) C:\>aio cloudmanager:org:select » Error: [CloudManagerCLI:NO_CM_ORGS] No Cloud Manager authorized organizations found. » Code: NO_CM_ORGS Everything was working fine for me earlier, but suddenly I'm no longer able to access it.If this issue is related to permission, c

 Hi all,I'm working on an AEM component and trying to get a property from the dialog using Sling Models. Here's a snippet of my code:@Model(adaptables = Resource.class)public class MyComponentModel {@586265private String title;public String getTitle() {return title;}} However, when I try to use this model in my HTL file like this:<div data-sly-use.model="com.myproject.models.MyComponentModel">${model.title}</div> The title is always showing as null, even though I have set it in the dialog. Can anyone help me understand what’s going wrong?

Hi everyone,I am facing an issue in OOTB page property "Advanced tab -> Robots tags" field in we-retail project. Please provide your input on this issue.In We-retail project, I am checking 2 pages --> Language Masters - /content/we-retail/language-masters/en/experience/test and CA EN live copy - /content/we-retail/us/en/experience/test. I added "noindex, follow" values in "Robots tags" field and rolled out this page. In crx/de, I am able to see the live copy has "Robots tags" field value as "noindex, follow" but I am not able to see the changes in Page Properties - http://localhost:4504/mnt/overlay/wcm/core/content/sites/properties.html?item=/content/we-retail/ca/en/experience/test. In language masters Page Properties - http://localhost:4504/mnt/overlay/wcm/core/content/sites/properties.html?item=/content/we-retail/language-masters/en/experience/test, I am able to see the "Robots tags" value correctly.

Hi Team,Can we implement showing or hiding a text field based on radio button selection in AEM core component forms?Core components FormsAEMasCS Thanks,Roy

Hi Everyone, I'm currently working on an Edge Delivery Services (EDS) project using XWalk and trying to fetch data from an AEM GraphQL endpoint. Here’s the simplified JavaScript logic I’m using:const isAuthor = window.location.hostname.includes('adobeaemcloud'); const domain = isAuthor ? '' : 'publish-pxxx-exxxxx.adobeaemcloud.com'; const endpoint = '/graphql/execute.json/eds-dummy/faqs'; const url = domain ? https://${domain}${endpoint} : endpoint; const response = await fetch(url); const data = await response.json();I also followed the steps outlined in the Publishing pages with AEM Assets article and applied the following changes:Updated paths.json:{ "mappings": [ "/content/eds-dummy/:/" ], "includes": [ "/content/eds-dummy/", "/content/dam/eds-dummy/" ] }Set Cloud Configuration for the DAM folder (/content/dam/eds-dummy/): Went to Assets → /content/dam/eds-dummy/ Opened Properties → Cloud Services Set the Cloud Configuration to /conf/eds-dummy and saved. After applying these conf

Hi everyone,We're kicking off a new AEM project from scratch, and the requirement is to use Angular for the frontend. By default, the Angular version is set to 9 when scaffolding the project, but we needed a more recent version — so we upgraded Angular successfully, and the build completes without errors.However, we're facing a few issues:The Angular components are not rendering on the pages.Component mapping doesn’t seem to be working.The clientlibs-angular folder is being generated, but the js.txt file inside is empty.I have limited experience with Angular, so I’d really appreciate it if anyone who has gone through a similar upgrade process or encountered these issues could share some guidance or best practices.Thanks in advance!

Does anyone have a glossary/glossentry best practices for translations? The glossentries work great in the source language (English) when we integrate the terms into the text. The glossary entries also create a glossary in the PDF as expected in English. However, for languages where nouns change form (I know conjugate is the wrong word, but it is the closest I can think of) depending on how the term is used in the sentence, the glossary term no longer works as intended. The only thing I can think to do is to remove the glossary term (link) from the sentence and list it at the end of the topic something like, "Glossary Terms Used: glossentry1, glossentry2," where the link is in the topic, but not embedded within the sentence. This, however, would look really awkward in a PDF output. How are glossary entries supposed to be used for translated documents?

Hello everyone,I am currently developing with Adobe Experience Manager (AEM) using the VSCode AEM Sync extension and have encountered the following error message:”path not under jcr_root folder: /home/aem_XXXX/ui.apps/src” This issue arises despite the fact that the specified path ”/home/aem_XXXX/ui.apps/src/main/content/jcr_root/apps/site/www/news-release/clientlibs/clientlib-site/” includes the jcr_root directory.EnvironmentRunning Docker containers on Windows using WSLUsing Ubuntu inside the containerAEM is running fine, and localhost:4502 is accessibleAdditional InformationThe output from VSCode AEM Sync is constantly showing "AEM Sync started... Searching for jcr_root" and it seems not to be detecting the jcr_root correctly.Attempts to ResolveChecked file paths and permissions inside the Docker containerVerified VSCode workspace settings (workspaceContains:**/jcr_root/**)I would appreciate any advice or solutions to this issue, especially any tips on setting up paths when usi

 Hi everyone,I'm integrating Angular with AEM and trying to render a simple Angular component. The build runs fine, clientlibs-angular is generated correctly, and the JS files are included using:<cq:includeClientLib categories="myproject.angular" />In my HTL file, I have:<div class="angular-hero"> <app-hero></app-hero> </div>Angular component:@8220494({ selector: 'app-hero', template: `<h1>Hello from Angular Hero!</h1>` }) export class HeroComponent {}But nothing renders on the page, and no errors show in the console. What could I be missing?Thanks in advance!

Hi,I would like to set up metadata driven permissions on Assets so I figured out that OOTB feature should exist based on the documentationhttps://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/metadata-driven-permissions#:~:text=Enabling%20Metadata%2DDriven%20Permissions%20involves,assets%20with%20specific%20property%20values.However when i set up locally (using the latest SDK available) it is not working - I am not able to see the property I configured in the json appearing in my permission section.Does anyone else have the same issue?Thanks,Andrijana

Hello,   We are noticing an issue where Image presets created in AEM 6.5 and are not auto-publishing to Dynamic Media.  We have tried recreating the Dynamic Media configurations, but no luck.   Please suggest if anyone has encountered a similar issue.