Fatal error on 5.3 update

  • Resolved Christian Roth

    (@christiangoyippi)


    4 months, 1 week ago

    Hi, the 5.3 update caused a fatal error on two websites:

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 50 der Datei /path_to_wordpress/wp-content/plugins/backwpup/inc/class-migrate.php verursacht. Fehlermeldung: Uncaught TypeError: BackWPup_Migrate::migrate_storage_token(): Argument #3 ($jobs) must be of type array, bool given, called in /path_to_wordpress/wp-content/plugins/backwpup/inc/class-migrate.php on line 38 and defined in /path_to_wordpress/wp-content/plugins/backwpup/inc/class-migrate.php:50
    Stack trace:
    #0 /path_to_wordpress/wp-content/plugins/backwpup/inc/class-migrate.php(38): BackWPup_Migrate->migrate_storage_token()
    #1 /path_to_wordpress/wp-content/plugins/backwpup/inc/class-install.php(31): BackWPup_Migrate::migrate()
    #2 /path_to_wordpress/wp-content/plugins/backwpup/src/Plugin/Plugin.php(141): BackWPup_Install::activate()
    #3 /path_to_wordpress/wp-includes/class-wp-hook.php(324): WPMedia\BackWPup\Plugin\Plugin->init()
    #4 /path_to_wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #5 /path_to_wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
    #6 /path_to_wordpress/wp-settings.php(578): do_action()
    #7 /path_to_wordpress/wp-config.php(118): require_once('/path_to_wordpress...')
    #8 /path_to_wordpress/wp-load.php(50): require_once('/path_to_wordpress...')
    #9 /path_to_wordpress/wp-admin/admin.php(35): require_once('/path_to_wordpress...')
    #10 /path_to_wordpress/wp-admin/index.php(10): require_once('/path_to_wordpress...')
    #11 {main}
     thrown

    Both Websites are hosted on a shared hosting package at domainFactory.

    All the best
    Christian

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Plugin Support

    (@saranshwpm)

    4 months, 1 week ago

    Hi Christian,

    Thank you for letting us know.

    Could you please confirm what type of backup jobs you have on the affected sites — file backup, database backup, or both? Also, please check if there are any legacy jobs left on the site under:

    BackWPUp > Advanced Settings > Jobs > Access to Legacy Jobs

    Apart from this error message, do you notice any issue with running backups or using the plugin?

    Let me know, and I’ll check further for you

    Thread Starter Christian Roth

    (@christiangoyippi)

    4 months, 1 week ago

    Hi, that is not possbile. As soon as I activate the plugin, the site is unaccessible due to the fatal error.

    From the zip files in the uploads folder I can see that there are both backup types, file and database backups. As far as I know there are no legacy jobs left.

    All the best
    Christian

    Plugin Support Plugin Support

    (@saranshwpm)

    4 months, 1 week ago

    Hi Christian,

    Thank you for the update.

    It seems the issue might be related to one of the existing jobs being corrupted, which could be causing the fatal error on activation. In most cases, reinstalling the plugin helps resolve this. Could you please try reinstalling and see if it clears the issue?

    If reinstalling is not an option, feel free to reach out to us directly so we can check this further for you and help fix it.

    Let me know how it goes.

    Thread Starter Christian Roth

    (@christiangoyippi)

    4 months, 1 week ago

    Hi,

    just reinstalling the plugin was not helping. The fatal error appears immediately after activating the plugin again. I had to manually delete all the backwpup option values in the database. Then I could activate the plugin and set up the jobs from scratch.

    All the best
    Christian

    Plugin Support Plugin Support

    (@saranshwpm)

    4 months, 1 week ago

    Hi Christian,

    I am glad you were able to sort it out, even though it was not an ideal experience.

    I want to let you know that this has been discussed internally, and we are already working on measures to prevent such issues in future updates. We will be releasing a fix for this in v5.3.1.

    Thank you again for your patience and for sharing this with us.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.