Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
I logged in da.live as I did it 1 year ago I do not see sites, I cannot manage config and permissions All people from the org has the same issues It was working some time ago
Situation:We have Content Fragments which have are referencing to other Content Fragments. When we send out this CF’s to translation, we expect that the path to the referenced CF’s are adjusted to the locale of the target page although the referenced CF’s are not part of the translation job as they have not been changed. The path adjustment is currently only done if translation configuration is not set to “Do not translate” under the dropdown "Translate Content Fragment Assets”. So, the path is only adjusted if te referenced CF’s are part of the translation job. Requirement: To avoid unnecessary translation costs, we need an option that the paths to referenced are adjusted although they are not part of the translation itself.
Sharing a specific AEM Assets issue I ran into and its solution. Steps to reproduce the issue: Goto https://experience.adobe.com/?repoId=author-pXX-eXX.adobeaemcloud.com#/@myorg/assets/importmetadataform/ The environment should have more than 600 user groups with ACE permissions. Hit Import metadata Import will throw this error Root cause:Specifically https://author-pXX-eXX.adobeaemcloud.com/conf/global/settings/dam/adminui-extension/metadataschema/rep:policy.-1.json this request returns 300. While loading the import wizard, the Assets viewer tries to load complete rep:policy under metadataschema to show allowed schemas. This is an expensive operation and throws 300, if the number of nodes under /conf/global/settings/dam/adminui-extension/metadataschema/rep:policy is more than default 200 nodes Fix: The current bandage to fix this issue is to bump the max nodes for GetDefaultServlet to larger number. Create an osgi config under apps/myapp/osgiconfig/config.author/org.apache.sling.serv
Description - When reports are exported, any text in a Workfront field that is in a rich text format, including bullets, bold, italics, etc., all that rich text formatting is not included in the exported report. Why is this feature important to you - Without rich text formatting, recipients of exported reports may not understand what the author of the report was trying to communicate, causing confusion, lack of trust, and continued perceived lack of understanding from Adobe Workfront for customers requiring professional looking reports out of Workfront. This seems so basic, and Adobe's name and reputation will continuously be tarnished if this isn't addressed (or even accepted and acknowledged?!). How would you like the feature to work - include rich text in exported reports. Current Behaviour - Lack of rich text in exported reports.
Hello,I am struggling to understand why as an administrator I am not able to clink on an asset in Content Hub and open it in the DAM to edit. Is some development required?Content Hub users often share links to assets with the Content Librarian, requesting edits of those assets. What is the easiest way to find and edit those assets?As searching by file name is not a time productive option. Thanks, Natasha
Hi Team,We recently migrated our application to AEM as a Cloud Service. During page replication, /libs/settings/wcm/designs/default path included in the publish references. AEM as a Cloud Service, /libs is immutable and should not be published. As a result, page publication is blocked unless we manually uncheck this reference in the publication wizard and then proceed with publishing the page. To confirm we do not have any reference to this path in code.Has anyone encountered this behavior before or knows what could be causing this OOTB reference to be added during publication? Is there any known component, policy, style system configuration, or reference provider that could introduce this dependency?Any insights or suggestion would be greatly appreciated.Many thanks in advance!
SSO (SAML) breaks after an in-place upgrade to AEM 6.5.25 (CFP-25) Environment: on-premise AEM Author, upgraded from 6.5.10 to 6.5.25.Immediately after applying CFP-25, every SSO-related decrypt operation fails with:javax.crypto.BadPaddingException: pad block corruptedThis appears to break decryption of the SAML keystore/truststore passwords and replication transport passwords. As a result, SSO fails and the CMS becomes inaccessible, except by disabling SAML authentication and using the manual login route. The master key is stored in the JCR under /etc/key; it was never migrated to the filesystem bundle. The key value itself was not changed during the upgrade. I simply installed the CFP package, waited until it was complete and restarted the instance, as per the instructions. The workaround that resolved the issue (currently on test environments) was to rewrite the stored /etc/key value from the older obfuscated format to the raw value, so the newer crypto bundle could read it correct
We are looking to manage OSGi configurations in the AMS environment instead of storing sensitive values in the codebase. In Adobe Cloud Manager, there is an option to manage environment-specific secrets and configurations. Is there a similar approach available in AMS, and if so, how can we manage these configurations securely?
Two Java items in the AEM as a Cloud Service release notes affect almost every team with custom code: a deprecated API deadline that has already passed, and a Java 25 runtime migration with fixed target dates. Here’s what Adobe’s current notes say, with exact dates.1. Deprecated Java APIs: deadline was September 28, 2026Adobe’s notes list packages slated for removal, including org.apache.sling.commons.auth, org.apache.felix.webconsole, org.eclipse.jetty, com.mongodb, org.apache.log4j, ch.qos.logback, org.slf4j.spi, org.slf4j.event, com.google.common, com.drew, org.apache.abdera, org.apache.cocoon.xml, org.apache.felix.http.whiteboard and org.apache.jackrabbit.oak.plugins.memory.Since April 14, 2026: per the notes, Cloud Manager pipelines with code using these APIs fail at the Code Quality step, and deployment is blocked until the usage is removed. This is not a 2026.9 change. After September 28, 2026: environments still using them stop receiving critical Adobe release updates and fall
Hi all! I’m back with another hyperlink question.Any idea why this wouldn’t work in a project report?displayname=Plannerlink.url=program:Planner Linkvalueexpression=IF(ISBLANK({program}.{DE:Planner Link}),"","Link"))valueformat=HTMLThe whole column just loads blank.Thank you in advance!
Hello Community,We're looking for suggestions and lessons learned from anyone who has performed metadata updates at a very large scale in AEM 6.5 On-Prem Assets.Our RequirementAEM 6.5 On-Prem ~5 Million Assets (50 Lakhs) Repository Size: ~40 TB Need to update ~20 metadata properties on existing assets The update source will come from a mapping/reference file Important: The requirement is to append/update metadata values without overwriting existing values. Existing metadata must be preserved wherever applicable.
AEM Sites modernization is moving beyond manually rebuilding every page and component.With AI-assisted modernization, teams can potentially accelerate activities such as:Migrating content from legacy websites or CMS platforms Mapping page structures to reusable blocks Applying design-system patterns Creating new Edge Delivery Services pages Making style and template updates Previewing changes before deploymentBut migration speed alone does not define a successful implementation.A site can be migrated quickly and still create long-term challenges if:The content model does not match the authoring workflow Page structures are converted into non-reusable blocks SEO metadata, URLs or redirects are missed Accessibility and responsive behavior are not properly validated Integrations, personalization, search or commerce logic are overlooked The final site looks visually correct but is difficult to maintainThe current AEM Experience Modernization Agent approach is interesting because it combine
Hi All, We are migrating AEM Forms to Cloud from AMS.When setting up the local, we placed the .far file add-on in the install and then brought over our custom forms. 09.09.2026 21:04:17.714 *ERROR* [[0:0:0:0:0:0:0:1] [1788968057597] GET /content/forms/af/brandA/en/forms/contact-sales-form.html HTTP/1.1] com.adobe.aemds.guide.internal.impl.utils.rhino.RhinoScriptProcessor Failed to execute script 'parser': FAILED ASSERTIONjava.lang.IllegalStateException: FAILED ASSERTION at org.mozilla.javascript.Kit.codeBug(Kit.java:375) at org.mozilla.javascript.TokenStream.<init>(TokenStream.java:47) at org.mozilla.javascript.Parser.parse(Parser.java:568) at org.mozilla.javascript.Context.parse(Context.java:2533) at org.mozilla.javascript.Context.compileImpl(Context.java:2482) at org.mozilla.javascript.Context.compileString(Context.java:1486) at org.mozilla.javascript.Context.compileString(Context.java:1475) at org.mozilla.javascript.Context.evaluateString(Context.java:1231) at com.adobe.aemds.
Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.Would love to hear from others are these things you
Hi All, Getting the below issue - C:\Users\admin\AppData\Local\@adobe\aio-cli>aio aem-migration:dispatcher-converter -t=ams********** Executing Dispatcher Converter **********Converting Dispatcher Configurations...Found usage of undefined variable:target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:${PUBLISH_DEFAULT_HOSTNAME}Apache configuration uses non-whitelisted directives:target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projA_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projB_portal_publish.vhost:64 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projB_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/projC_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandD_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandE_publish.vhost:63 LogLeveltarget/dispatcher/src/conf.d/available_vhosts/brandF_publis
Hi all,Sharing a small open-source tool I built for AEM as a Cloud Service: a Usage action in the Assets console that answers “where is this asset used?” more completely than the built-in References rail.Select an asset and a Usage button appears. It lists every page, experience fragment and content fragment using that asset with the exact component, a Published/Draft badge, and direct Edit/View links.What it adds over the native References railInline images in rich text (Text component) Assets referenced inside content fragments Experience fragments listed separately from pages Language masters vs. live copies, so a rollout isn’t counted multiple times Published status + a direct link per resultHow it works (high level)A servlet bound by resourceType=dam:Asset + selector usage → GET {asset}.usage.json. No /bin path to allowlist, and the asset’s own ACLs apply. An AssetReferenceResolver service runs three lookups: a QueryBuilder query over configurable asset properties (fileReference,
Most AEM migration guides talk about infrastructure and pipelines. Fewer talk about what actually breaks at the component level when you move AEM Sites code to Cloud Service. Here's a practical checklist based on real migration work.1. Audit every OSGi Console dependency in your componentsIf any component logic reads config directly from /system/console/configMgr assumptions, or your devs used the OSGi console to hot-patch configs in prod, that workflow is gone. Cloud Service requires all OSGi configs to be defined as .cfg.json files in your repo and deployed through the pipeline. Grep your codebase for any code that assumes runtime-editable config it needs to move to proper config nodes per run mode (dev, stage, prod).2. Replace JCR_SQL2 and XPath queries with indexed, cloud-safe queriesCloud Service's Oak indexing is stricter about unindexed traversal queries anything that ran fine on-prem with a small index footprint can silently time out or get throttled in the cloud. Run the Oak I
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!
If your team is planning (or mid-way through) a migration from on-prem AEM or AMS to AEM as a Cloud Service, here's a rundown of the things that tend to blindside people beyond what's in Adobe's official migration docs.1. The "no full read/write access to the repo" shift is bigger than it soundsOn-prem, you got used to poking around CRXDE Lite, hotfixing content in prod, or running ad-hoc Groovy scripts against the JCR. Cloud Service locks that down hard no CRXDE Lite in prod, no direct repo shell access. Everything has to go through code, content packages, or the Cloud Manager pipeline. Teams that relied on "just SSH in and fix it" workflows need to rebuild that muscle memory around proper CI/CD and content sync tooling months before cutover, not during it.2. Cloud Manager's code quality gates will fail builds you didn't know were brokenCloud Manager runs static analysis (Sonar-based rules) on every build, and it's stricter than most teams expect. Common failures:Deprecated APIs (Reso
Island Peak Climbing starts long before the boots leave the ground. The air is thin from the very first trailhead. The snow crunches loud under thick boots. The mountain does not ask for fame or money. It asks for respect and patience. A bold heart knows that the path to the summit is not a race. It is a long conversation with gravity, cold, and the will to keep moving. When the climber looks up at the sharp ridge of Island Peak, the world shrinks to foot, hand, and breath.The Mountain Speaks in Cold WindThe Himalayas stand like a wall of stone and ice. Island Peak rises to 6,189 meters. That is nearly double the height of many famous mountains in other countries. The peak sits near the Khumbu region. Prayer flags snap in the wind. The trail passes through forests, then bare rock, then snow that never melts. Each day brings a new height. Each height brings thinner air. The climber feels the heart beat harder. The lungs work like bellows. The body learns that fear is not the enemy. It i
When adding approvers in the "Add people or names" field while creating a document approval workflow, the typeahead search functionality currently only works when searching by a single name value, such as a first name.For example, typing "Sarah" displays a list of matching users. However, once a space and last name character are entered (e.g., "Sarah B"), the typeahead dropdown no longer returns any results, even when multiple users matching that criteria exist in the system.Requested Enhancement:Update the typeahead functionality to support multi-word user searches, allowing results to populate when users enter a first name followed by all or part of a last name. For example:"Sarah" → Returns all users named Sarah "Sarah B" → Returns all users whose names begin with Sarah B "Sarah Brown" → Further narrows results to the specific user(s)This behavior would align with the legacy user lookup/typeahead fields found elsewhere in Workfront and provide a more consistent user experience acros
Hi users, due to new rules of GDPR here in Italy, the privacy act ask us to set a major control on tracking pixels; by far we know that we can set the otion at action level, with the specific chck-box, but, for us, having over 500 email templates active in 100 jouirneys it’s impossible to create a copy for every action w or w/o tracking. So the qustion: is it possible to block the tracking pixel at profile level, setting a boolean field that automatically blocks/uncheck the pixels while sending the email? Hpe it’s clear, thank you for support
When using the Week view layout in a Calendar report it has an hour-by-hour grid for each day of the week. When objects without a time don’t fall into these hour slots the hour-by-hour grid shows blank, taking up a lot of empty space on the page. I would like the ability to hide, collapse or turn off the hour-by-hour grid when viewing a Calendar report when the hourly grid is empty or unused.
Description - If you go to settings > interface and then try to edit a filter or a view, there is no responsiveness when you click "save filter." Though this is the tiniest thing, I get no confirmation visually that my changes have actually been applied and I have to close the window/open the filter or view back up to verify or just trust that it was applied. Why is this feature important to you - Would improve UX when editing views and filters. How would you like the feature to work - 1) Ideally when I hit "save filter" the window would close, and I'd get the little pop up confirming my changes have been applied, similar to when you save a custom form edit. 2) But I'd take anything really! A check mark to appear upon hitting save. A pop up confirming my changes have been applied. Anything! Current Behaviour - When you click "save filter" nothing happens- I therefore end up clicking it like 5 times thinking it isn't responding to me 😉
Hey Everyone,I am investigating traffic from various LLMs on our website. When I click a link from within Claude or Copilot, I noticed that document.referrer is null which means we can not reliably attribute traffic/conversions to LLM as it would show up ad Direct traffic instead.More peculiar thing is, I still see some hits, albeit very less which are referred from Copilot or Claude. I don’t understand why this scenario is gray instead of completely black and white?Has anyone else encountered this issue or has been able to find a workaround this? Is there any setting/flag we can update in our website? Happy to know any additional thoughts around this.Best,Isha
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
