CM1 5.3 SR1 20180621 Patch

Patch ID - 5315_20180621

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:

Select Desired Upload Folder From Image Widget

[CMS-3427] - Image widget should allow to choose folder for upload

The image widget has been updated to include an option to choose the desired upload folder.  This option is only present when first uploading a new image using the Image widget.

image widget

Global Variables Now Allow HTML Tags

[CMS-3329] - Global Variables do not allow HTML tags when published

Global Variables now allow for HTML code to be used for a variable on the published web site.

New Cookie Consent Widget and Dashboard Gadget

[CMS-4030] - Cookie Consent Widget

A Cookie Consent widget has been added which displays a consent dialog and optional links to privacy and cookie policy pages.  Please see the Cookie Consent widget page for more information.

[CMS-4032] - Cookie Consent Dashboard Gadget

A Cookie Consent gadget has been added which displays information regarding each entry and provides a way to export that information in .CSV format per site.  The Cookie Consent widget page also provides more information on the gadget.

[CMS-4113] - Widget Builder - Allow for Image, File, and Page link fields to be cleared

Widgets built with Widget Builder that include page, file, and image fields now offer a way to clear the value of those fields.

[CMS-4123] - Enable the requireHTTPS configuration property on the 5.3 SR1 Patch Stream

A new server property allows CM1 customers using HTTPS to force HTTP requests to HTTPS.  To configure this property, please see the Server Properties Reference page.

[CMS-4111] -  Maintenance Screens need to set 500 series HTTP status code so monitoring tools know there is a Maintenance error

The updated maintaince screens allow for improved monitoring services for SaaS customers.

[CMS-4031] -  DTS Service for Logging Cookie Consent

A new DTS service has been added which provides for storage of cookie consent entries made on the live site.

[CMS-4029] -  Change Google Analytics Gadget to not inject JavaScript into Page Templates

The Google Analytics gadget has been changed to not inject tags into pages and templates.  It is recommended that going forward customers apply Google Analytics tags to their pages and templates accordingly.

Defects Corrected in this Patch

[CMS-3461] - Help Document for CM1 File Widget needs updated screenshot

The File widget documentation on the help site was outdated and has been updated along with this patch release.

[CMS-3582] - Error messsage when invalid path search

When entering an invalid path in the CM1 Finder, a non-descriptive error was returned to the browser.  This has been corrected and an appropriate message is now displayed.

[CMS-3622] - Incorrect suggested URLs in the "Redirect Manager" popup (after moving a section/extlink)

For SaaS customers with Redirect Manager enabled, when deleting or moving section and external links an incorrect message dialog was displayed.  This dialog has been removed when deleting or moving section and external links.

[CMS-4104] - Staging Incremental publish fails with Null Pointer exception when deleted item is in queue

If an item that was deleted became stuck in the incremental publishing queue, the incremental publish would not run.  This has been corrected.

[CMS-4163] - Drop TLSv1 from the supported protocols -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2

TLSv1 reached its end of life as of June 30, 2018.  This protocol has been removed from the product as of 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.  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;