Fixed issues in the 2024.12.0 release
This article covers the bugs fixed in various areas of the 2024.12.0 release of ÃÛ¶¹ÊÓƵ Experience Manager Guides as a Cloud Service.
Learn about upgrade instructions for the 2024.12.0 release.
Authoring
- DITA map creation on a UUID instance fails when
xmleditor.uniquefilenames
is enabled inXMLEditorConfig
. (21201) - When closing a file, comments and labels added in the Save Changes and Unlock File dialog box are not getting saved in the Version History with the new version. This is specific to a use case where Ask for Check-in on Close or Ask for New Version on Close is enabled in
XMLEditorConfig
. (20065) - Document state marked as Done reverts back to Draft before saving a new version, resulting in the Done state not persisting in any document versions. (20006)
- Unable to add a PDF file as an image reference in a topic in the Web Editor. (21206)
- Selecting a DITA file in the Assets UI shows the Open in FrameMaker option, even when disabled in the configuration. (20082)
Publishing
- In the Native PDF output, chapter titles are missing from the TOC, leading to an incorrect hierarchy. (21840)
Management
- Resource leaks occur due to Unclosed ResourceResolver errors in logs. (18488)
- When creating a new or duplicate baseline, labels are displayed in a random order. (19307)
Baseline
- Editing and then saving a baseline on a cloud setup timesout after 1 minute if the baseline has large number of topics or maps. (19558)
Translation
- Map translation using baseline becomes slow and eventually fails to load the list of all the associated topics and maps files. (19733)
Known issues with workaround
ÃÛ¶¹ÊÓƵ has identified the following known issues in the 2024.12.0 release of ÃÛ¶¹ÊÓƵ Experience Manager Guides as a Cloud Service.
Project creation fails while processing content translation
While sending content for translation, the project creation fails with the following log errors:
com.adobe.cq.wcm.translation.impl.TranslationPrepareResource
Error while processing Translation project
com.adobe.cq.projects.api.ProjectException
: Unable to create the project
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException
: OakAccess0000
: Access denied
Workaround: To resolve this issue, perform the following workaround steps:
-
Add a repoinit file. In case, the file does not exist, create the file by performing the .
-
Add the following line in the file and deploy the code:
code language-none { "scripts": [ "set principal ACL for translation-job-service\n allow jcr:all on /home/users/system/cq:services/internal/translation\nend" ] }
-
Test the translation after deployment.