This document contains notes about the changed functionality in EPiServer CMS SP2. For further informaton about the changes in other EPiServer CMS 5 versions, please read the release notes for that release.
EPiServer CMS Manager 22.214.171.124 is required to install EPiServer CMS 5 SP2.
EPiServer CMS Manager 126.96.36.199 will be automatically installed if the server is connected to the internet. An offline installation is also available if the server is not connected to the internet.
We only support upgrade of EPiServer CMS 5 sites to EPiServer CMS 5 SP2. A migration tool is now available as Release Candidate 1 for migrating EPiServer CMS 4.62 sites to EPiServer CMS 5 SP2. Download EPiServer CMS Migration Tool RC1.
EPiServer CMS 5 SP2 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://www.episerverworld.com/Support/Bug-List/ (partner access required).
EPiServer CMS 5 SP2 has been tested on 64-bit version of Windows 2003 Server, which is now officially supported. No special instructions are required for this scenario.
Some configuration changes have been implemented due to a requirement to support multiple sites in IIS with a single EPiServer CMS installation with all sites using the same start page. The requirement to use the same start page for the different sites makes it impossible to use the standard Enterprise-style configuration with multiple <site> sections in web.config, since each Enterprise site must have a unique start page.
Prior to EPiServer CMS 5 SP2, EPiServer CMS used the IIS application ID to identify the correct <site> section and it was impossible for two or more IIS sites to use the same <site> section. Each IIS site had a unique application ID.
An existing web.config file should continue to work unmodified, even though it is recommended to implement the changes above. Compatibility mechanisms are:
With the changes outlined above, several new configuration scenarios for EPiServer CMS are supported.
Note Scenario 2 also has a potential risk with the following web.config (very abbreviated). When configuring a single IIS site to respond to both www.company.com and www.othercompany.com, you have the possibility of entering an URL like http://www.company.com/othercompany, i.e. by the hostname you are identifying Site1, but the virtual path belongs to Site2. This will be regarded as an error and an exception is thrown.
<add name=”www.company.com” />
<siteSettings siteUrl=”http://www.company.com/company” />
<add name=”www.othercompany.com” />
<siteSettings siteUrl=”http://www.othercompany.com/othercompany” />
There are several changes affecting the properties in web.config. Further information about the settings in web.config can be found in the technical note Configuration in EPiServer CMS 5.