Return to

Release Notes (Sitecore CMS 5.1.1 and CMS 5.2)

This document includes the latest information concerning the Staging module.

November 3, 2006

Staging module v5.2.1 for Sitecore 5.1.1/5.2 is released.

April 20, 2006

Staging module v5.2 for Sitecore 5.2 is released.

February 13, 2006

Staging module v5.1.1 is released.

1.  Change Log

This section describes changes in different versions.

1.1.  New Release - 5.2

Version 5.2 works with Sitecore 5.2. MS SQL and FireBird servers are supported.

Changes and Fixes:

Documentation changes:

1.2.  Between 5.1 and 5.1.1

This version will work with Sitecore, and running on SQL Server and solves the following issues.

Changes and Fixes:

Documentation changes:

1.3.  Between 5.2 and 5.2.1

This version has been tested with Sitecore and Sitecore and is expected to work with Sitecore 5.2.0.x and Sitecore 5.1.1.x releases.

Changes and Fixes:


1.4.  Between 5.0 and 5.1

This release includes the following changes since the previous release of the Staging module:  

2.  Known Issues

  1. All transferred files appear in UPPER case. This is in order to support danish letters Æ Ø and Å.
  2. Staging Console always reports that the files are being downloaded, regardless of whether they are actually downloaded or not. You can see the actual actions performed in the log file.
  3. FTP Download in passive mode downloads files no matter if the file size has changed or not.

  4. If you set the Delete Destination File Before Upload setting to true, the Staging module will upload/download (in FTP passive mode) all files no matter if their size has changed or not.
  5. Note: observed only with Staging 5.2 working with FireBird installation.

    Due to an internal error in FireBird runtime, it is not always possible to get exclusive access to the database. This should not be considered as a critical error or unstable behavior, since in such case the scheduled task will keep trying to perform staging until successful.

  6. A license error may occur the first time the Staging module is started. Restarting IIS solves the problem.

  7. Renamed files are not tracked.

  8. After ASP.NET recycles application domain on the slave server, the module may stop functioning properly. This is a problem in the Firebird embedded engine. Workaround: restart IIS.