CM System Patch for Version 7.3 build 201306R01 (Patch id: B-01331)


The latest patch for version 7.3 is available and can be downloaded using the links below.

Important Note: This patch includes an upgrade to Ephox EditLive! (Version 9), which is compatible with Java7u45 as long as the java security settings are set to “medium”

The Read Me for reference:

Rhythmyx Patch for Version 7.3.0 build 201306R01
Patch id: B-01331
Patch Install Toolkit version: 1.0


  1. Shutdown or close all Rhythmyx applications (server, workbench, etc.).

  2. Install the Rhythmyx Patch Install Toolkit by extracting to {installation root}.
    If you do not have the toolkit, contact Percussion Software Technical Support to obtain it. If the toolkit
    is already installed, go directly to step 2. The toolkit is installed if the following directory exists:
    {installation root}/Patch/InstallToolkit.

  3. Extract into {installation root}/Patch.

  4. Go to {installation root}/Patch/B-01331 and run install.bat (Windows) or (Unix) in order to install
    the patch. Uninstall.bat/.sh can be used to uninstall the patch. On Unix systems, the user must have execute
    permissions in order to launch the shell script(s). During both install and uninstall, the following warning
    message will be seen in the console:

    “Unable to locate tools.jar. Expected to find it in {installation root}\lib ools.jar.”

    This message is expected and can be ignored.

  5. See “Additional Configuration” for manual steps which may be required after installing/uninstalling the patch.

Additional Configuration:

In an item link relationship, this patch will resolve site and folder ids appropriately even if these ids are
incorrect or if they are not selected from Ephox EditLive content browser. The system can automatically resolve any broken
links based on item location in the folder structure, information from the current page being assembled, information
from the include folder and site selected in Ephox EditLive content browser.

By default this feature is disabled. To enable add autofixFolderSiteIds=true property in 
Root/rxconfig/Server/ file.

This new feature allows the system to resolve the link path based on several criteria:

1.	Only one item: If an item is in only one folder in the entire system this feature should always link to only that 

2.	One or more copy of an item: If a copy of an item is created using copy as link, the system automatically 
	calculates the right item version to link to even if the include folder or site was not selected in the content 
	browser.  If include folder or site was not selected, the system will assume that the link is to the version that is 
	in the closest folder path. Please note that for some unknown reason if such links are still broken, recreating the 
	links by including the folder path in the content browser will ensure that the correct version of the item is linked.  

	Example use case: The original version of an item is in the local site, but you want to link to the copy of this 
	item from another site.

3. 	Multiple sites with same folder path: There may be cases where more than one site is configured pointing to the 
	same folder path. Such sites configurations allow publish the same site content to multiple servers like staging, qa 
	or production. If you currently have this setup, turning on autofixFolderSiteIds feature will log errors to indicate 
	that additional configuration is required. If this feature is enabled in the system and with multiple sites referring 
	to same folder path, we now need to decide the default site and configure rest of the site in groups.  For example, 
	in a Staging and Public sites setup where both configured from same folder path, the public site would be the default 
	as that is the site to which the item will be linked if no site information is provided and staging site need to be 
	configured as site group. There default site must not be configured. The sites not configured in groups are treated 
	as default sites. The site groups are configured using siteGroups.<groupName>=<siteid>[,siteid] property in 
	Root/rxconfig/Server/ file.  For example if staging site id is 305 then in file to 
	create staging site group you need to have siteGroups.staging=305.  In case of multiple staging sites in the system, 
	separate the site ids by comma as siteGroups.staging=305,307.
Modify User Velocity Macros
	An old form of $rx.location.generate used in imghelp macro which comes with the Fast Forward User Velocity macros file does 
	not handle items in multiple folders well.  To make use of the folder and site fixup here, you should change this to pass 
	$sys.assemblyItem as a parameter.  This allows the function to accesse the original site and folderid of the page in caluclating
	the correct folder and site for the passed in node.  Some of the other parameters on this method are no longer required as the
	values can be obtained from the $sys.assemblyItem.  This should be changed elswhere in the template code it is also used with these 
	same parameters.
	Change the following line in User Velocity Macros:
	#macro(imghelp $image $template)$rx.location.generate($template, $image, $rx.location.folderPath($image),$sys.assemblyItem.getFilter().getName(), $sys.assemblyItem.getSiteId().longValue(), $tools.number.toNumber($tools.list.get($sys.params.get('sys_context'), 0)) )#end
	#macro(imghelp $image $template)$rx.location.generate($sys.assemblyItem, $template, $image)#end

The extra warning messages and prevention of table cloning on field deletion will not be available unless Workbench is upgraded. This patch
provides a new workbench version which can be downloaded from the server from the following path.

Review the separate document outlining the changes to Ephox and check if inline template code requires modifications.

Fixes Included:

B-01300 Changed parser to remove extra HTMLTidy process and handle content that may not be well formed xml.
Ephox has been updated also to version 9 in this process. This change has many improvements over the existing
field processing. White space and other non xml content are now handled with minimal re-formatting. Spacing
from inline templates is now passed through without change so templates should be reviewed if a particular
spacing/format is require.
See the separate document for the full information about the changes.

B-01321 Preview is not passing additional HTTP Parameters
Extra html parameters set up in workbench for Menus are now passed through to preview url making them available to template.

B-01294 FTP unpublish issue
The file path for unpublish was sometimes miscalculated with ftp publishing causing unpublish failure.

D-01189 Patch for folder and site ids improvements and fixes
See Additional Configuration

D-01024 In content editor, calendar control’s Today button does not populate current date calendar control
Control has been updated to a jquery control. The “time” control parameter is still used to indicate if the
date or both date and time should be used.

D-01226 Adding a field to Contact Content type - Workbench Freezes
Adding and Removing fields no longer causes entire content table to be copied. Changing field data type will still clone
and recreate table. A warning is provided as this can take a long time for large content tables and those containing binaries.

D-01256 System validates for email id for notification even if notification is not enabled in workflow transition
Email address for all uses in transition role was being retrieved from LDAP even when no notification was being sent.

D-01298 Error in assembly is not causing publishing failure
Some errors in assembly were not triggering failure of page to be published and error message would be delivered.

Fixes Included from Patch B-01299:

D-01189 Publishing to Staging server de-activates “Rx inline links”

Fixes Included from Patch B-01297:

D-01282 Update 7.3 patch 7.3 Install may not overwrite Ephox plugin jars

Fixes Included from Patch B-01267:

D-01257 : Inline controls in Ephox EditLive 8.1 broken when the edit live field is in a field group

Do you know if ephox version 9 is also compatible with java 1.6 update 65? I think we’re going to start paying for support to stay on java 1.6.