Adobe Experience Manager Guides

What are the best practices for managing graphics and ensuring the most recent copy uploaded to the repository is the current VERSION, not just a working copy?All documentation on version control I’ve found for Guides is specific to the DITA files, not graphics objects.When we upload/copy an updated graphic, the popup windows asks us if we want to create a version of the EXISTING working copy. It does not ask about creating a version for the correction we are uploading. It looks like whatever we last uploaded remains a working copy, not an actual version, which means graphics sent out for translation may not be the most recent and correction file.Does this mean any time we upload a corrected graphic, we have to drag/drop twice. Once to upload and force the system to create a new version of the existing working copy and the new graphic become the existing working copy. Then a second time to force that correction to be the newest version?I’m seeing graphics that I know have been changed/

When I publish a document with an image on the front cover, it is supposed to set it to front and center, but instead it takes up the entire page:  The image itself is not that large. Guides seems to be expanding it. Here is the source: <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE concept PUBLIC "-//Emerson//DTD DITA Concept//EN" "mmiconcept.dtd"><concept id="GUID-9e62db09-26b4-4e6e-9ec3-9fc68b449cda-enHYPHENus" outputclass="frontcover">  <title>G-SeriesPDSFront</title>  <conbody>    <image align="center" height="3in" href="GUID-0b554440-e72e-4261-bec9-8efa22a822d0-enHYPHENus.png" id="image_mpl_bdw_jz" outputclass="front_center" placement="break" width="4in">    </image>    <image href="GUID-b4720b3e-04db-4a4a-8ac8-1d6a401fe5bd.png" id="image_1" outputclass="brand_logo">    </image>    <section id="section_1" outputclass="pds-frontpage">      <title>Exceptional reliability and safety</title>      <ul id

We are experiencing an issue in our AEM as a Cloud Service environment  where non-admin authors are unable to use standard publishing due to an implicit system path reference.When a user attempts to publish a content page, the replication payload automatically appends a reference to the legacy system path /libs/settings/wcm/designs/default/jcr:content. Because /libs is immutable and standard users lack crx:replicate permissions at the root/libs level, the replication engine blocks the direct publish and routes the payload to the default request_for_activation workflow.To isolate this issue, we created a dedicated test user and explicitly granted them jcr:all permissions on the following paths:/var  & /content/dam/mygps/en/pi  & /content/mygps/us/en/pi (Plus standard jcr:read on root /) Despite having full jcr:all (which includes read, write, and replicate) across all relevant content and variable directories, this test user still triggers the approval workflow. The replication

We have a connector set up from Guides to our translation vendor, Propio. We send 9 languages at once. Most of the languages are imported back in without an issue. For one language, we can see in the Translation Project that all the files have been translated. However, when I go back to Assets or Guides some of the dita topic don’t seem to be working. The Title in Assets says “null” and when I open the topic, it’s just a blank screen. Other topics are working. I couldn’t find a common denominator for topics that aren’t working. There are some folders where none of the topics are working, but others were some work and some don’t.Has anyone had this issue, and if so how did you resolve it? Adobe has suggested sending only one language at a time, but we have 9 standard languages that we have to translate each document into, and sending one at a time is not feasible.

Best Video Editing Course in Lucknow with Placement Unity Veda College offers an industry-focused program designed to help students build professional editing skills through practical learning and real-world projects. The course covers Adobe Premiere Pro, Adobe After Effects, DaVinci Resolve, Motion Graphics, Color Grading, Audio Editing, Video Production, and Post-Production using industry-standard software. Students gain hands-on experience through live projects, portfolio development, and expert mentorship, helping them become job-ready for the media and entertainment industry. The college highlights practical labs, experienced faculty, and placement support as key features of its creative programs.

Hi everyone,We're trying to understand the best approach for making Salesforce Opportunity Product (Opportunity Line Item) data available in Marketo.Currently, Opportunity information is available in Marketo only when there is an Opportunity Contact Role associated with the Opportunity. In our Salesforce org, this is typically the Logistics Contact, but that contact is not relevant for our marketing use case.Our goal is to make Opportunity Product information available in Marketo, such as:Primary Product Product 2 Product 3 Solution Group Other Opportunity Product fieldsso that Marketing can build Smart Lists and Smart Campaigns based on these values.Our questions are:Is there any way to sync or expose Opportunity Product (Opportunity Line Item) data to Marketo without relying on the Logistics Contact or another Opportunity Contact Role? Does Marketo support syncing Opportunity Product data directly, or is a custom solution (such as Salesforce Flow, Apex, or Custom Object Sync) require

GIF images render as static JPEG in AEM Guides output (animation lost). GIF images added in AEM Guides are not rendering as animated images in the output. Instead, they are being converted to static JPEG renditions during rendering. ​@DivrajSingh  I would appreciate a prompt response on this issue. Thanks

Good afternoon!We use (AEM/Guides) Native PDF output and have our draft comments set to display in PDF output with special formatting.They had been working fine until we recently updated to 5.1. Now everything in Guides shows correctly (author, source, preview) but there are no Draft Comments in the output PDF. What could have caused this? Is there a default that reverted possibly?  Any help is appreciated!Thanks,Josh

