• Resolved mikeverduin

    (@mikeverduin)


    with the update to 3.7.1 I’m now getting this error:

    Deprecated: Non-static method BackWPup_Admin::admin_css() should not be called statically in /home/verduins/public_html/wp-includes/class-wp-hook.php on line 288

    any thoughts?

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter mikeverduin

    (@mikeverduin)

    line 288 of that file has nothing to do with it as far as I can tell.

    I’ve searched class-wp-hook.php for “admin” “backup” and “css” and none of them are in that file.

    Thread Starter mikeverduin

    (@mikeverduin)

    New Problem.

    I deactivated the plugin, then reactivated it.

    Error is gone now, but so is the menu for BackupWP. There are still cron events to run on the wp-cron events page, but I can’t change anything.

    Plugin Support happyAnt

    (@duongcuong96)

    Hi @mikeverduin
    Did you update WordPress to the latest version? and which PHP version you running now?
    Thank you!

    Thread Starter mikeverduin

    (@mikeverduin)

    I’m running 5.3.2 wordpress
    PHP I have no control over but I’m running: 7.0.33

    I am getting the same error.
    PHP version was initially 7.0.33, but after an error I changed it to 7.2.27.
    Still, there is no change.

    5.3.2 WordPress
    7.2.27 PHP

    Thread Starter mikeverduin

    (@mikeverduin)

    This morning, the dashboard is fine again and I have control over the plug in. all is fine.

    I’m wondering if turning it off and on fixed it, and maybe I needed to clear a browser cache in Edge to see the dashboard/menu again.

    Thread Starter mikeverduin

    (@mikeverduin)

    Whoops.

    Now that the dashboard is back, the error is back too.

    Thread Starter mikeverduin

    (@mikeverduin)

    This fixed it for me:

    went to public_html/wp-content/plugins/backwpup/inc

    edit the file class-admin.php

    line 28

    change “public function” to “public static function”

    saved it and it got rid of the error.

    I’m having the same issue on a page that did not have the issue before the weekend.

    Deprecated: Non-static method BackWPup_Admin::admin_css() should not be called statically in */wp-includes/class-wp-hook.php on line 288

    If mikeveruin says he fixed it by editing the plugin, and three people suddenly report the same error, it seems to be an issue with the plugin – most likely line 28.

    I’ll apply Mike’s patch and hope the plugin developers include the patch in the next update so our hasty patches won’t be overwritten.

    Gilles

    (@alizesonline)

    Same issue with one of my client’s website. It is running under WP 5.3.2 and Divi 4.3.4. The message disappeared when I removed the BackWPup tools menu from the admin top bar.

    The issue was caused by a warning text that was added to the head section of the html.

    Same issue since the 5.4 of WordPress

    Thread Starter mikeverduin

    (@mikeverduin)

    I’ve remarked it as ‘unresolved’

    I am also experiencing this issue.

    Here is the error message in the debug log:
    PHP Deprecated: Non-static method BackWPup_Admin::admin_css() should not be called statically in */wp-includes/class-wp-hook.php on line 287

    BackWPup version: 3.7.1
    WordPress version: 5.4
    PHP version: 7.2.29

    Anonymous User 15026628

    (@anonymized-15026628)

    Hello

    Yes, we have the same issue coming up after updating to WP 5.4.

    PHP Deprecated: Non-static method BackWPup_Admin::admin_css() should not be called statically in .../wp-includes/class-wp-hook.php on line 287

    BackWPUp: 3.7.1
    WP: 5.4

    Do you have a solution?

    Kind regards, Odilo

    Thread Starter mikeverduin

    (@mikeverduin)

    This fixed it for me:

    went to public_html/wp-content/plugins/backwpup/inc

    edit the file class-admin.php

    line 28

    change “public function” to “public static function”

    saved it and it got rid of the error.

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Error on every page 3.7.1 update’ is closed to new replies.