Adobe Experience Manager Sites | Community
Skip to main content

Adobe Experience Manager Sites

Welcome to the Adobe Experience Manager Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Experience Manager.

  • 10000+ Total posts
  • 102,432 Total replies
Filter by:
10000+ Total posts
Nilesh_Mali
Nilesh_MaliLevel 3
 Adobe Experience Manager Sites
Java 21: The build is successful locally, but the following error occurs when updating the Java version on AEM Cloud

[BUILD] Running maven build command(s)Using Java version 21 from .cloudmanager/java-version.Executing command mvn --batch-mode org.apache.maven.plugins:maven-dependency-plugin:3.1.2:resolve-plugins06:49:47,547 [main] [INFO] Scanning for projects.........06:51:04,568 [main] [INFO] Toolchain in maven-compiler-plugin: JDK[/usr/lib/jvm/jdk-11.0.22]06:51:04,608 [main] [INFO] Changes detected - recompiling the module! :source06:51:04,610 [main] [INFO] Compiling 450 source files with javac [forked debug release 21] to target/classes06:51:05,021 [main] [INFO] -------------------------------------------------------------06:51:05,021 [main] [ERROR] COMPILATION ERROR :06:51:05,021 [main] [INFO] -------------------------------------------------------------06:51:05,021 [main] [ERROR] error: release version 21 not supported06:51:05,021 [main] [INFO] 1 error06:51:05,022 [main] [INFO] -------------------------------------------------------------  

30445
P
A
aldoc77148901Level 2
 Adobe Experience Manager Sites
AEM Product recommendation CIF component

