You actually do not need to place the new assemblies in the Project Manager bin folder. Please, check the sf_CmsVariables
table in the database, and make sure the value of the
variable is equal to the build number of Sitefinity 3.1 SP2 which is 1482
. If this is not so, then the upgrade has not been successful and you would need to start again with the upgrading. If the number is the same, please send us your database to investigate it locally.
Just as a reminder, here are the steps you should follow for an upgrade:
1. Install Sitefinity 3.1 SP2.
2. Create a new project.
3. Click Go to administer the project. At the first wizard step, you should enter the database connection settings here (to point to the original project database).
Note that if you
are using SQL Express, at the first wizard step, you should copy the
.mdf file from your old App_Data folder to the new project App_Data
If you are using SQL Server, enter the database connection settings here (to point to the old database).
using Windows Authentication, make sure the account that runs the
ASPNET process has the appropriate permissions to the database.
4. Copy all custom files from your old project to the new
project. These include user controls, scripts, images, .css files, .dll
5. If you have made any modifications in your old project Admin folder and web.config file, add those to the new project.
6. Copy your old project .master files to the new project App_Master folder.
7. In each .master file, remove the obsolete <div
class="cmsWrapper"> tag that was required in versions prior to 3.1.
A form adapter is now used, so you must also replace the
<sf1:CmsForm> tag with the standard <form> tag .
the Telerik team