BacWPup 2.0 and WP 3.2 totally broken

I just tried the 2.01 plugin update and the backup executed perfectly and created a .ZIP file in the correct nested directory with the other prior backups.

Thank you!

I still get an error “Class ‘ZipArchive’ not found” and no valid zip file created with 2.0.1 on my site.

I was having similar issues. So, I deactivated the plugin and then reactivated it. Now, it appears to be functioning fine for me after the upgrade to 2.0.1.

WP 3.2 with 2.01 still fails for me. On one site I can’t create new jobs or change existing ones. Save Changes does nothing.
Running a job gets to the making a zip part, says it’s creating PCLZIP file, but I don’t have PCLZIP on this host, I hsve ZLIB. Using the wrong library?

Still another site does nothing when you run the job. No entries in the just nothing until you abort the job snd then you get user abort in the log.

Clicking the drop down from the sdmin bsr always takes me to job overview whatever is clicked.

This thing is way to fragile. Apparently very sensitive to the run environment because there are different results on different hosts.

Opps that should read WP 3.2 and 2.01

One more error noticed. If there are no active jobs then on Dashboard widget “Aktive Jobs” these errors show up:

Warning: Invalid argument supplied for foreach() in /<path>/wp-content/plugins/backwpup/backwpup-functions.php on line 391

Warning: array_multisort() [function.array-multisort]: Argument #3 is expected to be an array or a sort flag in /<path>/wp-content/plugins/backwpup/backwpup-functions.php on line 393

Warning: Invalid argument supplied for foreach() in /<path>/wp-content/plugins/backwpup/backwpup-functions.php on line 396
none

And please change the spelling of Aktive to Active.

I change the file format from zip to gzip and it works.
But the dropbox upload does not work ??
The backup file is 16 mb and i must cancle the job after more than 2000 seconds. The app is registered correctly at my dropbox account

wp 3.2, backwpup 2.0.1

before the update it worked very well for several weeks

I have been using BackWPup without issue for almost 12 months with a nightly backup emailed to me.

I now have the problems reported here – no backup received overnight – I aborted it after several hours running. My database is currently only 10.94 MB (which when zipped and emailed to me was less than 2 MB).

Tonight I installed backwpup 2.0.1, then deactivated it and reactivated it (yesterday I also deleted both my existing jobs and recreated then, after installing version 2.0, to clear the many errors others also had and reported at the start of this thread).

After installing version 2.0.1, I tried to do a “Run Now” backup. It goes to a black window with nothing in it and (like an earlier poster) the progress bars at the bottom immediately jump to 100% but the job never ends (I’m doubting whether it even starts).

I only have two jobs – one the scheduled nightly backup, the other is an inactive database table check which I run manually occasionally.

The database table check (which used to be pretty quick) also does not run – it goes to the black screen with the two 100% bars but nothing happens. I don’t think anyone else posting in this thread has mentioned trying a table check. Does this work for anyone else?

Like others, I love BackWPup and it has been so reliable for me over many months that I hope I can keep using it.

I got the same poblems on my host as Ridgididgi.
I’m using WP 3.2 with BackWPup 2.0.1

When I start the job nothing happens at all. I see the black log window the progress bars jump immediately to 100% and the job never ends.

The log is empty until I abort the the job.
But it’s only the message ‘aborted by user’.

I’ve tried several workarounds (deactivated/activated the plugin, recreated the job, tried different job-settings, zip/tar, only db-dump, only file backup) it’s everytime the same.

Hi there!
At my knowledge not everything of these issues seems plugin-related.
Just to double check the web server:
does the web server support:
– PHP 5.2.4 or higher?
– Safe-Mode off?
– cURL supported?
– ZIP support/creation enabled?
– PHP temp folder with regular path/settings?

As of my testing there seem to be some issues with different hosters not every hoster has the right settings for temp folders etc. or zip creation not allowed or restricted to a few bytes…

I believe we all do a lot of testing and try every possible setting. Just a few thoughts as a guide also for other users looking here…
-dave ??

Hey everyone, my latest site backup ran perfectly last night and created a .ZIP file without problems. This is the second consecutive scheduled run of backup without incident. For me, I think the latest update of 2.01 resolved the issue(s) causing the errors discussed in this forum.

I personally thank the plugin developer for his quick response and involvement in this resolution. I hope the others with problems have a quick resolve as well – I agree that the problems experienced may not all be related to the plugin, but rather the hosting settings or configuration. It would pay to check with your host tech support and work that angle too.

Many thanks!

I checked them as far as I know where to get the informations.

– PHP 5.2.17
– Safe-Mode disabled
– cURL-Support enabled
– ZIP: Libzip/ZLIB both enabled
– don’t know whre to get this info

Hi Dave

Thanks for your reply. Like Flibbo, I have checked what I can and these are the results:
– PHP 5.2.6-1+lenny9
– Safe-Mode OFF
– cURL-Support enabled
– ZIP: Libzip/ZLIB both enabled

Re “PHP temp folder with regular path/settings” – not sure what/how to check re this.

@daveshine

Just wanted to say thanks. Your advice above about Job Settings (3,5,30,300) worked for me. All the best!

I think it’s a bit unfair to keep blaming the host as the problem when most of us were upgrading from a working BackWPup installation. To blame the host does not answer why the the plugin could work before! Most have little control over the hosting anyway

You might do better to re-release the last 3.1.x compatible version (v1.7.8?) with the bare minimum of patches to get it working on 3.2 while you work out the kinks on 2.0x. At least we could do backups. I’m sure any number of use would be glad to let you analyze what’s happening on our machines that are having the current problems.

But don’t dodge the problem by blaiming the hosts.