Release Notes

Patch ID - 5315_20180306

This is a cumulative patch for CM1 5.3 SR1 that includes defect corrections & minor enhancements. This patch includes an Uninstall option to support rollback in the event the Patch introduces a problem or issue. The patch may be downloaded from the Support portal.  For instructions on Installing or Uninstalling the Patch, please review the Patch Readme file.  An updated list of Known Issues can be found at the bottom of this page. 

This is a culmulative patch that includes all of the improvements delivered in previous patches for the 5.3 SR1 version.  For details on what was included in previous Patch updates, please see the release notes for prior patches.  Links to prior patch Release Notes are provided below:

Improvements in this Patch

This patch includes a couple of issues that did not make the cut for the prior patches and late breaking corrections for customer reported issues.


The forms widget has received another accessibility update, form fields with their id and name attributes configured, will render proper markup and title attributes are now rendered correctly.

SFTP Publishing

The SFTP delivery engine has been updated to support the latest SFTP security protocols being patched on Linux SFTP servers.

Rich Text Assets

An issue with preview of shared Rich Text assets has been corrected. Prior to the patch, previewing a Rich Text shared asset by itself would result in an 'undefined' error.   

A defect was corrected that would remove the class attribute from Managed Links in the Rich Text Editor.  After patching the system will no longer remove these attributes.

Page Autolist / General DTS / Live Widgets

A general ADA/508 complaint surrounding the iframe used for cross domain communications has been mitigated. 

Summary List of Issues Included in this Patch

[CMS-3077] - Form Widget should have a configuration for fields to include an aria label
[CMS-3200] - Accessibility issue CORS iframe
[CMS-3631] - Managed Links are incorrectly removing the class attribute on all generated a links
[CMS-3341] - SFTP client out of date - needs updated to support newer ciphers
[CMS-3624] - Preview of shared rich text asset throws undefined error
[CMS-3633] - Description of metadata item in MetadataDeliveryHandler outputs unreadable long number of  guid
7[CMS-3444] - Page Auto List Widget Receives Accessibility Error For empty iFrame
[CMS-3620] - Web_resources typo in 03-01 patch - pushing some files to wrong directory

Known Issue List

  • CMS-3614 - After applying the Patch end users may need to Clear their browser cache in the CM1 user interface in order to see the new changes to the Rich text Editor and plugins, ideally this should be automated. 
  • CMS-3389 - Customer using the secure sections feature will have problems starting the DTS after applying the patch.  They should contact technical support for a work around prior to attempting to patch their instance. 
  • CMS-3257 Customers using the MySQL database server as the backing database for the DTS, will lose the MySQL Connector jar if it was previously placed into the <InstallDir>/Deployment/Server/perc-lib directory.  To correct this problem the MySQL Connector for Java may be installed or symlinked into the <InstallDir>/Deployment/Server/lib directory.  Percussion does not include this connector as part of our installation due to license incompatibility issues.
  • CMS-3490 - Customers Patching the DTS on Windows Servers will need to reinstall the DTS Windows service by using the "<InstallDir>\Deployment\Server\bin\service.bat remove" and  "<InstallDir>\Deployment\Server\bin\service.bat install" commands.  Once the service has been successfully re-installed, the Percussion DTS Windows Service will correctly start. 
  • CMS-3280 -Customer's running the DTS on a server that also has native APR libraries installed, may run into problems starting the DTS HTTPS connector.   The HTTPS connector may fail to start with an invalid Keystore configuration.  To resolve this issue, remove or comment out the following line in the <InstallDir>/Deployment/Server/conf/server.xml file:

<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/>


<!-- <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"/> -->.  Restarting the DTS after this change will resolve the APR related errors.

Leave a comment