CM1 5.3 SR1 20180501 Patch

Patch ID - 5315_20180501

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:

Improvements in this patch:

Comments Widget Improvements

The Comments Form and the Comments widget have been improved to include a new Honeypot field for stopping SPAM and Bots from posting comments.  The Widgets were also updated for improved ADA/508 compliance.   The Comments widget now allows for the selection of a Heading style for comments. 

Screenshot of Comments Form with Honeypot field highlighted

Thumbnail Size for Images uploaded with the REST API or the Bulk Uploaded Gadget

A new configuration property has been added to support configuration of the default thumbnail size the Image thumbnails that get created for Images that are uploaded using the Bulk Upload Gadget or the Asset REST API.  After setting this property to a new value other than the default of 50 pixels, the Percussion Service must be restarted. 

Defects corrected in this patch:

[CMS-2919] - Creating a Blog using the CM1 Dashboard Blog Gadget doesn't use the Site's default file extension when creating the Blog's index page.

For customer's that have set the Default File Extension to html or another file extension, when creating new Blogs, the blog index Page will now correctly pick up the default file extension.  Previously the Blog landing page was always generated as "index".

[CMS-3850] - Accessibility - Comments Form - A 1.3.1 Info and Relationships - Input field is missing a description

The markup generated by the Comments Form was not using proper Label / Field markup.  This has been corrected such that the generated markup is ADA/508 compliant. 

[CMS-3926] - Images and Files Linked through Custom Widget's are not Approved on Page Approval

There was an issue where Custom Widgets that had File or Image fields, or content that had Managed Links to Assets were not Approved when the Page was Approved.  This forced content editors to manually Approve each linked Image or File Asset.  After the Patch, when the Page is Approved, the link Image and File Assets will also be Approved. 

[CMS-3935] - Count Folder Item Utility at /Rhythmyx/test/countFolderItem.jsp stopped working

The utility Page for counting the number of Pages or Items in a given folder was broken due to a prior Patch update.  This utility has been updated and will once again return the count of Pages in a given folder. 

[CMS-3940] - Accessibility: Comments Widget Doesn't Provide Ability to Choose Heading for Title Field

The Comments widget did not allow for selection of the heading style for the comment title field creating an ADA/508 compliance issue.  After the patch the element used to format the comment title can be configured in the Layout properties of the widget. 

[CMS-3942] - RxFix to clear bad folder and site ids on startup

Due to a defect corrected in a previous patch it was possible for some customers to have incorrect values left behind in the database that could cause Rich Text or HTML content to "disapear" from the published page.  The system will now look for any bad data left behind by that bug fix and will clean the database if any bad data is found at system startup. 

[CMS-3891] - Blog Index Page is very slow to load - it loads all blog posts in the markup

Customer's using the Blog list and also including the Page Summary in the listing reported significant performance issues with the Blog Landing Page on the published website as every image for every blog post's Page Summary was being referenced when the Page was rendered.  The Blog Index Page will now only include the Max Per Page blog posts in the static markup to prevent this rendering issue. 

Known Issue List

Deleted Managed Links

An issue exists for customers that have the Automated Managed Link feature turned on that can cause Page Approvals to fail after applying this Patch if a linked Asset has been deleted.  Affected customers would receive a "Cannot load PSComponentSummary for id: " error when attempting to approve a Page. 

To work around this problem, either temporarily disable the Automated Managed Link feature by setting the Server property to "false", or run the following SQL on the content repository database to remove "Orphaned" links. 



This issue will be resolved in the next CM1 patch. 

  • 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.  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 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.  Restarting the DTS after this change will resolve the APR related errors.

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


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

Navigation Skip Link - ADA/508 Validation Warnings

Some customers have reported Skip Link warnings after applying the patch.  This may be because the Navigation widget now generates the Skip Link by default with a tabindex of -1 to hide the Skip Link until website theme css has been updated.  If you encounter this warning, update the Layout properties of your Navigation widget and set the tabindex of the Skip Link to 1.  Then in your Design->web_resources\themename\theme.css make sure that you have styled the Skip Link. 

For example, this is the CSS used on the theme:

a.perc-navigation-skiplink {
a.perc-navigation-skiplink:focus, a.perc-navigation-skiplink:active {
color: #fff;
left: 0;
top: 0;
width: 30%;
height: auto;
margin: 10px 35%;
border-radius: 15px;
border:4px solid #ee5336;