Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
This document contains notes about the changes in EPiServer CMS 5 SP2 RC. For release informaton regarding EPiServer CMS 5 R2, please refer to the Release Notes for EPiServer CMS 5 R2 .
Note that this is a release candidate. Please report any issues via the Developer Fourm on EPiServer World. |
As with EPiServer CMS 5 R2 SP1, installation and upgrade of EPiServer CMS 5 R2 SP2 RC is done with EPiServer Deployment Center. This is slightly different compared to EPiServer CMS 5 R2, which was installed with EPiServer Installation Manager. If you are upgrading from EPiServer CMS 5 R2, further information about Deployment Center can be found in the EPiServer CMS Installation and Deployment System Overview.
EPiServer CMS 5 R2 SP2 RC mainly contains bug fixes and no new functionality. A list of issues that have been solved in this release is available on EPiServer World. http://world.episerver.com/bugs (partner access required).
The ASP.NET output cache for files is now turned off by default in the EPiServer CMS 5 R2 SP2 release. Please note when upgrading to EPiServer 5 CMS R2 SP2 this update may require consideration.
In the EPiServer 5 R2 SP2 release a new attribute has been added on staticFile this is called enableOutputCache - turning this attribute on enables the output caching of ASP.NET files.
In versions EPiServer 5 CMS R2 and EPiServer 5 CMS R2 SP1 the output cache causes a problem where files were not getting updated until the server cache expires. (This only happened for files where expirationTime in web.config was set to a positive value - a workaround for this was to force cacheControl to “private”, or set expirationTime to a negative value).
For further background information see the post - Files being cached too aggressively in R2.
Further Information:
Http Caching strategies: VPP Files
Files being cached too aggressively in R2
Performance tweak Optimizing StaticFileHandler in EPiServer CMS 5 (part 2)
Performance tweak: Optimizing StaticFileHandler in EPiServer CMS 5 (part 1)
Some recommendations for cache configuration in IIS 7:
Configuring cache expiration on IIS 7.
EPiServer CMS 5 R2 SP2 RC now has full support for Internet Explorer 8 as a browser for editing.
Migrating EPiServer CMS 4.62 Sites to EPiServer CMS 5 R2 SP2 RC To migrate an EPiServer CMS 4.62 Web site to EPiServer CMS 5 R2 SP2 RC, it is first necessary to migrate to EPiServer CMS 5 R2 with EPiServer CMS Migration Tool 1.1.0.28. After that upgrade can be done to EPiServer CMS 5 R2 SP2 RC by following the relevant installation instructions. |