On two occasions the last month, the whole page tree in Umbraco has become corrupt. All pages in the page tree get a “#” as link and you cannot visit any page on the site. The only solution we’ve found is to republish the whole page tree and this takes several hours!
It seems like the problem occurs after creation of new document types. In particular, after a new document type is created and you create a page of the new document type in the page tree (to test it) and thereafter removes it, the problem seem to occur.
We have seen this issue both in our development environment, and what is more serious, in our production environment.
I know that bug way too well :'( - I'm not sure why it happens all I can remember is that it's a weird and annoying bug which happens in that particular version.
It's something about the XML cache being corrupted for some reason.
However upgrading might be hard depending on how many 3rd party packages you're using on the site and how much custom API integration etc. that has been made. If you're using uComponents for instance then you need to pay attention to the some specific details about how to upgrade it properly.
Thanks a lot for the answer Jan! It is good to know that it is a known issue.
Moving forward, we will at least make sure that no editors are editing anything while deploying/changing document types, just to minimize the risk of the issue to happen. And upgrading is of course worth thinking about :-)
Corrupt page tree
Our client is using Umbraco 4.7.2.
On two occasions the last month, the whole page tree in Umbraco has become corrupt. All pages in the page tree get a “
#” as link and you cannot visit any page on the site. The only solution we’ve found is to republish the whole page tree and this takes several hours!It seems like the problem occurs after creation of new document types. In particular, after a new document type is created and you create a page of the new document type in the page tree (to test it) and thereafter removes it, the problem seem to occur.
We have seen this issue both in our development environment, and what is more serious, in our production environment.
The site contains approx. 3000 pages.
Anyone got a clue on what is going on?
Hi Jessica
I know that bug way too well :'( - I'm not sure why it happens all I can remember is that it's a weird and annoying bug which happens in that particular version.
It's something about the XML cache being corrupted for some reason.
You can read more about it in this post from 2012 https://our.umbraco.org/forum/using/ui-questions/35164-All-nodes-reverting-to-'hash'-url-472-49 - Judging from this issue http://issues.umbraco.org/issue/U4-1002 it should perhaps be possible to avoid it by upgrading to the last version of Umbraco 4, which would be 4.11.10 - It can be fetched from Lee Kellehers "secret" stash here http://code.leekelleher.com/umbraco/archive/
However upgrading might be hard depending on how many 3rd party packages you're using on the site and how much custom API integration etc. that has been made. If you're using uComponents for instance then you need to pay attention to the some specific details about how to upgrade it properly.
I hope this helps a bit.
/Jan
Thanks a lot for the answer Jan! It is good to know that it is a known issue.
Moving forward, we will at least make sure that no editors are editing anything while deploying/changing document types, just to minimize the risk of the issue to happen. And upgrading is of course worth thinking about :-)
is working on a reply...