We just upgraded a big Umbraco site (15K+ nodes) from 4.7 to 4.11.8
and all seems working good except all nodes need a host header (added
through Manage Host names) to make it work.. else am getting an Object
Reference not set to an instance error
What path did you follow doing the upgrade? Did you go straight to 4.11.8?
If so...did you remember to merge the web.config changes? And did you remember to add the new config files to the config folder and make sure that existing config files are merged properly as well?
I know that the hostname part has been re-writen in 4.11 and since 4.11.5 it should be working without issues...so perhaps this is related to the upgrade and how it has been done?
If you set hostname "mysite.com" on node "MySite.com" in 4.9 and before, Umbraco would still be able to map to the "Utilities" node and children, but starting with 4.10 it locks it search to node "MySite.com" and its children, and will not look anymore into other parts of the trees. This is to fix some nasty bugs with multi-sites setups where pages from one site would leak into another site.
So, if you want it to work, yes you have to set hostname "mysite.com/utilities" in the right place.
That being said, you should get a 404, not an exception. Could you post the complete stacktrace of the exception here?
this is a major headache for us too - it would be nice if the bug of leaking pages [i prefer to see it as a feature of being able to jump root tree nodes] was a setting in the Umbraco config, i.e. turn on off, as it has been, and would still be, very useful.
After upgrade to 4.11.8 - all the root nodes need a host name for it to work!
We just upgraded a big Umbraco site (15K+ nodes) from 4.7 to 4.11.8 and all seems working good except all nodes need a host header (added through Manage Host names) to make it work.. else am getting an Object Reference not set to an instance error
The site structure is
Content
-- MySite.com ( This has host header mysite.com )
-------- Page 1
-------- Page 2
-- Utilities
-------- Utility1
-------- Utility2
-------- Utility3
We could access http://MySite.com/Utility1, http://MySite.com/Utility2 ; etc without having a host header on 4.7 version.. but after the upgrade going to http://MySite.com/Utility1 throws Object ref error..
It works good if I add http://mysite.com/Utility1 as the host name through Manage Host names..
Anybody knows how to fix it as we have 100s of Utility nodes in there and the URLs are very important..
Thanks in advance for help.
Hi Anz
What path did you follow doing the upgrade? Did you go straight to 4.11.8?
If so...did you remember to merge the web.config changes? And did you remember to add the new config files to the config folder and make sure that existing config files are merged properly as well?
I know that the hostname part has been re-writen in 4.11 and since 4.11.5 it should be working without issues...so perhaps this is related to the upgrade and how it has been done?
Looking forward to hearing from you.
/Jan
Hi Jan,
Thank you for your reply.. Here is the update path we took
4.7.0
4.7.1.1
4.7.2
4.8.1
4.11.4
4.11.8
we upgraded to pretty much all major Umbraco updates.
Config files are merged correct but am double checking the config files with a fresh 4.11.8 copy right now..
Hey,
If you set hostname "mysite.com" on node "MySite.com" in 4.9 and before, Umbraco would still be able to map to the "Utilities" node and children, but starting with 4.10 it locks it search to node "MySite.com" and its children, and will not look anymore into other parts of the trees. This is to fix some nasty bugs with multi-sites setups where pages from one site would leak into another site.
So, if you want it to work, yes you have to set hostname "mysite.com/utilities" in the right place.
That being said, you should get a 404, not an exception. Could you post the complete stacktrace of the exception here?
Stephan
Hi Stepen,
Thank you for your message.. Yes it was a 404.. The object reference was due to wrong settings in UmbracoSettings.config file..
So we enjoyed using a bug and now need to find a solution :)
Planning to write a custom 404 Handler to handle this..
Thanks again for the help
Anz
Your welcome ;-)
But... setting domains on the "utilities" node cannot be a solution for you?
There is 100s of nodes and there will be more.. so making a 404handler seems to be the best solution for us.
Ah... 100s of nodes which are not under one common node on which you could set the domain, then?
If I set host name to "Utilities" node the URLs of the sub nodes will be
http://MySite.com/Utilities/Utility1
http://MySite.com/Utilities/Utility2
etc..
The URLs
http://MySite.com/Utility1
http://MySite.com/Utility2
etc are very important in our case..
ie - I will need to add host name entry to each of the sub nodes
Got it. Then yes, a 404 handler may be the way to go. Let me know if it works.
this is a major headache for us too - it would be nice if the bug of leaking pages [i prefer to see it as a feature of being able to jump root tree nodes] was a setting in the Umbraco config, i.e. turn on off, as it has been, and would still be, very useful.
fergus
This broke our site too. We are still recovering, but with Stephen's help we figured out a possible configuration fix.
Like Fergus said, a major headache.
is working on a reply...