• We are trying to develop a site using WordPress Multi-Site. EVerything has been working OK until yesterday when we began getting this error message displayed within the Dashboard when trying to move between one area of the Dashboard to another. We have a total of two users, one with Super-Admin, the other with Subscriber status:

    Notice: add_object_page is deprecated since version 4.5.0! Use add_menu_page() instead. in /home/borgec/public_html/wp-includes/functions.php on line 3828

    Notice: has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/borgec/public_html/wp-includes/functions.php on line 4020
    Sorry, you are not allowed to access this page.

    And then on the public side of the page itself – this error displays across the top:

    Notice: Undefined property: EasyColumns::$use_custom in /home/borgec/public_html/wp-content/plugins/easy-columns/easy-columns.php on line 233

    I’ve tried disabling various plugins, for the Easy Columns plugin I even deleted it altogether, then re-installed a fresh copy, and still getting the above error message.

    Any suggestions where to look or what to do?

    p.s. here is the site – not much up there yet – very rough:
    https://goddessguide.com/

    • This topic was modified 7 years, 10 months ago by yukon4.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    As those are just notices, they’re not major issues.

    Do you have wp_debug set to true in wp-config.php? If so, set it to false to hide them or just disable display of notices (but log them until you’re ready to go into production:

    
    define('WP_DEBUG_DISPLAY', false);
    define('WP_DEBUG_LOG', true);

    So what happened yesterday? Are you running on the same version of PHP?

    Thread Starter yukon4

    (@yukon4)

    Ah – – yes – I have it set to true. So, you’re saying these “bugs” are nothing to worry about and turn off debug and “out of sight, out of mind”? : )

    I will try that. Thank you!

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    I suggest you leave logging on so you can check things as you develop, but when you go into production, disable wp_debug_log and delete wp-content/debug.log as it can otherwise get very large and potentially expose sensitive stuff.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Mystery Error Message Suddenly’ is closed to new replies.