Support » Plugin: BackUpWordPress » Upgrade to 2.3 breaks site

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Paul de Wouters

    (@pauldewouters)

    Human Made

    Hi, thanks for using BackUpWordPress and reporting this problem.

    We are aware of the issue, and are investigating the caue.

    It would be helpful if you could install a plugin that displays the active backup jobs
    http://wordpress.org/plugins/wp-crontrol/

    and link to a screenshot of the list of cron jobs.

    thanks

    Hi Paul:
    I already had the “What’s in Cron” plugin installed, so easy to do a screenshot for you: http://holeinthedonut.com/Screen%20Shot%202013-07-11%20at%2011.40.51%20AM.png

    I might add that when this first happened I checked the WP Cron and found some remaining jobs from two other backup plugins that I had used in the past, both of which were so poorly designed that they did not clean up the scheduled cron jobs when I uninstalled them. I removed those jobs from cron about a week ago, so when I tried to upgrade today, that could not have been the conflict.

    Also, there are other jobs below those shown, but they are all “publish future post”

    Plugin Author Paul de Wouters

    (@pauldewouters)

    Human Made

    Hi baweibel,

    thanks for the quick reply!

    Looks like the cron job is being scheduled properly. It would be great if you could turn WP_DEBUG on and trigger the error again and paste the results here or in a pastebin.

    Also, if you’re comfortable with th mySQL database, could you send us the content of the BackUpWordPress option?
    It should be listed as hmbkp_schedule_default-1 or hmbkp_schedule_default-2 or hmbkp_schedule_daily

    thanks

    Sorry Paul, but that’s all WAY beyond my ability

    Plugin Author Paul de Wouters

    (@pauldewouters)

    Human Made

    no worries, thanks for your help.

    I’m having the same issue — since updating to the latest version, the admin CP is inaccessible due to the error mentioned above.

    I’m available to give you any data that you need to diagnose the issue.

    Here’s what I have listed in the mysqldb:

    option_id option_name option_value autoload
    17767 hmbkp_plugin_version 2.2.4 yes
    30743 hmbkp_default_path /Volumes/data/ServiceData/Web/rimdog/wp-content/526701e277-backups yes
    30785 hmbkp_path /Volumes/data/ServiceData/Web/rimdog/wp-content/526701e277-backups yes
    29436 hmbkp_schedule_backup a:3:{s:4:”type”;s:8:”complete”;s:12:”reoccurrence”;s:5:”daily”;s:11:”max_backups”;i:10;} yes

    I’m having the same issues as mentioned here. This is what is in the mysqldb:

    option_id option_name option_value autoload
    17767 hmbkp_plugin_version 2.2.4 yes
    30743 hmbkp_default_path /Volumes/data/ServiceData/Web/rimdog/wp-content/526701e277-backups yes
    30785 hmbkp_path /Volumes/data/ServiceData/Web/rimdog/wp-content/526701e277-backups yes
    29436 hmbkp_schedule_backup a:3:{s:4:”type”;s:8:”complete”;s:12:”reoccurrence”;s:5:”daily”;s:11:”max_backups”;i:10;} yes

    with WP-DEBUG enabled, the output is:

    [Fri Jul 12 07:36:54 2013] [error] [client 192.168.5.53] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Argument 1 for HMBKP_Scheduled_Backup::set_reoccurrence must be a valid cron reoccurrence or “manually”‘ in /Volumes/data/ServiceData/Web/rimdog/wp-content/plugins/backupwordpress/classes/schedule.php:484\nStack trace:\n#0 /Volumes/data/ServiceData/Web/rimdog/wp-content/plugins/backupwordpress/functions/core.php(151): HMBKP_Scheduled_Backup->set_reoccurrence(‘hmbkp_daily’)\n#1 /Volumes/data/ServiceData/Web/rimdog/wp-content/plugins/backupwordpress/backupwordpress.php(156): hmbkp_update()\n#2 [internal function]: hmbkp_init(”)\n#3 /Volumes/data/ServiceData/Web/rimdog/wp-includes/plugin.php(406): call_user_func_array(‘hmbkp_init’, Array)\n#4 /Volumes/data/ServiceData/Web/rimdog/wp-admin/admin.php(111): do_action(‘admin_init’)\n#5 /Volumes/data/ServiceData/Web/rimdog/wp-admin/plugins.php(10): require_once(‘/Volumes/data/S…’)\n#6 {main}\n thrown in /Volumes/data/ServiceData/Web/rimdog/wp-content/plugins/backupwordpress/classes/schedule.php on line 484, referer: http://www.rimdog.com/wp-admin/plugins.php

    Plugin Author Paul de Wouters

    (@pauldewouters)

    Human Made

    thanks for the data, looks like there’s an issue with the upgrade routine. Do you remember what version you upgraded from?

    I tried to upgrade from 2.2.4 if that helps.

    Handoko

    (@handoko-zhang)

    @baweibel:

    I have similar case. I guess the upgrade routine conflicts with one or some plugins I’m using. So I disabled all the other plugins and upgraded BackUpWordPress to version 2.3. Everything is working correctly so far.

    Sorry for the delayed reply. I upgraded from whatever the previous version of Backup WordPress was. I always try to keep my plugins up to date.

    @handoko

    Did you re-enable the plugins after installing 2.3?
    And did everything still work?

    Handoko

    (@handoko-zhang)

    Yes, everything is working correctly. I first disabled all other plugins, upgraded BackUpWordPress to version 2.3, and enabled all other plugins.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Upgrade to 2.3 breaks site’ is closed to new replies.