• Resolved fotske

    (@fotske)


    Hi,

    I realized in the Fatal error logs under WooCommerce > Status > Logs that your plugin creates a fatal error every day:

    Uncaught Error: Unknown named parameter $arg in /home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php:324

    “error”: { “type”: 1, “file”: “/home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php”, “line”: 324 }, “remote-logging”: true, “backtrace”: [ “”, “#0 /home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)”, “#1 /home/customer/www/mywebsite.com/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)”, “#2 /home/customer/www/mywebsite.com/public_html/wp-cron.php(191): do_action_ref_array(‘backwpup_cron’, Array)”, “#3 {main}”, “thrown” ] }

    Could you please solve this issue?

    Thank you very much in advance.

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

    (@saranshwpm)

    Hello @fotske,

    Thanks for sharing this log with us.

    This might be related to the PHP version currently running on your site. Could you please let me know:

    • The PHP version your site is using
    • The version of the BackWPup plugin installed

    Also, are you facing any specific issue while using BackWPup because of this error?

    Looking forward to your reply so we can dig in further.

    Thread Starter fotske

    (@fotske)

    Hello,

    • My PHP version is 8.2.28.
    • The BackWPup version is 5.2.3

    I checked BackWPup in WordPress and I realize in the backup history that the last backup dates back to September 23 2024…

    So I think that the plugin does not work on my website anymore since this date…

    Plugin Support Saransh

    (@saranshwpm)

    Hello @fotske,

    Thanks for the details.

    Based on what you shared, it’s possible this issue is linked to an old legacy backup job that was created before September 2024. Around that time, we released version 4.1.5 which removed the EasyCron integration and made some deeper changes to how cron jobs are handled. If any of those legacy jobs still reference outdated structures, it might be causing the current error during scheduled runs.

    Here’s what I’d suggest:

    1. Go to BackWPup > Advance Settings > Jobs tab Check if there’s any job listed under the “Access to legacy jobs” section.
    2. If you see old jobs there and you no longer use them, you can safely delete them.
    3. After that, try running a manual backup directly from the dashboard using the “Run Now” button. Here’s a quick guide on that: 👉 https://backwpup.com/docs/starting-backup-job-immediately-or-scheduled/

    Let me know if the error still shows up after that, we’ll take it from there.

    Best regards,

    Plugin Support Saransh

    (@saranshwpm)

    Hi,

    Since we haven’t received any follow-up, I’ll go ahead and mark this as closed for now.

    If you need any further help, feel free to reach out anytime.

    Thread Starter fotske

    (@fotske)

    Hi,

    Sorry for my late reply.

    I followed your steps and I still have a fatal error in the WooCommerce logs:

    2025-08-03T01:00:03+00:00Critique Uncaught Error: Unknown named parameter $arg in /home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php:324 Contexte supplémentaire{ “error”: { “type”: 1, “file”: “/home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php”, “line”: 324 }, “remote-logging”: true, “backtrace”: [ “”, “#0 /home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)”, “#1 /home/customer/www/mywebsite.com/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)”, “#2 /home/customer/www/mywebsite.com/public_html/wp-cron.php(191): do_action_ref_array(‘backwpup_cron’, Array)”, “#3 {main}”, “thrown” ] }2025-08-03T02:00:02+00:00Critique Uncaught Error: Unknown named parameter $arg in /home/customer/www/mywebsite.com/public_html/wp-includes/class-wp-hook.php:324

    Why is that and how to solve this issue?

    Plugin Support Saransh

    (@saranshwpm)

    Hi,

    This seems to be something very specific to your setup and backup file. I would recommend reaching out to our support team directly from our website, so we can review the backup in detail and identify what exactly is causing the issue.

    Best Regards,

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

The topic ‘Fatal error caused by the Backwpup plugin’ is closed to new replies.