CM1 5.3 SR1 20180409 Patch

Patch ID - 5315_20180409

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.

This is a culmulative or Rollup patch that includes all of the bug fixes and improvements delivered in previous patches for the 5.3 SR1 version. For details on bug fixes and improvments 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:

Most Read Blog Posts Widget & Blog Post Hit Tracking

The Blog Post widget has been updated to include a new tracking feature that can be used in combination with the new Most Read Articles widget. This feature can be leveraged to add a list of most popular Blog Posts on a site to your Blog List page or to other areas of your website. More information can be found in the documentation for the Widget's documentation page.

Blog List and Result List Updates

The Blog List and the Result List widget's have been updated to allow the "Entry(s)" label to be changed in the list results. The Result widget now also allows for the Locale to be selected when configuring the date format to better support International date formats.

Improved Audit Logging of Content Deletion

The system has been updated to record log entries when a Folder, Section, Page, or Asset is deleted from the system. These activities are now logged to the logs/AppServer/server.log file and will include the path to the Content that was deleted, the date and time, and the User Name of the user that performed the Delete operation.

Improvement in patch process:

Two minor improvement in the patch process were made for Linux system administrators applying the patch.

The install.sh and uninstall.sh files will now be executable by default.
The command to clear DTS Derby lock files has been consolidated to just one command that can be copy and pasted from the patch output when the patch fails to install because the Derby lock files are present (after verifying that the DTS is indeed shutdown).

Defects corrected in this patch:

[CMS-3801] - Copy Site / Delete Site Menu's Duplicated on Doubleclick of Same Site with Navigation Editor Open

This is a follow-up to an issue addressed in the previous patch where the menu's in the Navigation Editor were duplicated when switching between sites. This patch addresses the duplication issue when double clicking the same site.

[CMS-3858] - Session timeout warning or expiration dialog no longer being displayed

Session timeout warning dialog was not working after applying the latest patch. This has been corrected and the Extend Session dialogue will now be properly displayed.

[CMS-3861] - Navigation sort order not being respected after applying 3-15 or 4-5 2018 Patch

Changes to the navigation sort order made in the Navigation Editor or new navigation changes were not showing up until the navigation cache was cleared or the instance was restarted.

[CMS-3872] - Move Directory Widgets to Percussion Tray

The Directory widgets were only showing up when "All" widgets was selected in the Widget tray. This has been corrected and the widgets will now display alongside the "Percussion" widgets.

[CMS-3889] - Page AutoList Hide Historical Posts doesn't work if two Autolist Widgets are configured on Page

In instances where more than one Page Auto List was added to the same Page or Template, the Hide Historical Posts feature did not work for the 2nd Page Autolist. We recommend that customer's edit and save Page Auto lists after applying the patch to ensure that this update is applied.

[CMS-3896] - Allow no page name to be passed to PSCreateSiteSection as code now generates from configuration

For developers creating new sections via the Folder API, the Landing Page name is no longer required and the system Default Document file name will be used when a new section is created without the Landing Page name supplied.

[CMS-3898] - Fix up relationships with orphan owner or dependent on startup

The system will now auto correct "orphaned" content relationships that may have been created by deleted content or previous system bugs when the server starts up.

[CMS-3899] - Managed link href not converted to # in published page when dependent is not public.

After applying the previous patch Managed Links were not properly "dead-linking" links to archived or missing content. This issue also caused some local content to improperly hidden on publish.

[CMS-3902] - BouncyCastle configuration not picked up by SFTP Delivery Handler in latest patch

The security update to support publishing to hardened SFTP server was missing a file that prevented the configuration from working automatically after applying the patch. This has been corrected and therefore manual update of that file is no longer required.

[CMS-3911] - Archived Navigation Sections being published in the Nav after applying Patch

An error was introduced in the previous patch where it was possible for some archived section Landing Pages incorrectly published to the live site.

[CMS-3924] - Feed Info Service can hang and prevent CM1 Service from Shutting Down

The issue where if the service was stopped while the RSS Feed service was performing an operation, the service shutdown could hang and fail to properly shutdown has been addressed.

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.

e.g.

.

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 help.percussion.com theme:

a.perc-navigation-skiplink {
left:-999px;
position:absolute;
top:auto;
width:1px;
height:1px;
overflow:hidden;
z-index:-999;
}
a.perc-navigation-skiplink:focus, a.perc-navigation-skiplink:active {
color: #fff;
background-color:#133c55;
left: 0;
top: 0;
width: 30%;
height: auto;
overflow:auto;
margin: 10px 35%;
padding:5px;
border-radius: 15px;
border:4px solid #ee5336;
text-align:center;
font-size:1.2em;
z-index:999;
}