bassu

Resolved by upgrading to PHP 5.2.10. Test task executed successfully with latest backwpup.1.2.1.
WOW. It was such a long nightmare, lol.

Three weeks back when I did my tests on different versions of backwpup, I remember I did test backwpup 1.0.3 on a different machine with PHP 5.2.13 but guess what I wasn’t successful at that time.

I’m now marking this thread as resolved and hopefully it’ll help many other WordPress bloggers who all faced the same issue.

Thanks Daniel.

Tried checking backwpup.1.2.1 but still the same.

# php -v
PHP 5.1.6 (cli) (built: Apr 7 2009 08:00:04)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

# php -i | grep -c memory-limit
1

Yes, 1.0.7 doesn’t work including the latest 1.0.10 as I just checked.
Unfortunately, 1.0.6 still shows the same blank page. I think, in this case I shall stick to either older version 0.8.1 or use bash to simply have plain backups.

Thanks.

Just did. Removed 1.0.7 completely and installed 1.0.5 and well, well, here’s the error:

Parse error: syntax error, unexpected ‘}’, expecting ‘,’ or ‘;’ in /path/to/vhost/wp-content/plugins/backwpup/app/options-runnow-iframe.php on line 30

I guess you added some debugging clauses ?? Right

I meant in the browser. The actual iframe php file does have code but for some reason it’s not executing and showing a blank page instead :*(

The iframe shows up a blank page and there’s nothing in its source code unfortunately

Sorry for the confusion. I pasted rest of the URL. It does have domain.tld.

Do let know if there’s anything else you want to have checked?

I also tried enabling full PHP error debugging but its the same, lol.

memory_limit = 200M
error_reporting = E_ALL
display_errors = On
short_open_tag = On

Yep, it exists. Path of iframe is correct.

/plugins/backwpup/app/options-runnow-iframe.php?ABSPATH=%2Fvar%2Fwww%2Fdomain.com%2F&jobid=1&_wpnonce=26a9b8270d

translates to /var/www/domain.com/

Some of my tests:

* WordPress 2.6 with Backwpup 0.8.0 works pretty well.
* WordPress 3.0 with Backwpup 0.8.0 works too.
* WordPress 3.0 with Backwpup 1.0.3 fails with blank page.

Thanks Daniel. Actually the problem occurs even I’ve cache plugin removed or deactivated. I just downloaded newer 1.0.3 but it still shows off the blank page.

Ironically, its scheduler is also not working for me. Only creates null log files and not any back archives.

Is it possible for you to add some sort of error handling or debugging features to backwpup? Or I guess, there should a compatibility checking tool that should check server or PHP runtime environment to find out if its supported for backwp or not!