Adobe Experience Manager Guides

I am using on premise AEM service pack 12 with FMDITA 4.1. I am trying to add word and pdf documents as attachments to dita xml using cross reference. But after generating AEM SITE from dita , the path to the documents is not getting resolved and causes broken link. Following are the screenshots:     How can this issue be resolved any idea? @divrajsingh   

When I set the table scaling in the DITA file (in the XML Editor), nothing changes in the FMPS output. I can turn on and off rowsep and colsep and the output generates as expected, but table scaling is ignored.Table scaling works correctly with the default DITA-OT output, it's only the FMPS that's ignoring it. I have looked in the settings file and in the edd files, but nothing jumps out at me as a fix. Does anyone have any suggestions?

AEM Guides v4.0.2FMPS 2020.2 In my PDF output, conreffing to my DITA specialization results in a big blank spot. My DITA specialization is based on a parml, and I can successfully conref to a parml and dl, but not to the specialization based on the parml. Does anyone know where in FrameMaker you can define what elements can be conreffed? The XML Editor allows the conref and the content shows up in the editor, it just will not appear in the output. I know an option is to just stop using the specialization and convert all my slentry to plenty, etc, but I'm trying to reserve that option as a last resort since we have 12 years of legacy content that uses the DITA specialization.

Hi everybody, This should be a simple question, but I can't seem to find it in the User Guide.I accidentally deleted a DITAmap from the Assets UI. I've since done other operations (before realizing the mistake I made), and so the Undo button isn't available. What do I do to get this DITAmap back--whether with some kind of undelete, or old-version-restoring? Thanks,Eric

