Print

This section contains information about the latest release of the module such as release history, changes made to the current version and the list of known issues.

1.  Release History

November 18, 2009

Staging module v5.4.0 rev.091111 for Sitecore CMS 6 is released.

Sitecore versions: tested with Sitecore 6.0.1 rev.090317 and Sitecore 6.1.0 rev.090821.

New Features:

• The module now supports staging for any language.

Issues resolved:

• Partial cache clearing didn’t work properly.
• If the staging module was provided with invalid credentials, the module did not display an appropriate error in the log.
• Full cache clearing might remove user runtime settings on slave server.
• An exception could occur during a publishing operation when a content delivery server did not include the core or master databases.
• Error was not displayed in Cache section of Staging console when the module was configured with incorrect credentials.
• Staging operations could fail if the PublishTarget field did not contain the ID of an item.
• Staging module couldn’t upload files with 0 size to the slave server.
• ‘Date time format’ setting for ftp transfer was never used and now is removed. 

July 9, 2008

Staging module v5.4.0 rev.080625 for Sitecore CMS 6 is released.

Sitecore versions: tested with Sitecore CMS 6.0.

2.  Known Issues

The following known issues has been reported so far:

1. All transferred files appear in the UPPER case. This is done in order to support the Danish letters Æ, Ø and Å.
2. The Staging Module tries to recreate existing folders on slave server during uploading in FTP mode.
   You can notice the “service tries to create an existent folder” errors in the IIS or Windows logs (550 is FTP error code, 183 is Windows error code). This is caused by limitation of the FTP client and is just a report; the operation doesn’t perform any harmful actions.
3. The Sitecore may consider the status.xml file an XML control.
   It is possible that Sitecore tries to verify whether the Staging status.xml file is an XML control. Under certain circumstances, this file may be locked and Sitecore may show an error message in the browser or log file. To fix this, reconfigure the “/sitecore modules” control source in the controlSources section of the web.config file according to your solution. It should not include the “/sitecore modules/staging” folder.