Broke my DB while dribbling with document types - Umbraco 6.0.0
I've been setting up a site on Umbraco 6.0.0 today
It's been really rocking and going along nicely, until I somehow created a datatype and referenced it in my content, but the created node just disappeared from my content tree! And this was when I had already created a subnode to this node.
I tried to create it again with no luck.. A few times actually..
Since then, my nodes keep being unpublished in the content tree, and the site is very.. Unstable..
I tried to delete the document type, but that won't work since it's being used I suppose (by the not showing nodes)
Now I can't really do anything with my site, since I can't remove the nodes from my tree (not even the showing parent)
What do I do to fix it?
One of the content types i want to delete.
The result of deleting it..
The weird unpublished content tree
Trying to remove it (the showing node with unseen children)
That unfortunately seems like a nasty bug - could you please submit it as a ticket in the issue tracker? issues.umbraco.org/issues/U4 - This way it will get the attention of the core developers.
But do you know how I can clean my Db to get it working again, I have to remove all reference to these document types, which includes all nodes using them, which seem to include all xmlpreview things, and on and on.. Where do I start deleting? Anyone?
I looked around down the database PK constraints, and got all the way to cmspreviewxml having a dependancy on the contentid from the cmscontent. But I can't remove those since it's somehow a Read Only table.. What do I do?
EDIT:
The table is read only in MySql Workbench because it has no primary key or otherwise unique non nullable columns defined..
Bah.. I managed to get all references to the broken data types away.. NOTE TO EVERYONE, you can write delete queries to MySQL even though you cannot edit the rows using the MySQL Workbench GUI.
Now.. The question is.. Do I dare give it another try?
Broke my DB while dribbling with document types - Umbraco 6.0.0
I've been setting up a site on Umbraco 6.0.0 today
It's been really rocking and going along nicely, until I somehow created a datatype and referenced it in my content, but the created node just disappeared from my content tree! And this was when I had already created a subnode to this node.
I tried to create it again with no luck.. A few times actually..
Since then, my nodes keep being unpublished in the content tree, and the site is very.. Unstable..
I tried to delete the document type, but that won't work since it's being used I suppose (by the not showing nodes)
Now I can't really do anything with my site, since I can't remove the nodes from my tree (not even the showing parent)
What do I do to fix it?
One of the content types i want to delete.
The result of deleting it..
The weird unpublished content tree
Trying to remove it (the showing node with unseen children)
Doesn't work
Hi Niclas
That unfortunately seems like a nasty bug - could you please submit it as a ticket in the issue tracker? issues.umbraco.org/issues/U4 - This way it will get the attention of the core developers.
/Jan
Hi Jan, thanks for your reply!
Submitted an issue here: http://issues.umbraco.org/issue/U4-1745
But do you know how I can clean my Db to get it working again, I have to remove all reference to these document types, which includes all nodes using them, which seem to include all xmlpreview things, and on and on.. Where do I start deleting? Anyone?
Thanks!
I looked around down the database PK constraints, and got all the way to cmspreviewxml having a dependancy on the contentid from the cmscontent. But I can't remove those since it's somehow a Read Only table.. What do I do?
EDIT:
The table is read only in MySql Workbench because it has no primary key or otherwise unique non nullable columns defined..
Bah.. I managed to get all references to the broken data types away.. NOTE TO EVERYONE, you can write delete queries to MySQL even though you cannot edit the rows using the MySQL Workbench GUI.
Now.. The question is.. Do I dare give it another try?
is working on a reply...