Agencies
Services
Version 6.5.14
Adobe Experience Manager has been updated from v6.5.13 to v6.5.14. This update includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements.
Highlights
Experience Manager 6.5.14.0 includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements, that are released since the initial availability of 6.5 in April 2019.
Bug Fixes
- Unable to add or view tags for PDF files
- When you upload a duplicate asset to the Digital Asset Management repository and Experience Manager detects and provides an option to delete the duplicate asset, the original asset also gets deleted from the repository.
- Unable to save Asset properties until you click Save & Close twice
- Experience Manager does not save the folder metadata correctly when you specify special characters in multifields.
- Screen reader does not read Mute and Unmute button on video using Dynamic Media component.
- Unable to apply a saved policy to one of the containers of an editable template to let you add Dynamic Media components.
- Assets not getting uploaded to Dynamic Media account because of missing upload parameter.
- When a file is attached to a multi-panel adaptive form and a draft of the adaptive form is saved, an error occurs
- In a Document of Record (DoR), some values in a table are truncated.
- In Adaptive Forms, radio button and checkbox are not in tab order
- When a user uploads a PDF to an Adaptive Form, the AEM Forms server becomes unresponsive
- Content Fragments enumeration field validation issue the first time that the content fragment is loaded.
- In the Content Fragment dialog box, under Properties, the Content Fragment field does not retain the saved path in the selection pop-up.
- When creating or editing a new content fragment in the Content Fragment editor, by way of the Dispatcher, the content fragment model is not saved. Furthermore, the Content Fragment editor is not closed, and an error is displayed in the browser log