This article contains a list of issues resolved in the December 2022 release and Summer 2020 release of Adobe FrameMaker Publishing Server and subsequent patch releases.
Check FrameMaker community for solutions, workarounds, or any late-breaking information.
Check FrameMaker Publishing Server User Guide for detailed explanation of features and "how-to" information.
December 2022 release
- Fixed security vulnerabilities related to the authentication mechanism. More details about the security fixes are available in Adobe Security Bulletin - APSB24-38.
- REST APIs are now case-sensitive, and URLs will also need to be case-sensitive. Check Work with FMPS using REST APIs for more details.
- Workers now require authentication at the time of launch. Check the Launch the client using the StartWorker.bat file section in Configure the client components to learn more about the configuration changes.
Update 3 is only supported on Microsoft Windows Server 2022.
- Fixed security vulnerabilities related to the authentication mechanism. More details about the security fixes are available in Adobe Security Bulletin - APSB24-10.
- Fixed security vulnerabilities related to the authentication mechanism. More details about the security fixes are available in Adobe Security Bulletin - APSB23-58 (Ref – 13557).
Summer 2020 release
- Fixed security vulnerabilities related to the authentication mechanism. Fixed security vulnerabilities related to the authentication mechanism. More details about the security fixes are available in Adobe Security Bulletin - APSB24-38.
- REST APIs are now case-sensitive, and URLs will also need to be case-sensitive. Check Work with FMPS using REST APIs for more details.
- Workers now require authentication at the time of launch. Check the Launch the client using the StartWorker.bat file section in Configure the client components to learn more about the configuration changes.
Update 4 is only supported on Microsoft Windows Server 2022.
- Fixed security vulnerabilities related to the authentication mechanism.
New features and enhancements
Publish output using baseline in Adobe Experience Manager Guides
Publishing has been made more powerful in FrameMaker Publishing Server with the new feature to publish output using baselines in Experience Manager Guides. The baseline is a version of your topics and assets in AEM that can be used for publishing. FMPS now supports publishing content directly from Experience Manager Guides in PDF, HTML5, or ePub formats using a given baseline instead of syncing to the latest version. If you don't specify any baseline at the time of publishing, then only the output is published using the latest version.
For more information, see the Publish output using a Baseline with FrameMaker Publishing Server section in the Using Adobe Experience Manager Guides guide.
Fixed issues
- Generating PDF output using Experience Manager Guides fails when a PDF file with the same name already exists on the AEM server.
(Ref – 10135) - Task created with a preset that contains a DITAVAL or .sts file having a Unicode character in the name is not executed.
(Ref – 10146) - Requests failed and user logs not synced properly for AEM tasks having a large book or DITA map.
(Ref – 9806) - Server connection not working properly for https protocol due to invalid path of SSL Certificate.
(Ref – 10769)
Before installing FrameMaker Publishing Server Update 1, clean the MongoDB instance. This is required to fix some critical security issues.
Fixed issues
- Local input (source) directory gets deleted on completion of AEM Site output generation task.
(Ref – 9511) - Logging in with different casing in username, such as domain\username or domain\UserName, creates two different user areas.
(Ref – 9506) - When using FrameMaker Publishing Server to generate PDF output through Experience Manager Guides, FrameMaker Publishing Server fails to upload the PDF output on AEM Server.
(Ref – 9373) - Publishing DITA map to PDF is interrupted with a dialog to save unsaved files before proceeding.
(Ref – 9210) - Performance issues noticed when FrameMaker Publishing Server is in an idle state for few hours and while running cron jobs.
(Ref – 9133, 9203) - FrameMaker Publishing Server crashes when an API call is made to delete a non-existing task.
(Ref – 9256)
