In this article I have discussed some of the common issues which I have to faced to upgrade my sitefinity project from Sitefinity 4.1 to Sitefinity 8.2(Which is currently the Latest version).
when I was searching for how to upgrade my sitefinity project then I found the following link.
http://docs.sitefinity.com/upgrade
After going through that link I came to know that now I can directly upgrade my project from sitefinity 4.x to 8.x. So I started upgrading my project as mention in the link.
By following the up-gradation procedure ,I first stuck on the following message
"Message: PASSED: OpenAccessPageProvider: Upgrad AllowParameterValidation"
And I waited the entire day in hopes that it may proceed but it didn't. I thought that it is due to some error so to make sure that it is still in progress I try running an SQL profiler during the next attempt to upgrade just to see whether there are SQL queries being made when the screen is stuck on that message. While there are SQL queries being executed it would mean that the upgrade is still running.
If there have not been any queries executed in the past 5-10 minutes it would most likely mean that an error has occurred. Try refreshing the page in that case and see if the upgrade continues.
One free SQL profiler that can be used can be found here: https://expressprofiler.codeplex.com/.
After using this I came to know that this upgrade procedure will take some time depending upon the database size in my case my database size is approx. 5GB which end up taking around 12-14 hours to complete the up-gradation.
Now I have to check that all is well after the up-gradation process which end up giving some warnings.
when I check My frontend site its not running because of some code level error which I have resolved by using the following link that tells me about all the api changes from sitefinity 4.x to the latest version.
http://docs.sitefinity.com/api-changes-and-backward-compatibility
Here I would like to mention few major changes which should be kept in mind while fixing the code after up-gradation.
In Sitefinity 5.1, some of the modules were decoupled, i.e. moved from Telerik.Sitefinity.dll to a separate assembly. News, Blogs, Lists and Events are moved to Telerik.Sitefinity.ContentModules.dll and Ecommerce is moved to Teletik.Sitefinity.Ecommerce.dll.
That means any of your code chunks using these modules would need referencing(Telerik.Sitefinity.ContentModules.dll/Teletik.Sitefinity.Ecommerce.dll).
And In Sitefinity 7.3 there are some changes related to search can be seen at http://docs.sitefinity.com/api-changes-in-sitefinity-7-3
After making all the updates to my code for my frontend site now its time to move to sitefinity backend.
My frontend site working fine but when I go to backend it will again take some time for optimization purpose.
After that I logged in to sitefinity backend and started checking different modules if there is all is well. but when I go to news module and edit its item and it gives me following error.
Solution:
I have resolved this by adding the following line in my web.config file.
Now after that I have check some other modules all were looking fine but when I went to libraries modules there are some links that gives error.
I am unable to access following links and it gives me the error as shown in above image.
http://localhost:1007/Sitefinity/Content/Documents/LibraryDocuments
http://localhost:1007/Sitefinity/Content/Images/LibraryImages
http://localhost:1007/Sitefinity/Content/Videos/LibraryVideos
Although I am able to access all the libraries by their default page links as follows
http://localhost:1007/Sitefinity/Content/Documents
http://localhost:1007/Sitefinity/Content/Images
http://localhost:1007/Sitefinity/Content/Videos
To solve this I have searched a lot but could not find a solution to directly fix this one.
For this one we have to upgrade our project once again. :(
This issue was resolved through support ticket.
Solution:
We have to upgrade our project again and before upgrading the project we have to remove all "config:lazy" entries from our LibrariesConfig.config file, Which was actually causing some problem during the upgrade process.
Now my project is up and running :) hope this article will help others as well.
when I was searching for how to upgrade my sitefinity project then I found the following link.
http://docs.sitefinity.com/upgrade
After going through that link I came to know that now I can directly upgrade my project from sitefinity 4.x to 8.x. So I started upgrading my project as mention in the link.
By following the up-gradation procedure ,I first stuck on the following message
"Message: PASSED: OpenAccessPageProvider: Upgrad AllowParameterValidation"
And I waited the entire day in hopes that it may proceed but it didn't. I thought that it is due to some error so to make sure that it is still in progress I try running an SQL profiler during the next attempt to upgrade just to see whether there are SQL queries being made when the screen is stuck on that message. While there are SQL queries being executed it would mean that the upgrade is still running.
If there have not been any queries executed in the past 5-10 minutes it would most likely mean that an error has occurred. Try refreshing the page in that case and see if the upgrade continues.
One free SQL profiler that can be used can be found here: https://expressprofiler.codeplex.com/.
After using this I came to know that this upgrade procedure will take some time depending upon the database size in my case my database size is approx. 5GB which end up taking around 12-14 hours to complete the up-gradation.
Now I have to check that all is well after the up-gradation process which end up giving some warnings.
when I check My frontend site its not running because of some code level error which I have resolved by using the following link that tells me about all the api changes from sitefinity 4.x to the latest version.
http://docs.sitefinity.com/api-changes-and-backward-compatibility
Here I would like to mention few major changes which should be kept in mind while fixing the code after up-gradation.
In Sitefinity 5.1, some of the modules were decoupled, i.e. moved from Telerik.Sitefinity.dll to a separate assembly. News, Blogs, Lists and Events are moved to Telerik.Sitefinity.ContentModules.dll and Ecommerce is moved to Teletik.Sitefinity.Ecommerce.dll.
That means any of your code chunks using these modules would need referencing(Telerik.Sitefinity.ContentModules.dll/Teletik.Sitefinity.Ecommerce.dll).
And In Sitefinity 7.3 there are some changes related to search can be seen at http://docs.sitefinity.com/api-changes-in-sitefinity-7-3
After making all the updates to my code for my frontend site now its time to move to sitefinity backend.
My frontend site working fine but when I go to backend it will again take some time for optimization purpose.
After that I logged in to sitefinity backend and started checking different modules if there is all is well. but when I go to news module and edit its item and it gives me following error.
Solution:
I have resolved this by adding the following line in my web.config file.
<add key="Telerik.EnableEmbeddedSkins" value="false" />Now after that I have check some other modules all were looking fine but when I went to libraries modules there are some links that gives error.
I am unable to access following links and it gives me the error as shown in above image.
http://localhost:1007/Sitefinity/Content/Documents/LibraryDocuments
http://localhost:1007/Sitefinity/Content/Images/LibraryImages
http://localhost:1007/Sitefinity/Content/Videos/LibraryVideos
Although I am able to access all the libraries by their default page links as follows
http://localhost:1007/Sitefinity/Content/Documents
http://localhost:1007/Sitefinity/Content/Images
http://localhost:1007/Sitefinity/Content/Videos
To solve this I have searched a lot but could not find a solution to directly fix this one.
For this one we have to upgrade our project once again. :(
This issue was resolved through support ticket.
Solution:
We have to upgrade our project again and before upgrading the project we have to remove all "config:lazy" entries from our LibrariesConfig.config file, Which was actually causing some problem during the upgrade process.
Now my project is up and running :) hope this article will help others as well.
Upgrading from Sitefinity can significantly improve performance, security, and user experience. For a smooth transition, Hire Sitefinity Developers who specialize in migration, customization, and optimization. They ensure your website stays modern, scalable, and aligned with the latest digital trends.
ReplyDelete