Database messed up after failed restore
Permalink
Hello there,
I encountered a strange error when trying to extend a site (v. 5.6.2.1):
It is a multilingual, e-commerce using site.
So here's what happened:
1. I set up a new language page tree
When copying the pagetree, using the multilingal add-on, it gave me an error (supposingly because many e-com products were residing under one of the pages to copy)
2. After messing this up, I just tried to revert to the most recent backup to "start from scratch" from before adding the page tree. When clicking "restore", it gave me the infamous "stack frame error" from which I read in the forums.
What happened then seems a bit strange - the restored database seemed to be there somehow, some pages in the page tree were there, some were there that shouldnt.
All the cache-deleting and table-refreshing did not help.
When adding a new page now, It shows the MySQL 1062 (Duplicate Entry) error, when adding a block or stack, same thing.
But after I return to the dashboard after the error msg, the page is actually there but not where I added it, but under the last page I added... So when "Page 8" is the most recent page, and I want to add a page under "Home", it shows the error and afterwards, the page pops up as a child of "Page 8". I can move it over to any other location.
Now I looked at the database and found, that the cIDs are strange. When for example in "Pages" Table, the cIDs are from 0 to 791 in a rather regular manner and most of these cID actually exist, so when I navigate to one of the number as Page ID, it shows something.
But then, the cID start from 1132 up to 1390 without one of them being a actual page, all 404 when going there.
Same for Stacks.
It seems to me like the "going back" with the database restore did not actually work and now all the "old" cIDs from all the versions of everything are still there and giving me duplicate entry errors no matter what I do.
Anybody encountered something like that? I still do not understand how this works preciseley. Do I need to manually delete all the not-working database entries? What strange sorcery is going on there?
Thanks for any help!
I encountered a strange error when trying to extend a site (v. 5.6.2.1):
It is a multilingual, e-commerce using site.
So here's what happened:
1. I set up a new language page tree
When copying the pagetree, using the multilingal add-on, it gave me an error (supposingly because many e-com products were residing under one of the pages to copy)
2. After messing this up, I just tried to revert to the most recent backup to "start from scratch" from before adding the page tree. When clicking "restore", it gave me the infamous "stack frame error" from which I read in the forums.
What happened then seems a bit strange - the restored database seemed to be there somehow, some pages in the page tree were there, some were there that shouldnt.
All the cache-deleting and table-refreshing did not help.
When adding a new page now, It shows the MySQL 1062 (Duplicate Entry) error, when adding a block or stack, same thing.
But after I return to the dashboard after the error msg, the page is actually there but not where I added it, but under the last page I added... So when "Page 8" is the most recent page, and I want to add a page under "Home", it shows the error and afterwards, the page pops up as a child of "Page 8". I can move it over to any other location.
Now I looked at the database and found, that the cIDs are strange. When for example in "Pages" Table, the cIDs are from 0 to 791 in a rather regular manner and most of these cID actually exist, so when I navigate to one of the number as Page ID, it shows something.
But then, the cID start from 1132 up to 1390 without one of them being a actual page, all 404 when going there.
Same for Stacks.
It seems to me like the "going back" with the database restore did not actually work and now all the "old" cIDs from all the versions of everything are still there and giving me duplicate entry errors no matter what I do.
Anybody encountered something like that? I still do not understand how this works preciseley. Do I need to manually delete all the not-working database entries? What strange sorcery is going on there?
Thanks for any help!
And I found another issue:
To prevent the same problem, I moved the page that contains all the e-com products out of the language tree. But it was copied and caused problems nonetheless when copying the language trees! How is that going?
Thanks!