Hi, we are using AEM Guides Native PDF for publishing PDFs, and I wanted to check if others have encountered issues with table break behavior.Current behavior:Tables that begin and end on the same page render correctly. When a table spans across multiple pages: The portion on the next page starts directly with the table header. The table continues from where it was split, without any indication that it is continued. Expected behavior:Tables that begin and end on the same page should continue to work as expected. When a table spans multiple pages: The table portion on subsequent pages should display a label such as:"Table #: Table Title (continued)" This should be followed by the table header and the remaining table content. Example image:   

I have a requirement to add a custom column to the list view along with the other OOTB fields in Adobe Experience Manager (AEM) Cloud instance. Could anyone guide me on how to achieve this? I want to add a column with header Content-Type that will fetch the value from jcr:content/metadata/content-type.I could achieve this with the reorder.jsp file pointed here: https://experience-aem.blogspot.com/2019/10/aem-6520-aem-assets-add-custom-metadata-columns-in-assets-console-list-view.html but this does not work in AEM Cloud.Again, this URL also explains in another way : https://experience-aem.blogspot.com/2019/08/aem-6510-adding-custom-metadata-columns-in-list-view-of-assets-search-console.html but again this conflicts with OOTB behavior and breaks the search functionality in AEMaaCS.Any concrete solution that works on cloud?

I’m having an odd issue when receiving translations back from our provider.  Issue:When translations are accepted back into AEM from our translation provider, I'm seeing a variance in the metadata the assets end up with in the target folder.  It's mainly one field: "cq:TranslationSourcePath" (needed for my purposes) Project 1: Results show the cq:translationSourcePath (along with other metadata) on the target (de_de) assets “jcr:content” node. Project 2: missing translation metadata, Note it’s a different project, same target (de_de) note one of the only fields that gets copied to the target asset.Please Note: I'm not convinced this is a translation provider-related issue, as the data already exists in the "staging" area that AEM creates when initiating translations. Please see the screenshot below for the temporary location created for the translation (this is before the translation was sent back to AEM, i.e., before it was deleted as part of clean up):  Conclusion:Because the data ex

We are observing an issue in AEM Guides (Cloud Service) where the translation status does not revert after cancelling a translation job. As per Adobe documentation and earlier fixed issues, when a translation job is cancelled or deleted, the “In Progress” status should revert to the original state. However, in our environment, the status continues to remain “In Progress”. Observed Behavior: When sending a DITA topic/map for translation where the target language copy does not exist: A placeholder (empty) language copy is created. If the translation job is then cancelled: The placeholder file remains in the target language folder. The translation status of the asset still shows “In Progress”. The status does not revert even after some time or refresh. Expected Behavior: On cancellation of the translation job: Translation status should revert from “In Progress” to the original state. Placeholder language copies (if not translated) should ideally be cleaned up or

Hi Team,Can we deploy AEM Guide in AEM RDE environment Thanks

Has anyone else had any issue with their Condition Presets resetting back to nothing selected in the preset? Sometimes it happens in the source language and sometimes in one of the target languages, but not the others?When it happens in the source language, it had existed and the settings were saved, then a few months later it is zeroed out.

