but unfortunately I get some errors in the backend. For instance when I try to add a new page it says in the popup:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18045
Then when I try to publish a node using the right click menu, the popup shows the publish dialog + the waiting bar already, so publishing seems broken.
What steps did you take? Did you go directly or did you do it incrementally?
If you did do it the incremental way did you do a test after each step to see what broke during the process? Did you use a versioning system like git or mercurial to make it easy to rollback between upgrades?
Yes I followed the steps from that link. I only did 1 /install step. Didn't copy the 4 dir's for every release in between.
Also did a winmerge on all the config files and followed the version specific upgrade instructions (like removing specific dll files).
I do have some packages installed: Cultiv search engine sitemap, relation types, goyaweb multi-language tools, famfamfam, doc2form, desktop media uploader, cmsimport, ucomponents, contour, nforum. How would they influence the base functionality of the CMS?
Also I just upgraded to 6.1.3 and now it seems the publishing error went away. The only one still left now is when creating a new page (see error in first post)
Seems to be some problem with trying to get a template that is not being found. Can you see if it helps to save all your document types one by one?
And/or saving the templates too?
The listed packages I think are all supported, maybe not doc2form though, not sure I've never tried and as I'm not sure how that works I don't know if it could intefere.
Upgrade problems
I just finished upgrading a Umbraco 4.7.2 site all the way up to Umbraco 6.1.2 using the instructions from
http://our.umbraco.org/documentation/installation/upgrading/version-specific
but unfortunately I get some errors in the backend. For instance when I try to add a new page it says in the popup:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18045
Then when I try to publish a node using the right click menu, the popup shows the publish dialog + the waiting bar already, so publishing seems broken.
Tips on how to debug this, are welcome!
Hi Yannick
What steps did you take? Did you go directly or did you do it incrementally?
If you did do it the incremental way did you do a test after each step to see what broke during the process? Did you use a versioning system like git or mercurial to make it easy to rollback between upgrades?
Did you follow the upgrade instructions in http://our.umbraco.org/documentation/Installation/Upgrading/ ? Did you merge the config files and did you merge the web.config changes as well?
Are you using some packages that might not be supported/work with this new version?
Looking forward to hearing from you.
/Jan
Yes I followed the steps from that link. I only did 1 /install step. Didn't copy the 4 dir's for every release in between.
Also did a winmerge on all the config files and followed the version specific upgrade instructions (like removing specific dll files).
I do have some packages installed: Cultiv search engine sitemap, relation types, goyaweb multi-language tools, famfamfam, doc2form, desktop media uploader, cmsimport, ucomponents, contour, nforum.
How would they influence the base functionality of the CMS?
Also I just upgraded to 6.1.3 and now it seems the publishing error went away. The only one still left now is when creating a new page (see error in first post)
Seems to be some problem with trying to get a template that is not being found. Can you see if it helps to save all your document types one by one?
And/or saving the templates too?
The listed packages I think are all supported, maybe not doc2form though, not sure I've never tried and as I'm not sure how that works I don't know if it could intefere.
thanks Seb! That fixed the error. Greetings from rainy Scheveningen :)
is working on a reply...