Can't email DB with BackWPup 2.0.0 in WP 3.2

Update: Version 2.0.1 BackWPup still has the exact same problem.

Hi LMP

See this existing thread which has a lot of advice on it
https://www.ads-software.com/support/topic/bacwpup-20-and-wp-32-totally-broken?

Mine still isn;t working, though – I have the same problem that you describe.

maling works on my testing

OK, I logged in to my admin control panel and noted the SQL versions. Maybe these will help you find out where the bug is:

SQL Server version: 5.2.6-MariaDB-mariadb101
MySQL client version: 5.0.77
PHP extension: mysql

I just downloaded and tested version 2.0.2 of BackWPup. No change. I still get a black rectangle, and no email is sent.

My PHP version is 5.2.13 could this cause my problems with BackWPup?

can u test the develpopment version ?

In https://www.ads-software.com/extend/plugins/backwpup/ version 2.0.2 is the newest listed.

I can’t see any external links to another web site (from where I would presumably download a beta version).

So, from where do I download the develpopment version?

Just tested version 2.0.3 BackWPup. Still the same problem… ??

Just tested version 2.0.3 BackWPup. Still the same problem… ??

Ditto ?? – see my longer post here

Well, I just found something interesting. I was about to give up on BackWPup version 2.x and downgrade to version 1.7.x, but I decided to give version 2 one last try…

First I deactivated BackWPup 2.0.3 from the plugins page.

Then I logged in to my web host’s control panel, and accessed the SQL database though PHPmyAdmin.

I then proceeded to delete all BackWPup entries (I found three) from the WP_Options table.

Back in the WordPress control panel, I activated BackWPup 2.0.3. It ran with the default settings, since I had deleted the old tables.

I then tried to create a job to email my database, and it worked!

One -minor- bug: I can’t delete the default “New” job in the jobs list. I also tried renaming it, and it just creates another job under the new name, while keeping the “New” job in the list.

So in conclusion, the solution seems to be to delete all old BackWPup preferences and settings from your SQL database manually before running the new version.

I think that this should be handled by BackWPup itself in future versions. It can’t be too difficult to include an “Erase all BackWPup settings from the SQL database” button in the BackWPup settings page.

P.S. I forgot to mention that I use W3 Total Cache. I did not have it installed when I tested version 2.0.0 and 2.0.1 of BackWPup.

I installed W3 Total Cache just recently, and it seems to work fine with BackWPup 2.0.3 (now that I deleted the old preferences – see my previous post).