Hello,I want to use Live Copies of the DAM structure to provide documents in different languages. The structure of the dam elements is based on the product catalog of the customer.MasterGroup AGroup AAProductDita TopicsDita MapsGroup ABGroup BEN….…The problem is that I cannot cancel the inheritance of the content for topics and dita maps. Like I can cancel the inheritance in the properties or on a normal AEM page.I can edit a Live Copy topic. But after the first rollout of the master was done, an exception occurred when I try to save the topic of the Live Copy. 21.02.2022 10:13:47.788 *ERROR* [127.0.0.1 [1645434827785] POST /bin/validatexml HTTP/1.1] com.adobe.fmdita.uuid.concrete.JcrResource Unable to get references for path /content/dam/dita-maps/copy/Overview.dita uuid nulljava.lang.NullPointerException: null               at com.adobe.fmdita.common.PathUtils.getURLWithoutBookmark(PathUtils.java:314) [com.ado

Hello -- How can I get my top page margins to be consistent across pages? I would like the top margin to be the same as the top page margin on the chapter page across all pages of the PDF. I think I’ve adjusted the margins in every place/layout (Chapter, First, Common) that I could find and did not have success getting the top margins to be consistent. 

Hi,   I want to create multiple tags there are around 1000 tags i need to create, is there any way I can create in bulk? Please let me know.   Aem version in use - 6.5.12   Thanks

HY, can anybody suggest how can we generate AEM SPA site from the dita map? What are the steps that need to be performed for rendering fmdita components in SPA?

When we are using the AEM Site output preset for our ditamap files, when the structure is created in AEM Sites, the root folder created from the ditamap has "-ditamap" appended to the page/folder name in AEM. We were looking for some setting to prevent this, but can't find one.

hello,  when I try to use any internal references or documents available inside AEM DAM to topics it works in the preview mode and when publishing the same content to AEM site pages It is rendered as plain texts instead of reference links in the pages. workaround : publish the documents to publish server and use the complete link.  This is observed on guides version 4.0.3 and aem 6.5.11 kindly provide a fix for this. 

Hello everyone - We are moving from on-prem to the cloud (AEMasCS). Have a general question with regard to repo management and deployment, and inputs/suggestions from the community. We have X number of sites and each site has its own repository. In the current on-prem situation, we have different pipelines that build these repositories and deploy to prod as needed based on their own schedules/release timelines. But now with AEMasCS, I see that all the repositories need to be pushed under one parent repo and we need to build & deploy together (if I understand it correctly), which means all the repositories need to be built and deployed at once. In practice that will not work for us, is there a way we can segregate the build and deployments based on the repository? Can we have a different sub-set of pipelines?Thank you

When dragging and dropping new files into AEM Guides, there is an option to create a new version of an existing file, an option to replace the file, and an option to cancel, but not an option to skip replacing that particular file. Is that going to be added? Or does the cancel option mean just to cancel that particular file and not the entire import batch?

Hello, I'm trying to follow the WKND tutorial however I am having issues with the client side libraries section. When I use npm run watch I get the following output and my changes aren't reflected in AEM: \Documents\aem-sdk\code\aem-guides-wknd\ui.frontend>npm run watch > aem-wknd-theme@1.0.0 watch > webpack-dev-server --config ./webpack.dev.js --env writeToDisk & chokidar -c "clientlib" ./dist & aemsync -w ../ui.apps/src/main/content Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating <i> [webpack-dev-server] [HPM] Proxy created: /content,/etc.clientlibs,/libs -> http://localhost:4502 <i> [webpack-dev-server] Project is running at: <i> [webpack-dev-server] Loopback: http://localhost:8080/ <i> [webpack-dev-server] On Your Network (IPv4): http://10.0.0.43:8080/ <i> [webpack-dev-server] Content not

We've found that sometimes the generation jobs for AEM Sites in Guides will get stuck (we are guessing due to some parsing error when it is generating pages), so eventually you need to cancel the job. However when you cancel the job, it stays in "Cancelling" mode and never actually cancels. You can see them on the Publishing Dashboard as well and again, you can't get rid of them, no matter how many times you click the "X" icon. This also starts to cause problems generating new jobs as they just sit in "Waiting" status and won't generate pages.

I've created a PDF using AEM Guides (via DITA-OT 1.23). The PDF contains several ohm symbols. When viewed in the PDF in a browser (selecting the PDF from the Generated Output area in AEM), the symbol appears correctly. When I download the PDF to my local system and view it in Acrobat DC or Reader, the ohm symbol disappears (blank space instead). Greatly appreciate any help/tips!

Copying and pasting content from Excel results in a <simpletable> instead of a <table>, and there doesn't seem to be a way to convert it from a simple table after it is in the DITA file.   Has anyone figured out a way around this? I need a table title and I'm not going to retype a large table manually.

Is anyone using Oxygen as the editor with the UUID version of AEM Guides? I used the Oxygen 30-day trial to test things out and I noticed that Oxygen displayed the file name, not the file title. Since the file name is the GUID/UUID, this is not helpful or usable. Does anyone know if this is a configuration issue? Can I configure something in AEM Guides or Oxygen to display the file title in the map/editor instead of the file name? (Unfortunately, my 30-day trial is over and I don't want to purchase Oxygen yet if it isn't going to work.)

Hi All, As a client requirement, I am looking to change the default "Destination Path" field within DITA Map "output preset" console and make it more customer-specific like "content/dam/customer-name/fmdita-outputs/".   I found that its coming from "/bin/publishlistener?operation=PUBLISHBEACON&source=%2Fcontent%2Fdam%2Fdita%2FTest%2FAChiu%2FTestMap2.ditamap&_=1658754219322"But not sure if there is a config that can be leveraged to prefix default "Destination Path". please let me know if you have come across a use case like this?     Thanks.

We recently built our career site on AEM. When potential candidates come to our new AEM site by clicking a trackable media source link (i.e., a link from our Facebook page), they then click a link on our new site which directs them to our applicant tracking system (ATS) to apply. That ATS tracks the source where our applications are coming from. In this example, it should track as Facebook. Currently, no source is being passed through from our new AEM website. Is there something we need to do on AEM to ensure the source code from our media URL (where the person actually originally came in from to AEM site) is passed through to our ATS? Thank you. 

Hi Everyone, I am new to this XML solution and trying to open the DITA file in Oxygen Editor. I have followed the steps provided on https://github.com/Adobe-TCS/DoX-Installer-for-AEMaaCSI am getting the option while trying to open the file from Assets - http://localhost:4502/assetdetails.html/content/dam/projects/test-proj/Test-topic.dita Then, I select to open with Oxygen Editor. It takes me to the Oxygen Editor tool, but not opening the file.How does this editing works? Any suggestion or tips are highly appreciated!Thanks!

Hi Team, Understand that there is common version framework for XML editor and Adobe AEM. We have the maximum 5 version settings in our Author environment that we would be keeping same and will not be configuring or altering this configuration. However for DITA, we have the requirement to keep n number of versions (Historical data) with in repository? could you please suggest any alternative to this (Except the alternate to keep n number of versions in configuration and purge content paths using Version purge)?Also any timelines to segregate the DITA versioning with AEM versioning framework? Thanks

Looking for some best practices for customizing map/topic templates to provide a guided authoring experience for my writers.

Hi,   After migration to 4.1version PDF templates drop-down is empty with no values. Could this possibly be a bug or something? 

While mapping ditaelements to AEM components, p nodes are not flattened, even though the flatten tag is there by default for topic/p in /libs/fmdita/config/elementmapping.xml.  According to the documentation, the p nodes will be flattened, if we enable it in the configuration (https://helpx.adobe.com/content/dam/help/en/xml-documentation-solution/4-0-3/Adobe-Experience-Manager-Guides_UUID_Installation-Configuration-Guide_EN.pdf). Did the below steps to enable the flattening. 1. Enabled "flattening.enabled"  in com.adobe.dxml.flattening.FlatteningConfigurationService2. Regenerated AEM site But stillthe node structure is coming expanded the resourcetype still remains same and not changed to fmdita/components/flattenedflatten property is not created Is there anything else I am missing here? 

We are trying to understand how to upgrade the version of AEM Guides in our AEMaaCS environment. AEM Guides is enabled (and was installed) by editing our Program in Cloud Manager and ticking the box for AEM Guides under "Solutions and Add-Ons". From the release notes, it states the following:   Upgrade your current Adobe Experience Manager Guides as a Cloud Service (later referred as AEM Guides as a Cloud Service) setup by performing the following steps: Check out the Cloud Services’ Git code and switch to the branch configured in the Cloud Services pipeline corresponding to the environment you want to upgrade. Update <dox.version> property in /dox/dox.installer/pom.xml file of your Cloud Services Git code to 2022.9.178. Commit the changes and run the Cloud Services pipeline to upgrade to the latest release of AEM Guides as a Cloud Service. However when I do step #1, I see no folder path for /dox/dox.installer. Where is this located? Are we looking