Hi weissonthego
It’s an odd one, an annoyance with MySQL and how it handles bad characters. The file in question ending _11.wmv contains some invalid characters.
I’ve reproduced the issue internally and we’re working on a fix. Will let you know when it’s done.
Regards,
Jason
Thanks for the response! I have tried many backups and found this to be one of the best.
I look forward to the fix.
Tnanks!
Hi weissonthego,
Can you try this version and see if it works any better?
https://wordpress.backup-technology.com/wponlinebackup-407.zip
Also, regarding the warning, it is not something that will have appeared in 2.2.9 and it generally should always have been there. Or, maybe you upgraded or installed another plugin around the same time as you upgraded to 2.2.9, and it created the table in question.
Thanks,
Jason
Hi Driskell,
This version failed also.
ERRORS:
1st Nov 2012 12.26.06 AM Error The backup failed: A database operation failed.
1st Nov 2012 12.26.06 AM Error A database operation failed.
Please try reinstalling the plugin – in most cases this will repair the database.
Please contact support if the issue persists, providing the complete event log for the activity. Diagnostic information follows:
Failed at: 1143(/home4/routersf/public_html/ARMEDPIRACYDEFENSE/wp-content/plugins/wponlinebackup-407/include/files.php)
WPDB error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘Implant Transfers-Implant Impression Transfers- 135-139.jpg’, ”, 1, 3412) ON DU’ at line 1. Last query: INSERT INTO wp_wponlinebackup_items (bin, parent_id, type, name, name_bin, path, activity_id, counter) VALUES (2, 3410, 1, ‘\’Implant Transfers-Implant Impression Transfers- 135-139.jpg’, ”Implant Transfers-Implant Impression Transfers- 135-139.jpg’, ”, 1, 3412) ON DUPLICATE KEY UPDATE name_bin = IF(activity_id = 1, name_bin, ”Implant Transfers-Implant Impression Transfers- 135-139.jpg’), path = IF(activity_id = 1, path, ”), counter = IF(activity_id = 1, counter, 3412), activity_id = 1
Hi weissonthego,
Apologies for that – it popped up during release testing and has been fixed.
The full release is happening today so you should be able to update and everything work.
Thanks,
Jason
Driskel,
I downloaded 2.2.10 and everything worked. I am curious, what the problem was.
Thank you for your help.
Hi weissonthego,
The original problem was you had files in your filesystem with strange special characters. They were stored using an unknown “code page” and MySQL was converting them to question marks meaning what ended up in the database was different to what we asked it to store. We do the conversion ourselves now so what ends up in the database is what we expect.
It’s brought up a lot of compatibility questions though which we’re working through, such as case sensitive filesystem support. But for now at least everything works and we now see warnings when we have problems where before it might have silently skipped things.
Thanks for all the help getting to the bottom of it!
Jason
No, thank you for your thorough investigation. I appreciate your responding also.
