Patch ID - 5315_20180405

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 or Rollup 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 is a minor patch that includes 2 additional defect corrections and 1 improvement. 


[CMS-3857] After applying the 20180315 Patch the Content Post Date is incorrectly updated to the last date that an item was published

If you have installed the 20180315 patch we highly recommend that you install this patch to resolve an issue where Publishing a Page could incorrectly set it's Post Override Date to the Publish date, overwriting the original value.  

[CMS-3855] Accessibility: Page - content end date metadata attribute being generated with a missing space

An accessibility issue was reported for Pages that have Calendar Start and End Date's configured.  There was a missing space in the End Date metadata attribute that caused user agents to report a parsing error. 


[CMS-3847] Improve the published metadata for a Page so that the date the Page was modified is included in the dcterms:modified property

The existing published metadata for a Page included the Created date but not the date that the Page was last modified in the CMS.  Add the dcterms:modified property so that remote search engines can pull the Pages last modified date from there, instead of from the published files last modified time (which will always be the last published date).

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.