cm1 5.3 SR1 5315_20190901Patch

Patch ID - 5315_20190901

This is a cumulative/rollup patch for CM1 5.3 SR1.

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-5756] - Performance - Add caching for the Navigation Is Landing Page Property, to prevent the Navigation tree being crawled unnecessarily in large Navigation trees

Customers with large Blog and Navigation hierarchies reported serious declines in performance the larger the Navigation / Blog tree became. A performance optimization was identified and 2 new cache regions were introduced specifically to improve overall system performance is these types of deployments.  With this additional functionality you may need to adjust the current default memory settings.  Please see Common Issues / Workarounds page for instructions on how to increase available memory.  

[CMS-5851] - Meta-data popup dialog doesn't close when filename value is updated

A regression was identified related to the Redirect Management update in the 5315_20190704 patch that would prevent the Page / Template Metadata dialog from closing properly. This issue is corrected in this patch and affected Percussion Cloud customers.

[CMS-5852] - Missing images/file/page listing after last selected one

A regression was identified related to a Bulk Upload Gadget update in the 5315_20190704 patch that would cause the Asset / Page selection dialog to display only the most recently selected asset instead of all Assets / Pages as was expected. This issue is corrected in this patch.

[CMS-5859] - Change in filename doesn't warn for redirect update

A regression was identified related to the Redirect Management update in the 5315_20190704 patch that would prevent Auto Generated Redirects to be generated when Pages were renamed. This issue is corrected in this Patch and affected Percussion Cloud customers.

[CMS-5862] - Performance - Auto tune Cache is not including the item region

The Cache Auto Tuner was not including the item cache in it's optimization of cache settings at startup. This could result in under tuned item cache for customers with large amounts of content resulting in less than desirable performance. This issue is corrected in this patch. Note that in order to fully take advantage of this update. The Percussion CMS service should be Started, then Stopped once fully started, and then started a second time. The reason for this is that the cache is tuned at startup, but is not applied until the service is stopped and started again.  With this additional functionality you may need to adjust the current default memory settings.  Please see Common Issues / Workarounds page for instructions on how to increase available memory.  

Installation Notes & Common Issues

Database Updates

Beginning with Patch 5315_20181221 the update engine now supports database schema updates as part of the update process. As a result the patch relies on the installer database configuration file to successfully run. In environments where the database setup has changed, or a server / RDBMS migration has occurred, it is possible that the installation database configuration file may be out of date which would cause the patch to fail. To avoid this problem, prior to installing the Patch verify that the contents of the <InstallDir>/rxconfig/Installer/rxrepository.properties file are correct. Updating this file is covered in the Appendix A section of the Migrating Percussion Environments help page.

Common Issues / Workarounds

Updates can occasionally fail to apply for a variety of reasons. To help streamline troubleshooting, we have created a new Common Issues / Workarounds page to collect the steps to correct these issues if you run into them when patching. As always if you run into a problem applying a patch, please contact the Technical Support team at support@percussion.com, and they will be happy to assist.

Known Issue List

  • CMS-5294 - The Ignore Unmodified Assets publishing feature does not work correctly on systems with 2000 or more Assets. We recommend that this option be unchecked in your publishing configuration to avoid publishing failures.

  • 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-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 

Uninstalling the Patch

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. Note: To install a patch after uninstalling an existing patch, uninstall the existing patch, start the service back up normal, shut the service down and then install a patch.