A strange bug has arrived in our customers umbraco site.
After they publish something the umbraco.config contains two Homepage-nodes. One of them contains all the relevant data, while the other is allmost empty. This break some of their XSLT-files.
Why does this happen, and what can we do to prevent it for happening again?
I don't suppose you're running some custom code to overrule the save event somehow?
If it's a clean 6.0.0 I think you should consider upgrading to 6.0.3 to see if that fixes the issue - Unfortunately 6.0 contains some weird bugs, which have been fixed in the patch releases.
I still recommend that you upgrade - from the above it seems you have not tried that approach yet. Unfortunately some weird bugs happened in v6.0.0 - v6.0.4 is out, try and go for it :)
Errror in umbraco.config after publishing events. Umbraco 6.0.0
A strange bug has arrived in our customers umbraco site.
After they publish something the umbraco.config contains two Homepage-nodes. One of them contains all the relevant data, while the other is allmost empty. This break some of their XSLT-files.
Why does this happen, and what can we do to prevent it for happening again?
Hi Magnus
I don't suppose you're running some custom code to overrule the save event somehow?
If it's a clean 6.0.0 I think you should consider upgrading to 6.0.3 to see if that fixes the issue - Unfortunately 6.0 contains some weird bugs, which have been fixed in the patch releases.
Hope this helps.
/Jan
No custom code that I know of.
We will try to upgrade to 6.0.3 and hope for the best.
/Magnus
I have digged deeper.
This block turns up in the TraceLog every other minute
2013-04-25 10:04:20,161 [6] ERROR umbraco.presentation.publishingService - [Thread 14] Error publishing node 1341
System.ArgumentNullException: Value cannot be null.
Parameter name: attribute
at System.Xml.Linq.XAttribute.op_Explicit(XAttribute attribute)
at UmbracoExamine.UmbracoContentIndexer.ReIndexNode(XElement node, String type)
at Examine.ExamineManager._ReIndexNode(XElement node, String type, IEnumerable`1 providers)
at umbraco.content.DocumentCacheEventHandler.Invoke(Document sender, DocumentCacheEventArgs e)
at umbraco.content.UpdateDocumentCache(Document d)
at umbraco.library.UpdateDocumentCache(Document doc)
at umbraco.presentation.publishingService.CheckPublishing(Object sender)
I have tried to delete the node, and remove it from the recycle bin, but it is still there. And if I look in the database:
SELECT count(*) FROM [sdsi].[dbo].[cmsDocument] WHERE nodeid = 1341
the result is aroung 46000, for a site that is three weeks old.
Hi Magnus
I still recommend that you upgrade - from the above it seems you have not tried that approach yet. Unfortunately some weird bugs happened in v6.0.0 - v6.0.4 is out, try and go for it :)
Cheers,
Jan
Hi Jan,
We have upgraded to 6.0.3 and cleaned the database. Thanks for the help.
Magnus
is working on a reply...