Hi, Austin.
After deleting old unapproved comments via phpmyadmin
DELETE FROM wp_comments WHERE comment_approved = 0
any backup file can't be imported.
phpmyadmin reads:
Error
SQL query:
<p>INSERT INTO <code></code>wp_comments
VALUES ( 8314, 4916, 'jimmie', 'contact@xxxxx.com', '', '71.61.xx.xx', '2010-03-16 03:44:30', '2010-03-16 01:44:30', 'What do you mean by, My Answer: xxxxxxxxx.', 0, '1', 'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; AskTB5.2)', '', 0, 0 ) ;
MySQL said: Documentation
#1062 - Duplicate entry '8314' for key 'PRIMARY'
Deleting this particular comment won't help, it gives an error with another one.
Sure enough, the classic manual export from phpmyadmin and then importing a file works fine without errors so this issue is truly wp-db-backup plugin bug.
Tested in different environments on both wp-db-backup plugin 2.2.1 and 2.2.2 versions.
No, I'm not talking about changing the siteurl or home values.
The backup file generated by the backup plugin deletes all the contents of the tables when you restore it. So I don't understand why you're running a delete query first: it won't make any difference.
It sounds to me like you're using an edited version of the backup script with the "DROP TABLE" command removed.
Let me explain. Around March 9 old unapproved comments ( thousand or so) which were sitting there and eating dust got deleted via phpmyadmin just to trim down the database.
It was done just one time.
All backup files generated after March 9(I receive them daily) became unusable. All of them give that type of error, which I described earlier.
All backup files generated before March 9 are usable and don't give that error.
I can't duplicate this issue on the fresh install out-of-the-box. I added some unapproved comments, deleted them via phpmyadmin, ran your plugin and imported its backup file. No errors, everything works as usual.
I can't duplicate this issue after traditional manual export via phpmyadmin. I imported that backup file from the production site onto the test site. Then I deleted unapproved comments just I did before by running "DELETE FROM wp_comments WHERE comment_approved = 0"
Then, I ran your plugin and imported its backup file. Once again, everything is fine. No comments errors while importing.
Having said that it seems that it was a random glitch.
But the fact remains the same, all production site's backup files received after March 9 are unusable.
Is there any way to, say, reset the plugin on the go, please?
Then , I believe, wp-db-backup plugin files become usable again.
Hi, Austin.
After deleting old unapproved comments via phpmyadmin
DELETE FROM wp_comments WHERE comment_approved = 0any backup file can't be imported.
phpmyadmin reads:
VALUES ( 8314, 4916, 'jimmie', 'contact@xxxxx.com', '', '71.61.xx.xx', '2010-03-16 03:44:30', '2010-03-16 01:44:30', 'What do you mean by, My Answer: xxxxxxxxx.', 0, '1', 'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; AskTB5.2)', '', 0, 0 ) ;
MySQL said: Documentation
#1062 - Duplicate entry '8314' for key 'PRIMARY'
Deleting this particular comment won't help, it gives an error with another one.
Sure enough, the classic manual export from phpmyadmin and then importing a file works fine without errors so this issue is truly wp-db-backup plugin bug.
Tested in different environments on both wp-db-backup plugin 2.2.1 and 2.2.2 versions.
Any idea for workaround?
Thanks in advance.
You haven't modified the backup file at all? You're just uploading it directly?
Are you talking about modifying "siteURL" and "home" value?
Sure, I do it all the time while verifying on the test site that backups are usable.
It has worked for me for many years but not anymore.
No, I'm not talking about changing the siteurl or home values.
The backup file generated by the backup plugin deletes all the contents of the tables when you restore it. So I don't understand why you're running a delete query first: it won't make any difference.
It sounds to me like you're using an edited version of the backup script with the "DROP TABLE" command removed.
oh, no
"DROP TABLE" is there, I didn't touch it.
Let me explain. Around March 9 old unapproved comments ( thousand or so) which were sitting there and eating dust got deleted via phpmyadmin just to trim down the database.
It was done just one time.
All backup files generated after March 9(I receive them daily) became unusable. All of them give that type of error, which I described earlier.
All backup files generated before March 9 are usable and don't give that error.
Austin,
I got more info.
I can't duplicate this issue on the fresh install out-of-the-box. I added some unapproved comments, deleted them via phpmyadmin, ran your plugin and imported its backup file. No errors, everything works as usual.
I can't duplicate this issue after traditional manual export via phpmyadmin. I imported that backup file from the production site onto the test site. Then I deleted unapproved comments just I did before by running "DELETE FROM wp_comments WHERE comment_approved = 0"
Then, I ran your plugin and imported its backup file. Once again, everything is fine. No comments errors while importing.
Having said that it seems that it was a random glitch.
But the fact remains the same, all production site's backup files received after March 9 are unusable.
Is there any way to, say, reset the plugin on the go, please?
Then , I believe, wp-db-backup plugin files become usable again.
Austin,
it seems that you have problems understanding my case since the very beginning.
Just to make your recovery faster please let me ask in an easiest way I can :
How to flush plugin's cache?
Thanks
I need to flush your cache, and you need cash, right?
Send me your reasonable wage for this service.
RSS feed for this topic
Reply
You must log in to post.