Hello,we have an AEM + Commerce headless architecture and we configured the Adobe Commerce Product Recommendations (https://experienceleague.adobe.com/en/docs/commerce/product-recommendations/overview)We're trying to use AEM Product Recommendation CIF component (https://github.com/adobe/aem-core-cif-components/tree/master/extensions/product-recs/content/src/main/content/jcr_root/apps/core/cif/extensions/product-recs/components/productrecommendations/v1/productrecommendations)Opening the component dialog we see this configurationSo, we guess the component knows how to behave according to the page template, so that it matches what configured on Commerce side  But how the component knows which Page type the current page corresponds at? More, to collect behavioral data, we must track them by our self using provided SDK as stated at https://experienceleague.adobe.com/en/docs/commerce/product-recommendations/getting-started/headless, right? 

7621
A
V
vashishth47Level 2
 Adobe Experience Manager Sites
issues setting up aem RDE environment

I am trying to setup adobe AEM RDE environment.  Have followed the steps mentioned in the following documentation https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/rde/how-to-use. I ran the "mvn clean package" command and then proceeded to run the command in the screenshot attached below("command run" file). Note I have two different project in my repo. I have also created a new dispatcher for RDE environment and added a symbolic link for the same in the active vhost folder. Added the lines present below in my screen shot.  However whenever I try to hit a servlet it only gives default apache output as <html><body><h1>It works!</h1></body></html>.Please let me know if anything else is required.  

7343
VishalKa5
T
test1234567Level 6
 Adobe Experience Manager Sites
Missing Publish Dependency Wizard for Page

Hello Community, In one environment, when I publish a page I do NOT get the Publish (dependency) wizard screen that lists referenced assets (e.g., images, Target configs, experiences). In the other (working) environment, that screen appears and shows “All Assets” with the referenced items (see screenshot). I need to know which group memberships and path permissions are required so this wizard appears and allows me to include dependent assets/activities. /libs/wcm/core/content/sites/publishpagewizard.html?item=/content/project/en/us&editmode Observed:Working environment: Selecting the page and choosing Manage Publication (or Publish) opens the dependency wizard (screenshot).Non‑working environment: The wizard does not appear; publication proceeds (or fails) without showing referenced assets, so dependent items (e.g., assets / Target activities) are not republished.Only difference so far: User/group permissions and possibly a custom workflow used in the failing environ

6601
Karishma_begumSh
M
ManjulaKumarLevel 2
 Adobe Experience Manager Sites
jayv25585659
jayv25585659Level 8
 Adobe Experience Manager Sites
Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
 Adobe Experience Manager Sites
AEM 6.5 EOL: Upgrade, Migrate, or Wait—What’s the Smart Move?

Hey Adobe community, With AEM 6.5 heading towards End of Life (core support ends Feb 2027, extended support Feb 2028), a lot of us are asking: What’s next? Should we stick with Long-Term Support (LTS) or take the leap to AEM Cloud? Let’s dig into the real questions: Why Upgrade?Is it just about staying supported, or are there real benefits to moving forward? LTS vs. Cloud: Pros and ConsWhat’s working for you with LTS? What’s tempting about Cloud? Any pain points or unexpected wins? Who Should Go Where?Are there certain teams, industries, or use cases that make more sense for LTS or Cloud? How do you decide? End-State Business ValueWhat does success look like after the upgrade or migration? How do you measure the impact on your business or clients? Share your experiences, opinions, and advice—whether you’re deep in migration planning or just starting to think about it. Let’s help each other figure out the smartest path forward!

547710
Shashi_Mulugu
Community Advisor
V
VishnuRa5Level 2
 Adobe Experience Manager Sites
Migration dispatcher issues 6.5 to cloud

Migrating from 6.5 to cloud and ran Analyzer for dispatcher module and committed suggested changes  Used below command and added missing immutable files as welldocker_immutability_check.cmd srcAble to deploy dispatcher in local docker instance successfully, but when we try to deploy using adobe webtier dispatcher pipeline getting below error  Cloud manager validator 2.0.89 2025/09/24 04:01:01 The following warnings were found: Did not find ServerAlias '*.adobeaemcloud.net' in any vhost file Did not find ServerAlias '*.adobeaemcloud.com' in any vhost file 2025/09/24 04:01:01 The following suggestions are proposed: /tmp/dispatcher/unzippedConfiguration/conf.d/enabled_vhosts/companybrand.vhost: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" should be symlinks /tmp/dispatcher/unzippedConfiguration/conf.dispatcher.d/enabled_farms/companybrand.farm: file is not a symlink, all files inside "enabled_vhosts" and "enabled_farms" shou

6732
V
M
Mahesh_GunajeLevel 7
 Adobe Experience Manager Sites
K
Krm974Level 2
 Adobe Experience Manager Sites
Recalculating all index numbers following deleting a row

I built a form having rows, where there is item numbers for each row such as 1 / 2 / 3 ... I use following to add a new instance: form1.Button.Button1::click - (FormCalc, client)Table1._Row1.addInstance(); I use following to delete the last instance: form1.Button.Button2::click - (FormCalc, client)var nCount = Table1.Row1.instanceManager.count ;//remove instanceTable1.Row1.instanceManager.removeInstance(nCount-1); Below script is to show row numbers at the first column.  form1.Table1.Row1.ItemNo::enter - (FormCalc, client)var rowCount = this.parent.instanceManager.count;form1.Table1.Row1.ItemNo::calculate - (FormCalc, client)this.rawValue = this.parent.index + 1; these above works great; however lately I needed to delete a random instance which is not the last row using: form1.Table1.Row1.#subform[0].del_button::click - (JavaScript, client)_Row1.removeInstance(this.parent.parent.index); Now there is such a bug when I delete another inst

5692
K
daniel-strmecki
Community Advisor and Adobe Champion
daniel-strmeckiCommunity Advisor and Adobe Champion
 Adobe Experience Manager Sites
Migration to the New Content Fragment Editor in AEMaaCS

Migration to the New Content Fragment Editor in AEMaaCS  by @daniel-strmecki   Introduction Content fragments (CF) in AEM allow authors to design, create, and publish page-independent content without visual design and/or layout. Therefore, authors can use them to prepare content that can be reused in multiple locations and channels, which is ideal for headless delivery or reuse across pages. The CF reference AEM core component enables simple referencing and using the CF data on a page, while GraphQL and/or REST APIs enable headless content delivery. The new CF editor was recently introduced by Adobe to enhance the authoring experience for structured content. It can be accessed from the new CF console and offers a few interesting new features: Tree navigation feature with a hierarchical view of the CFs structure to allow authors to easily navigate and edit CFs efficiently Improved authoring interface with features such as auto-save and breadcrumbs for navigating ba

7923
daniel-strmecki
Community Advisor and Adobe Champion
T
test1234567Level 6
 Adobe Experience Manager Sites
Y
YAMINIK1
 Adobe Experience Manager Sites
akhilraj
akhilrajLevel 5
 Adobe Experience Manager Sites
OIDC Performance Improvement and Solution for Constraint Violation

Hi, We have implemented the Azure OIDC auth mechanism for our internal AEM site. Normal functionalities are working fine, including:User creation if not presentAdding to groupsAdding the propertiesUpdating propertiesUser logoutHowever, we encounter the following errors when the load is high.09.09.2025 08:05:40.550 *ERROR* [qtp1259476332-8844] OIDCAuthenticationHandler Exception occured in extract credentials of Circuit OIDC Authentication Handler :: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0030: Uniqueness constraint violated property [jcr:uuid] having value c04a62db-b08a-3fcd-9da4-82fa487cbd7e: /home/users/7/7rlCyphwMn-XTm_MPlHp, /home/users/-/-Plc_ry19_nkYAn02zmw OIDC Authentication Handler :: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /home/users/8/8Q1wHuNaDigZHD6Bt79M/oidcTokensLine 6263: at com.intel.circuit.services.sso.services.CircuitOIDCAuthenticationHandler.extractCredentials(CircuitOIDCAuthenticationHandler.

8083
kautuk_sahni
Community Manager
T
test1234567Level 6
 Adobe Experience Manager Sites
Blank UI and mboxDefault Issues

Hello Community,I need your input regarding an issue we’re facing. We have an integration in place for AEM Target. We are successfully pulling audiences from Target and using them in AEM to personalize content based on browser type. In the author environment, we’re able to view the respective personalized content as expected.However, when testing in the publish environment (server), we notice that while the content is being replaced, the UI is often blank. Occasionally, we see the default content instead. Upon investigation, it appears that `.mboxDefault` is hiding the content, even though the content is being replaced for the intended audience:.mboxDefault {visibility: hidden;}I want to ensure this will not cause issues in higher environments. Has anyone encountered a similar issue, and what steps did you take to resolve it? Please advise.Additionally, we observed another issue related to `[execute.mboxes[0].profileParameters]`:**Parameter value for `_cq_.resolvedSegments` exceeds the

8892
kautuk_sahni
Community Manager
N
NandheswaraS_
 Adobe Experience Manager Sites
Vanity Path Issue in Hindi Pages: %20 (Space Encoding) Added Automatically

Hi Everyone,We are facing an issue in our AEM setup related to vanity paths and Hindi pages.Problem StatementWhen we author a page content path in Hindi pages, a %20 (encoded space) is getting appended at the end of the vanity path.This behavior is observed only for Hindi pages.For English pages, sling:vanityPath property, and we directly use the same vanity path without issues.ObservationsThe issue happens only after translation (we usually author English pages and then translate them to Hindi using Process9).In Author mode, when the content path is authored, it looks fine. But once published, the vanity path automatically adds %20 at the end.Example: /hindi/page → becomes /hindi/page%20.For English pages, vanity paths remain clean and this issue does not occur.There is no visible trailing space in the sling:vanityPath Property.What We TriedChecked page properties and vanity path values — in English they are clean.Verified that no explicit sling:vanityPat

12053
kautuk_sahni
Community Manager
A
aldoc77148901Level 2
 Adobe Experience Manager Sites
B
bruce_fernandesLevel 2
 Adobe Experience Manager Sites
Custom Content Fragment Component

Hello, Goal: To display content from a content fragment onto a page or experience fragment. This must include data from fragment reference fields ie: nested content fragments and content reference fields, specifically images. Currently, OOTB only displays either with their respective paths.  My Approach:Create a copy of the content fragment componentCreate a Sling Model that exposes the input values from the dialog boxFor text fields, I would like to grab them, maybe add some basic logic and expose it to the component's HTLFor nested content fragments, I would like to find the content fragment, grab it's data and expose it to the component's HTLFor images, I would like to do the same and make it available for HTL to grab in a way that it can then display it on the page.Create custom HTL for the component that displays all the content based on whether or not they are selected in the dialog boxStyle said component with CSS My issue is with the Sling Model and HTL, I a

5723
kautuk_sahni
Community Manager
K
KONDISR
 Adobe Experience Manager Sites
jayv25585659
jayv25585659Level 8
 Adobe Experience Manager Sites
W
winter_bunnyLevel 2
 Adobe Experience Manager Sites
Mahedi_Sabuj
Community Advisor
Mahedi_SabujCommunity Advisor
 Adobe Experience Manager Sites
A
Adobe Employee
anujkapoorAdobe Employee
 Adobe Experience Manager Sites
How to manage metadata before and after migrating to AEM Assets?

After purchasing Adobe’s Digital Asset Management solution, metadata is the most critical aspect while starting your asset management journey. Managing metadata gets completely out of the control of the administrators once the assets are distributed to the users. Effective asset metadata ensures better search, which is the ultimate destination for any DAM tool.Here are the recommended steps that you must execute before starting to migrate your assets to AEM:Step 1: How would you filter the assets that exist in the repository? Answer this question and create the list of fields that you need.Think about your users on how they will search assets that exist in the repository and then work backward to create such properties for your assets.Step 2: Revisit all existing properties and eliminate redundant onesLook for properties that seem irrelevant or duplicates of the existing properties and remove them from the list of required properties for Adobe’s DAM.Step 3: Segregate the propertie

17172
kautuk_sahni
Community Manager
S
SanaQuLevel 2
 Adobe Experience Manager Sites
Ritesh_Mittal
Community Advisor and Adobe Champion
Ritesh_MittalCommunity Advisor and Adobe Champion
 Adobe Experience Manager Sites
Master Your AEM Interview Preparation : A Comprehensive Guide

Master Your AEM Interview Preparation : A Comprehensive Guide by Ritesh Mittal Overview Are you gearing up for an Adobe Experience Manager (AEM) interview and want to ensure you're thoroughly prepared? Whether you're aiming for a Developer, Technical Lead, or Architect role, our latest YouTube video is here to be your ultimate guide. With over 100+ questions and detailed solutions, this video is designed to cover every aspect of AEM, both on-premise and in its cloud offerings. Here’s a deep dive into what you can expect from this comprehensive tutorial.   Why This Video is a Game-Changer for Your AEM Interview Prep Extensive Question Bank: The video features a curated selection of over 100 questions that are critical for AEM interviews. These questions span a wide range of topics and complexity levels, ensuring that you’re well-prepared for anything that might come your way. Each question is not just answered but explained in detail, offering insights into best practice

73134
kautuk_sahni
Community Manager

Badge winners

Show all badges
Terms & ConditionsAccessibility statement

Loading footer...