I recently upgraded our dev server from 4.5.2 straight to 4.7. There are a couple steps left out of the install instructions, but otherwise all went well.
What steps are missing? It would be great if you would share so Eran does not need to spend time figuring this out for himself and so that the instructions could be updated.
Two items I recall... one is related to the created and installed packages. The upgrade instructions had me copy blank XML files over the top of my existing files. Luckily I had backups I could bring back.
Also, there were additional files I needed to delete otherwise XSLT failed with errors.
You're welcome. Could you please mark Connies second answer as the solution if this was what did the trick? Then others can easily go to the solution if they come across this :-)
4.0.3 to 4.1 is not a firect upgrade, there are differences in the XML schema (so you need to change the UseLegacyXML setting or adjust your XSLT).
Also 4.7 uses a different .NET version (4)
I think it's recommended to upgrade to 4.5.2 first and then to 4.7, however expect some pitfalls along the way, especially if you use alot of 3rd Party packages as some of these are not compatible.
Obviously do NOT try this on a live website, try it locally and see how it goes.
upgrade to 4.7 from 4.5.2
hey, i want to update from 4.5.2 to 4.7?
is it the right way to upgrade straight to 4.7 ? or i need to upgrade first to 4.6.1 and then to 4.7 ?
Hi Eran
As far as I know it should be possible to go from 4.5 to 4.7 skipping the 4.6.2 step.
For general upgrade instructions you can find more information here: http://our.umbraco.org/wiki/install-and-setup/upgrading-an-umbraco-installation
And there are some 4.7 specific notes here: http://umbraco.codeplex.com/releases/view/62573 (The section below the fold that says "Important before upgrading").
Maybe it's a good idea to do a dummy upgrade by creating a clean install of 4.5.2 and try to upgrade that to 4.7?
Hope this helps
/Jan
I recently upgraded our dev server from 4.5.2 straight to 4.7. There are a couple steps left out of the install instructions, but otherwise all went well.
Hi Connie
What steps are missing? It would be great if you would share so Eran does not need to spend time figuring this out for himself and so that the instructions could be updated.
Thanks.
/Jan
Two items I recall... one is related to the created and installed packages. The upgrade instructions had me copy blank XML files over the top of my existing files. Luckily I had backups I could bring back.
Also, there were additional files I needed to delete otherwise XSLT failed with errors.
Delete:
IronMath.dll
IronPython.dll
IronPython.Modules.dll
IronRuby.dll
IronRuby.Libraries.dll
IronRuby.Libraries.Yaml.dll
Microsoft.Dynamic.dll
Microsoft.Scripting.Debugging.dll
Microsoft.Scripting.dll
RazorEngine.Core.dll
RazorEngine.Templates.dll
umbraco.MacroEngines.Legacy.dll
VistaDB.NET20.dll
VistaDB for Umbraco.dll
Hi Connie
Thanks for sharing this. Others might benefit from this if they come accross this issue.
/Jan
thanks for all the help everybody :)
Hi Eran
You're welcome. Could you please mark Connies second answer as the solution if this was what did the trick? Then others can easily go to the solution if they come across this :-)
/Jan
Hi Connie,
I deleted the above files, but still getting errors for the XSLT files? Anything you missed out?
~Sharmin
I could solve it
Steps:
~Sharmin
Can I upgrade directly from 4.0.3 to 4.7
Thanks
Krishna
Hey Krishna,
Welcome to the forum.
4.0.3 to 4.1 is not a firect upgrade, there are differences in the XML schema (so you need to change the UseLegacyXML setting or adjust your XSLT).
Also 4.7 uses a different .NET version (4)
I think it's recommended to upgrade to 4.5.2 first and then to 4.7, however expect some pitfalls along the way, especially if you use alot of 3rd Party packages as some of these are not compatible.
Obviously do NOT try this on a live website, try it locally and see how it goes.
Rich
Locally I am doing upgradation from 4.0.4.2 to 4.5. I am getting problem at step 3/5. Object reference not set to an instance of an object.
Thanks
krishna
Guys,
How long did it take to comple the upgrade process?
Thank you.
Takki
Hi,
I upgraded from 4.5.2 to 4.7 and getting the following error whenever i tried to run the page.
Wrong node document type. Node (id: 1438, name: 'Services and Solutions', document type: 'ServicesandSolutions'). Expected document type: 'ServicesandSolutions'.
I am getting same Wrong node document type error for all pages with other document types also.
Thanks
Anshul
is working on a reply...