CM1 5.3 SR1 20181210 Patch

Patch ID - 5315_20181210

This is a cumulative/rollup patch for CM1 5.3 SR1 that includes defect corrections & enhancements. This patch includes an uninstall option to support rollback in the event the patch introduces a problem or issue. The patch can be downloaded from the Support portal. For instructions on installing or uninstalling the patch, please review the Readme file provided in the patch folder.  

An updated list of Known Issues can be found at the bottom of this page.

For details on bug fixes and improvements in previous patch updates, please see the release notes for prior patches.  Links to prior patch release notes are provided below:

Issues addressed in this patch:

CMS-5289 - Managed Links incorrectly cleaned up while Publishing is running

A regression was corrected in the Managed Link database cleanup work where the system was trying to incorrectly remove dead Managed Links while the publishing process was running.  This flooded log files with unecessary errors when publishing was run.  This problem has been corrected in this patch. 

CMS-5290 - In rare cases, after applying the patch users are unable to edit Pages or Templates

An issue was discoverred where in rare cases it was possible for the Patching process to leave Page templates in an uneditable state.  A root cause was identified and this edge case is resolved by this patch. 

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.
  • CMS-3389 - Customer using the secure sections feature will have problems starting the DTS after applying the patch.  Note that after patching, a Full Publish is required.  If after a Full Publish is completed, the Secure Section is not functioning, please following instructions provided in Fixing Issue with Secure Section doc.
  • 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 start.