Rhythmyx 7.32 20190306 Patch

Change Description

[RHYT-1620] - Change missing landing page error to warning and set maximum times to log

The <InstallDir>/rxconfig/Server/Navigation.properties file contains a setting to turn on or off making a Landing Page a mandatory property for a NavOn.  When the navon.landingpage.required is set to true, the system will log up to 100 errors for any NavOn items that are detected to not have a Landing Page set.  When the property is set to false, Landing Page's will not be required and no errors will be logged if a NavOn has no landing page set.  A previous patch introduced this property and log limit, but the 100 item limit was not correctly implemented.  This patch corrects that problem and limits the number of errors that get reported to a maximum of 100.  

[RHYT-1852] - Pages with assembly errors are getting published

Prior to applying this patch, if an assembly error occurred in the bindings of a Page, Snippet, or Global template it was possible for the error and stack trace to be rendered and published as a successful publish.  This problem has been corrected in this patch. 

[RHYT-2579] - The Repository Consistency Checker report is invalid after running the revision removal task

The Repository Consistency Checker is an Admin tool that can be used to verify the state of Revisions of all content types in a Rhythmyx content repository.  The report was created to detect and correct problems with revisions in prior releases of the software.  When using the Revision Purge task to remove older versions of content that are not needed or wanted in the repository, the Repository Consistency Checker would incorrectly detect the correctly removed revisions as being problems and would attempt to recreate the missing versions. After applying this patch, the Repository Consistency Checker will only check current, tip, and public revisions for correctness and will no longer treat removed revisions as problems.

[RHYT-2580] - rxfixnextnumber needs to clear and reset the TEMPIDS table

An issue was reported with the PSX_TEMPIDS table that is used for ID generation for some types of objects (Acls and Guids) within the system.  It was possible for temporary id blocks to be left in this table and for the ID key to be set to astronomically high values.  This issue would eventually lead to failures in ID generation that would prevent new Acl's and Guids from being created.  To correct this database issue, the Next Number rxfix in the Admin tools has been updated to cleanup the TEMPIDS table and to auto correct the next number entry for TEMPIDS.  A new startup process has been created that will run the Next Number auto correction at system startup on the System Master to auto correct this problem if it exists on customer instances.   

[RHYT-2584] - Slow performance in Workbench cataloging Content Types and Templates after patching under Jetty

One of several Jetty performance updates included with this patch, this update improves performance of the first open of Templates or Content Types in the Workbench tool by 33% or greater. Several updates were made related to database transactions, and caching behavior for the Workbench in general, but also specifically with the Jetty server configuration. If you do not see a performance improvement with the Workbench after applying this patch, please create a support ticket to report the issue. A new cache warming process was added to the server startup to pre-load high frequency cacheable objects.  This process will right to the server.log and will indicate the performance gain after adding items to the cache. 

[RHYT-2589] - Security: Commons File Upload is out of date needs updated for security vulnerabilities

The Apache Commons File Upload component has been updated to mitigate several security vulnerabilities in the library.  The version after patching is 1.4.  This library is used by several features but primarily to handle uploading files and images to content items. 

[RHYT-2598] - DCE: User found the rollover icon descriptions for TinyMCE hard to read / unreadable

The default syling for the tooltip on the TinyMCE toolbar has been improved to be higher contrast and more legible.  This should improve the acessibility of the Editor. 

[RHYT-2600] - Taxonomy: Taxon's can be archived but can't be deleted if they have ever been used

An issue was reported where unwanted Taxonomy Node's could never be deleted if they were ever used.  This was true even if the Taxonomy Node had been removed from all existing content item revisions.  To mitigate this problem the functionality of the Delete taxon feature has been changed:  After applying the patch, when the delete option is selected, a prompt will be displayed that asks if the user would like to permanently delete the taxon from all revisions of content items. If the user selects yes, the Taxon will be permanently deleted.  If Taxonomy tags are needed to be preserved, use the archive Taxon option instead of delete. 

[RHYT-2602] - Configure the Jetty CachingWebAppClassLoader by default for improved performance

A performance issue was discovered where resource caching was not enabled when running under the Jetty server profile.  This lack of application caching could cause performance issues for frequently accessed resources, something that the product does frequently.  After patching, resource caching will be turned on by default.  This is configured via the <InstallDir>/jetty/base/webapps/Rhythmyx.xml application context file. 

[RHYT-2591] - Microsoft SQL Server 2017 Support Certification

