ok, using firefox 2.0.0.6 winxp sp2 wp 2.2.3 backwp 0.26 when I try to manually start a backup, it keeps loading.
firebug gives me this error:
x_bkpwp_ajax_create is not defined
do_create()admin.php (line 297)
onclick(click clientX=0, clientY=0)admin.php (line 1)
[Break on this error] x_bkpwp_ajax_create(preset,'');
there is no error log and inside the backup folder there is nothign to be found.
ovidou, how about "recalculating disk space" in AdvancedMode? Is there an ajax problem as well?
recalculating disk space gives:
x_bkpwp_ajax_calculater is not defined
calculate()admin.php (line 306)
onclick(click clientX=0, clientY=0)admin.php (line 1)
[Break on this error] x_bkpwp_ajax_calculater(preset,'');
and keeps loading. btw. I am using wp 2.2.2 not 2.2.3
maybe my question is too stupid, but: have you got javascript enabled? Somehow Sajax.php fails to load the required javascript components into the BackUpWordPress Interface.
Could you please post the information that is provided by this plugin: http://wordpress.designpraxis.at/plugins/phpinfo/ here? Maybe it tells us something about the source of you problem.
ok, I found a little problem: your plugin breaks the weathericon plugin. after deactivating this backupwp plugin the weathericon was again running fine.
could you look that up too?
I also posted that as a comment on the backupwp plugins page.
here is the server info:
PHP information for http://www.rondul.eu
max_execution_time: 60
max_input_time: 120
file_uploads: 1
upload_max_filesize: 32M
post_max_size: 32M
register_globals:
safe_mode: 0
allow_url_fopen: 1
Other information:
WordPress Version: 2.2.3
WordPress Blog URI: http://www.rondul.eu
WordPress Installation URI: http://www.rondul.eu
WordPress Permalink Structure: /%category%/%postname%/
WordPress wp-content directory is writable
WordPress does not use Gzip Compression
WP-Cache is running on this installation of WordPress
GD library is installed
PHP Version: 4.4.4-8+etch4
MySQL Version: 5.0.32-Debian_7etch1-log
Browser used: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Have you got eAccellerator or another opcode cache running on you webserver?
If so try to put this in your .htaccess file
# disable caching with eaccelerator
php_flag eaccelerator.enable 0
The Problem is, that such caching systems also cache the declared classes, thus resultin in an "Cannot redeclare class" error for PEAR, which stops BackUpWordPress from running...
I do have eaccelerator enabled. I disabled it cleaned, cleared and purged the cache, started a backup, got this error in firebug:
x_bkpwp_ajax_create is not defined
do_create()admin.php (line 314)
onclick(click clientX=0, clientY=0)admin.php (line 1)
[Break on this error] x_bkpwp_ajax_create(preset,'');
BUT the backup still hangs :-(
and yould tell me which files to exclude frm eaccelerator I can add them to the exclude list.
ovidou, the most important file to exclude from eaccelerator is PEAR.php. You'll find it the BackUpWordPress plugin's root folder. BUT: You also should exclude any other PEAR.php bundled with other plugins like WeatherIcon.
And still, besides that, you might have a multiple problem. Sajax needs to load, which seems not to be the case with your installation.
I really would want to have an exact copy of your WordPress setup on one of my machines...
I know it is a bit of an effort, but: could you set up a second copy of WordPress on the same Server as your existing one resides, leave everything as is , just install BackUpWordPress and run it?
If this fails, there is definitely some serverside configuration to consider...
as I am on my own server it is not really that much of an effort. I already have severall wp installs on the same server, should I just install backupwp into one of them or do you want a clean wp install?
Well, I think first we should check if there is a server side issue, so a clean wp 2.2.3 install with BackUpWordPress as the only Plugin would be best. Next thing to do would be to check BackUpWordPress with your other wp installations.
seems the guys from the weathericon found the solution although I have not had the time to test it, I'll do it tomorrow.
Yepp. See:
http://wordpress.designpraxis.at/plugins/backupwordpress/#comment-707
Garett, the lead developer of WeatherIcon, found the problem was in the use of PEAR.
“If WeatherIcon activates first, there is no issue. If BackupWordpress activates first, WeatherIcon won’t activate.”He has fixed the problem in 2.99.125.
He is running WeatherIcon 2.99.125 and BackupWP 0.2.7 on his site now. http://dev.zy.ca/
http://dev.zy.ca/revision/125
http://www.viper007bond.com/wordpress-plugins/forums/viewtopic.php?pid=2534
still having some issues here with backupwp 0.2.7 and weathericon 2.99.125
activated backupwp got these js errors in its backend:
x_bkpwp_ajax_create is not defined
do_create()admin.php (line 314)
onclick(click clientX=0, clientY=0)admin.php (line 1)
[Break on this error] x_bkpwp_ajax_create(preset,'');
x_bkpwp_ajax_calculater is not defined
calculate()admin.php (line 323)
onclick(click clientX=0, clientY=0)admin.php (line 1)
[Break on this error] x_bkpwp_ajax_calculater(preset,'');
and even the calculating used diskspace still hangs.
weathericon still does not activate if backupwp is activated...
oh, and for me it doesn't work the other way round neither. even if I activate weathericon first, I cannot activate Backupwp afterwards.
ovidiu, you might have another plugin activated, which uses PEAR and does not check for the dependecies or inclusion. Can you post a list of plugins you blog uses?
I found the problem today.
You have got register_globals set to off. Therefore Sajax has no access to the $_GET parameters. I am working on a solution and let you know here.
Okay ... there is still a problem ... not quite sure why it is happening ... I've synced the copies of PEAR now, but there is an interesting error in the PHP logs:
[17-Sep-2007 17:38:35] PHP Fatal error: Cannot redeclare _pear_call_destructors() (previously declared in /www/dev.zy.ca/wordpress-2.2.3/wp-content/plugins/WeatherIcon/libraries/PEAR.php:776) in /www/dev.zy.ca/wordpress-2.2.3/wp-content/plugins/backupwordpress/PEAR.php on line 807
Now this shouldn't be happening since both applications are checking to see if PEAR is loaded before loading their own ... so ... why are they both loading?
If you are using eAccelerator or another caching system, you might experience strange result on calling classes. See: http://wpforum.designpraxis.at/topic/ajax-error?replies=2#post-120
I've released BackUpWordPress versino 0.3.1
http://wordpress.designpraxis.at/2007/09/18/backupwordpress-031-released/
wow - now it works for me. but I still have the conflict with weathericon BUT I have PEAR.php on the exclude list for eaccelerator - and I can check the list of cached files and PEAR.php is not on the list, so could the error be somewhere else?
anyway, if I activate weathericon first, its working for me...
ovidiu, thanks for the feedback! And great to see it is working for you! Since the eaccelerator issue is out of the reach of WordPress and BackUpWordPress, I'll mark this resolved ;)
I just noticed one more strange thing: I have been playing with backupwp and weathericon and have enabled/disabled them several times for testing. Each time I deactivate and reactivate backupwp I have to set it up again. why does it not save its settings so when I activate it again, it already is set up?
that's because BackUpWordPress stores everything within the wp_options table. For Users who uninstall the plugin and do not want to reinstall it again, there would be unnecessary data left in that table.
The other thing is, if something goes wrong, because of a faulty setup of BackUpWordPress, and you want to start all over again, you'll need your faulty options cleaned up.
However, if you just overwrite your plugin with the newer version, all your settings would stay as is.
@rol
Thanks for the tip. However, I still get this error....
Warning: copy(/home/content/m/r/k/mrking/html/stats/.statspwd): failed to open stream: Permission denied in /home/content/m/r/k/mrking/html/wp-content/plugins/backupwordpress/bkpwp-classes/manage_backups.php on line 558
Even with that folder in my exclusion list and selected in manual back options.
You must log in to post.