Forums (Obsolete)

Old Forums

Technical support This forum is closed.

Version 1.x > Technical support > Delete Node Outside CultureInfo document

View modes:

Member

wtijsma - 1/10/2005 10:14:02 AM

Delete Node Outside CultureInfo document

Petr,

After your changes I still wasn't able to delete a node outside the tree.
I tried it, and it deleted ALL NODES in the entire CMS. Now I have to find out to restore it somehow. I don't know how to restore a transaction log, any ideas?

Useless to say that this may not happen EVER in a production environment, could you please look into this to prevent something like this happening again?

Regards, Wiebe


Member	wtijsma - 1/10/2005 11:31:03 AM Re: Delete Node Outside CultureInfo document Ok, the database is completely unrecoverable. I'm starting over.


Member	wtijsma - 1/10/2005 11:35:58 AM Re: Delete Node Outside CultureInfo document Is there a way to regenerate all database info from my current metadata? I don't want to enter all metadata manually again.


Guest	admin - 1/10/2005 12:43:02 PM Re: Delete Node Outside CultureInfo document Hi Wiebe, I'm very sorry for these problems. We are going to solve this issue in version 1.4 as I told you. I'm not sure why it deleted all data :( Do you have any backup? Even if you have no documents in the tree, the metadata should remain there, or not? Please let me know how we can help you.


Member	wtijsma - 1/10/2005 1:01:45 PM Re: Delete Node Outside CultureInfo document Hi Petr, I don't have a backup yet, I tried restoring it with the transaction log, but now my entire database is empty :-( It probably means I have to re-enter all the document templates as well, right?


Guest	admin - 1/10/2005 1:10:29 PM Re: Delete Node Outside CultureInfo document Do you have empty tables in the database or completely nothing? How many custom document templates do you have?


Member	wtijsma - 1/10/2005 1:13:17 PM Re: Delete Node Outside CultureInfo document empty tables, I haven't started the CMSDesk yet. I'm reinstalling a fresh 1.2, updating to 1.3, and try to use the SQL script dump to regenerate all the tables, views and procedures. Then I only have to enter the right data in your system tables, and can start entering data again.

Top