We have on premise AEM (6.5) author and publiser instance and during last 2-3 days our error.log file is full of following errors on publisher instanceOakState0001 errors09.04.2026 13:37:45.729 *ERROR* [55.32.21.101 [1775734665631] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.servlets.ReplicationServlet Error during replication: Repository error during node import: OakState0001: Unresolved conflicts in /content/some-page/jcr:contentcom.day.cq.replication.ReplicationException: Repository error during node import: OakState0001: Unresolved conflicts in /content/some-page/jcr:contentCaused by: javax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /content/some-page/jcr:contentCaused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakState0001: Unresolved conflicts in /content/some-page/jcr:content Concurrency warning 09.04.2026 14:50:46.659 *WARN* [EventAdminAsyncThread #9] org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate Attempted to perform

Missing keys/keyrefs used to generate specific “filler” content in the PDF: Key definition for "{keyrefName}" not found in the DITA map. With our upgrade to v5.1.1, this filler content no longer generates in the PDF and instead nothing generates to indicate any missing keys. Was this intentional? Is the only wayt to find missing keys to preview on-screen and look for red?

We have an instance of AEM 6.5.12. with Guides 4.6 UUID running on a server and we want another instance of the exact same thing on another server that we will use as our “development server.” This is not an upgrade. We want the 2 instances to be identical.On our new server I have installed the exact same AEM 6.5 with the same service pack and same 4.6 release guides.  All we need is the repository from the first instance. I cannot use package manager to do this because we must preserve the version history of all of our DITA topics.  From the documentation I’ve read it seems the best way to do this is with ther CRX2OAK tool.I’m not experienced with migration and would appreciate any steps or advice you might have. First, is the CRX2OAK tool the  best way to accomplish this? How do I get one repository to connect with another? Should the crx-quickstart folder from the target server be on the same server as our first AEM installation?  If so, what is the best way to move the crx-quicksta

Hello,We’re in the process of setting up our AEM Guides instance and have that link to our Workfront projects. I’ve noticed that the Workfront tasks list of AEM Guides has a limited number of columns. It would be helpful to our users to see the task percent complete, start dates, and predecessors on this view. Is it possible to add more columns to this view either through the native connector between the two or through Fusion?

I am searching for the question/answer series titled “Translations - Latest source language version of the map was not sent out”. I’m not seeing it in the AEM Guides group and it wasn’t listed under my account within the list of questions I had posted. Were some posts lost in the move to this new URL/interface?

Hi All, I am new to AEM Guides and tried my hand at importing an existing DITA project from https://github.com/DITAWriter/pilot_training_mitchell_bomberThis is a DITA-fied version of the Pilot Training Manual for the Mitchell Bomber B-25 I installed the package - com.adobe.fmdita.uuid-6.5-4.6.1.5886.zipI was unable to install the package com.adobe.fmdita.uuid-6.5-SP due to dependency com.adobe.fmdita:com.adobe.fmdita.uuid-6.5:5.0.0.211I created a folder in my DAM project and dumped .dita files from the above repo in it. When I tried to access the same in Guides editor window I get the below -  If I try to go into “Preview” mode I get the “Loading preview...” overlay which doesn’t go away -   Can anyone help point what am I doing wrong here? Thanks,Nagesh

Hi,I am using AEM cloud and we have Guides, when we select an asset (dita), we are able to see a Open in Framemaker button which when clicked opens the asset in FM. Do we have anything as such for Adobe illustrator, if Yes how do we enable it?If No, how to we build one which works just like the Open in Framemaker button??  This is how to enable the Open in Framemaker button:ThanksSandeep

I’m facing an issue with AEM Guides on AEM as a Cloud Service while generating Sites output from a DITAMap that references Markdown topics using this documentation: https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/knowledge-base/kb-articles/authoring/webeditor/markdown-in-dita-and-aem-guidesWhat I’m seeing: The DITAMap → Site generation runs Site pages do get created Page properties (sourcePath, UUIDs, map references, etc.) are all set correctly along with the hierarchy of nodes. However, the content is missing - the “injected-container” on the page is empty This preset works for normal dita topics. Error in logs:Markdown resource cannot be read as an XML Document org.xml.sax.SAXException This happens during the NodeJS-based publishing workflow, specifically while Guides is extracting dependencies / DTD rules. From the stack trace, it looks like the Markdown file is being attempted to be read as an XML document.Pages are created but the Markdown conten

I am trying to migrate existing unstructured FrameMaker documents (.fm and .book) to DITA following the official documentation here: Migrate unstructured FrameMaker documentsHowever, I am unable to proceed because the Map to DITA (or Convert to DITA) button is missing from the Assets toolbar when I select my .fm file. When I open the file, I only see options to generate PDF, HTML5, and EPUB (as shown in the attached screenshot), but no option for DITA migration.Steps to Reproduce: Upload an unstructured FrameMaker file (.fm) to an AEM Assets folder. Select the file. Look at the top toolbar and the Output Presets panel. Actual Result: The Map to DITA button is not visible. Only standard Asset options and Generate (PDF/HTML5/EPUB) are visible. Expected Result: The Map to DITA button should appear to initiate the migration workflow using the .sts file. Environment: Adobe Experience Manager (2025.11.23385.20251113T172403Z) aem-guides (2025.10.0.278)  

I'm trying to install Adobe Experience Manager 6.5 on Windows Server 2022 on command with the following command C:\AEM\Author>java -jar AEM_6.5_Quickstart.jar -r author -p4502However the installation keeps getting stuck on "Press CTRL -C to shutdown the Quickstart Server:Loading quickstart properties: defaultLoading quickstart properties: instanceLow-memory action set to forkUsing 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]The JVM reports a heap size of 2048 MB, meets our expectation of 1024 MB +/- 20Setting properties from filename 'C:/AEM/Author/AEM_6.5_Quickstart.jar'Setting 'sling.run.modes' to 'author' from command line.Verbose option not active, closing stdin and redirecting stdout and stderrRedirecting stdout to C:\AEM\Author\crx-quickstart\logs\stdout.logRedirecting stderr to C:\AEM\Author\crx-quickstart\logs\stderr.logPress CTRL-C to shutdown the Quickstart server...Java version installed is 21.0.9.Any idea

We need to update the DITA-OT that is included with AEM Guides to get a newer version of FOP. I have managed to migrate our custom PDF plugins to the new OT (4.3.4), but the AEM Sites output is not working. The files are processed properly by the DITA-OT, but are not getting handed over to Guides to create the site. I notice differences in the log output when publishing with different DITA-OT versions. I need a few hints on how to get the job-helper.xsl working in the newer DITA-OT. Working DITA-OT:copy-flag-check:copy-flag:[job-helper] Processing /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/.job.xml to /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/flagimage.list[job-helper] Loading stylesheet /opt/aem/launcher/profiles/ditaot--3922c171-076c-7dd5-4b4b-9b4f895be1bd/DITA-OT/plugins/org.dita.base/xsl/job-helper.xsl New DITA-OT:copy-flag-check: copy-flag: Thanks,-Huntley