Effective this patch level Rhythmyx is now Support Certified on Microsoft SQL Server 2017.  Customer's migrating from Microsoft SQL Server 2008 or other versions will be able to upgrade/migrate their Microsoft SQL Server version with full Percussion support of the application on the 2017 version of SQL Server. 

[RHYT-2595] - tools.list deprecated and removed in latest velocity tools updates - please provide an alternative

Several customers reported a major impact from the deprecation and removal of the Velocity List Tool ($tools.list) in the updated Apache Velocity Tools introduced in the latest patch.  The list tool was removed by the Apache Velocity team, as the latest version of Velocity fully supports working with Arrays without needing a separate tool.   The impact of removal would require an update to all Global, Page, or Snippet templates that used $tools.list.  To help mitigate this problem for Percussion customers, and to encourage continued patching, this patch re-introduces a Percussion maintained $tools.list to the Velocity tools available on the system by default.  This should provide customers with access to the latest Velocity templating capabilities while still providing backwards compatibility to Templates that made use of $tools.list.

[RHYT-2596] - DCE: User was not able to AdHoc Assignee for any content item and push the item to workflow

A defect was reported where the AdHoc Assignee dialog no longer functioned after switching from the Content Explorer Applet to the Desktop Content Explorer.  This problem has been corrected and the Ad Hoc Assignee dialog will now function correctly in the Desktop Content Explorer. 

[RHYT-2599] - DCE: Cut and Paste in TinyMCE not working correctly

A defect was reported where Cut and Paste did not work correctly in the TinyMCE editor when running in the Desktop Content Explorer.  This problem has been corrected in this patch.  Note that the keyboard may be used for Cut, Copy, and Paste options on both PC and Mac clients.  CTRL-X, CTRL-C, CTRL-V on PC and COMMAND-X, COMMAND-C, COMMAND-V on a Mac.

[RHYT-2603] - Prevent Fix Next Number from running on Publishing Hub

As the system has been improved to self-heal the next number table on system startup, the startup process needs to blocked on the startup of Publishing Hubs and only run on the System Master.  With this patch the RX Fix tool will be blocked from executing on publishing hubs to avoid problems in the creation of publishing logs. 

[RHYT-2605] - Jetty does not include a work directory so system temp dir is used for JSPs

By default the Jetty application server will write compiled web applications and temporary files to the system temp directory.  This could cause problems on systems that don't exclude the system temp directory from Anti Virus applications.  The location also created problems with troubleshooting and performing clean restarts of the application server.  After applying this patch an <InstallDir>/jetty/base/work directory will be created and the application server will now use that location for it's temporary files.  Customer's should make sure that the <InstallDir>/jetty/base/work directory is excluded from active anti virus or other real time scanners or indexers to avoid performance and locking contention problems. 

[RHYT-2607] - DCE - TinyMCE vertical scrollbar cuts off on full size in the editor

A problem was reported where on some resolutions the vertical scroll bar in the Rich text editor would be "cut off" and not selectable at full width.  Some padding has been added to ensure that the scrollbar appears when the editor is full size. 

[RHYT-2608] - Error with sys_reports application when using the native Microsoft SQL Server JDBC driver

A problem was reported where the sys_reports application would fail to start when using the native Microsoft SQL Server JDBC driver.  This problem has been corrected in this patch. 

[RHYT-2609] - DCE should be updated so that JavaScript errors get written to the DCE log

An improvement was made to logging in the Desktop Content Explorer to write any JavaScript related errors to the DCE log file. 

Known Issues / Limitations

RHYT-2575 Workflow Notifications: Invalid notification template results in template source code being emailed

It is important to validate that Workflow Notifications have valid Velocity syntax when setting up custom notification templates.  Syntax errors will result in malformed notification messages.  This will be resolved in a future patch. 

RHYT-2574 Workflow Notification Content Item Velocity Bindings are only referenceable via ${fieldname} syntax

The bindings for notification templates currently require that ${fieldname} syntax be used to reference content item fields.  $fieldname $!fieldname or $!{fieldname} syntax does not currently work for these bindings.  This will be addressed in a future patch. 

RHYT-2576 Workflow Notifications - double links are sent if ${wflink} or $!{wflink} used intead of $wflink by template developer

When adding links to custom notification templates, the $wflink variable must be used.  $!wflink, ${wflink} or $!{wflink} will result in a second notification link being appended to the notification message.  This will be addressed in a future patch. 

RHYT-1935 - Folder with old name need to be removed manually after publishing.

Once a folder name is changed and publishing is done, the new folder is published to the publish location, however, the folder with the old name is still present in that location and currently needs to be removed manually.