DocType properties disappearing from umbraco.config ?
I have a document type with about 12 properties and at some point all of these properties suddenly disappear from the umbraco.config. This is umbraco 4.0.3, but I had the same behavior in 4.0.2.
Once I right click on "Content" and select "Republish entire site", the file gets regenerated and the properties are back. Also, when I hit "Publish" on the corrupted node, it fixes the problem.
This seems to happen in one of three scenario's (or a combination of them), I haven't been able to pinpoint the exact point of failure:
Emptying the recycle bin
Uploading photo's in the media section (which causes the automatic creation of a document in content, but these new documents are NOT affected by this problem, it's a higher ancestor of this new document that gets corrupted)
Publishing a node and it's subnodes (again, not the corrupted node, but lower descendants of the corrupted node)
There are no errors in umbracoLog, nor Windows event log. I haven't been able to reproduce this with any consistency.
I checked and have reset the permissions. However, this was an issue on 3 seperate environments, so I doubt that permissions could be the cause. On my dev environment I always give full control to the network user, it's just easier that way. :)
Just an update, i've tried running through the three scenario's, emulating a "real-world" scenario and I haven't been able to reproduce the problem at all.
I'm now thinking of a fourth scenario that could come in to play is that this often happens when I create a copy of a tree of documents (not the corrupted one).
I'll keep monitoring and see if I can find a more accurate moment on which this problem emerges, it's very hard though, without seeing any errors in the logs.
DocType properties disappearing from umbraco.config ?
I have a document type with about 12 properties and at some point all of these properties suddenly disappear from the umbraco.config. This is umbraco 4.0.3, but I had the same behavior in 4.0.2.
Once I right click on "Content" and select "Republish entire site", the file gets regenerated and the properties are back. Also, when I hit "Publish" on the corrupted node, it fixes the problem.
This seems to happen in one of three scenario's (or a combination of them), I haven't been able to pinpoint the exact point of failure:
You know the drill... check file permissions. Double-check them. Triple-check them. Open up full control for a while and see if it makes a difference.
The stranger the behavior, the more likely you've got a file permission issue (might even be on one file).
cheers,
doug.
Thanks Doug!
I checked and have reset the permissions. However, this was an issue on 3 seperate environments, so I doubt that permissions could be the cause.
On my dev environment I always give full control to the network user, it's just easier that way. :)
Just an update, i've tried running through the three scenario's, emulating a "real-world" scenario and I haven't been able to reproduce the problem at all.
I'm now thinking of a fourth scenario that could come in to play is that this often happens when I create a copy of a tree of documents (not the corrupted one).
I'll keep monitoring and see if I can find a more accurate moment on which this problem emerges, it's very hard though, without seeing any errors in the logs.
is working on a reply...