Upgrade Instructions
The patch is provided to upgrade projects created with Sitefinity version 3.0 or later.
In order to apply the patch, please follow these instructions:
1.
BACK UP the project! It is extremely important that a backup is done of both the files and the database before installing anything new. This ensures that whenever anything goes wrong, no information is lost.
2.
UNZIP the patch archive in a temporary folder! Then copy all the unzipped folders and files in the project folder. If you unzip directly in the project folder, you will have to replace all permissions as the new files do not inherit the project's permissions.
3.
IMPORTANT. You need to check that changes you made to some of the project files are not replaced during the upgrade. Please note that
we are no longer overriding your control templates. By default, Sitefinity will use its
own embedded templates both for the back-end and the front-end. In order to use your customized control templates,
you should map a view to each of them. This is described in the KB Article
How to map a view to an external template, in Sitefinity?
4. Compare your original project
web.config file to the
new_web.config file from the archive. Change your original
web.config to reflect the changes introduced in the latest Sitefinity version. You can use any comparison tool you like.
The changes to the web.config since the 3.7 SP2 version of Sitefinity are in the dataAccess section of the web.config file. Depending on your database engine here are the changes:
Old section:
<dataAccess defaultConnection="DefaultConnection">
<connections>
<add name="DefaultConnection" driver="Nolics.ORMapper.DataProviders.SqlServer2005Provider" connectionStringName="Sitefinity" />
<add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
</connections>
Changes for SQLServer2005/2008:
<dataAccess defaultConnection="DefaultConnection">
<connections>
<add name="DefaultConnection" driver="Telerik.DataAccess.Providers.ExtendedSqlServer2005Provider, Telerik.DataAccess" connectionStringName="Sitefinity" />
<add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
</connections>
</dataAccess>
Changes for SQL 2000:
<dataAccess defaultConnection="DefaultConnection">
<connections>
<add name="DefaultConnection" driver="Telerik.DataAccess.Providers.ExtendedSqlServer2000Provider, Telerik.DataAccess" connectionStringName="Sitefinity" />
<add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
</connections>
</dataAccess>
Changes for Oracle:
<dataAccess defaultConnection="DefaultConnection">
<connections>
<add name="DefaultConnection" driver="Telerik.DataAccess.DefaultOracleProvider, Telerik.DataAccess.OracleProvider" connectionStringName="Sitefinity" />
<add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
</connections>
</dataAccess>
Changes for MySQL:
<dataAccess defaultConnection="DefaultConnection">
<connections>
<add name="DefaultConnection" driver="Telerik.DataAccess.MySQLProvider, Telerik.MySQLProvider" connectionStringName="Sitefinity" />
<add name="GenericContentConnection" driver="Telerik.Cms.Engine.Data.Providers.GCSql2005Provider, Telerik.Cms.Engine.Data" connectionStringName="Sitefinity" />
</connections>
</dataAccess>
5. Merge the existing file ~/Sitefinity/Admin/Default.aspx.cs with the same from the archive. There are some modifications in the code there, that you need to have, otherwise you will get an error in the Admin pages. If you do not have any custom code in that file, you can safely replace it with the one in the archive.
You need to start the Search Indexes. Otherwise, you will get error messages if you try to publish content. To start the Search Indexes, go to the administration area, Administration tab, section Services -> Search and start all indexes by clicking on the Start indexing links.
6. Open the folder ~/Sitefinity/ServiceAssemblies and make sure you delete the assembly there. When you initialize the Newsletters module, it will be recreated. If you don't do this before you apply the patch, you'll get the following error:
"Unable to load one or more of the requested types. Retrieve the LoaderExceptionsProperty for more information."
7. If you have several Sitefinity projects connected to one database, please make sure you upgrade all of the projects to the same version.
8. If you are moving your files from Sitefinity 3.7 to Sitefinity 3.7 SP3, please make sure that you move App_Data\Wikis.xml file as well. This file is the storage file for the Wiki module.
TROUBLESHOOTING
- Upgrading from Sitefinity 3.2 - How to solve problems with broken links to Images & Documents Library items after upgrade from 3.2 to 3.5 and later versions