Null reference exception when selecting nodes in content tree
Today I took my first look at 4.6.1 by means of upgrading a 4.6 site. All seemed great, I was editing content and all of a sudden hit the dreaded null reference exception when I select most(not all) nodes in the content tree. Here is the stack trace:
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +93
umbraco.controls.ContentControl.CreateChildControls() +769
System.Web.UI.Control.EnsureChildControls() +181
umbraco.controls.ContentControl.OnInit(EventArgs e) +122
System.Web.UI.Control.InitRecursive(Control namingContainer) +132
System.Web.UI.Control.AddedControl(Control control, Int32 index) +276
umbraco.cms.presentation.editContent.OnInit(EventArgs e) +1004
System.Web.UI.Control.InitRecursive(Control namingContainer) +132
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1953
I see there are a few posts on the forum similar to this relating to a bug that was fixed http://umbraco.codeplex.com/workitem/24871?ProjectName=umbraco? I had added two new properties to a document type but things were fine afterwards initially. What I don't get is that if it was a missing property for whatever reason why is affecting the display of nodes not using that doctype.
I have rebuilt the Examine Lucene indexes, restarted the app and the app pool with no success.
If anyone can shed any light on this or suggest possible fixes I would appreciate it, I'd prefer not to revert to a backup if at all possible.
I think you may have hit the nail on the head there Bo! Unfortunately without a fix I am still stuck with a broken site at the moment so going to need to try and do something. Will post any further information as/when I have it.
The bad news is that the issue was as identified by Bo above.
The good news is that there is a very simple solution to the problem, move your offending property(ies) off of the inherited tab onto a tab that is not inherited from a parent doctype.
This unfortunately does make the new inherited doctype tabs useless until it is fixed but at least it is now identified and will be fixed.
Niels has advised this will be addressed in the next release.
Null reference exception when selecting nodes in content tree
Today I took my first look at 4.6.1 by means of upgrading a 4.6 site. All seemed great, I was editing content and all of a sudden hit the dreaded null reference exception when I select most(not all) nodes in the content tree. Here is the stack trace:
Stack Trace:
I see there are a few posts on the forum similar to this relating to a bug that was fixed http://umbraco.codeplex.com/workitem/24871?ProjectName=umbraco ? I had added two new properties to a document type but things were fine afterwards initially. What I don't get is that if it was a missing property for whatever reason why is affecting the display of nodes not using that doctype.
I have rebuilt the Examine Lucene indexes, restarted the app and the app pool with no success.
If anyone can shed any light on this or suggest possible fixes I would appreciate it, I'd prefer not to revert to a backup if at all possible.
Hi Simon
I think it's related to this http://umbraco.codeplex.com/workitem/29889, but it hasn't been resolved yet
/Bo
I think you may have hit the nail on the head there Bo! Unfortunately without a fix I am still stuck with a broken site at the moment so going to need to try and do something. Will post any further information as/when I have it.
The bad news is that the issue was as identified by Bo above.
The good news is that there is a very simple solution to the problem, move your offending property(ies) off of the inherited tab onto a tab that is not inherited from a parent doctype.
This unfortunately does make the new inherited doctype tabs useless until it is fixed but at least it is now identified and will be fixed.
Niels has advised this will be addressed in the next release.
is working on a reply...