• [ Moderator note: moved to How-to and Troubleshooting. ]

    Hi,

    When you choose the “debug mode” you can get things as that :

    Notice: WP_Query est appelé avec un argument qui est déprécié depuis la version 3.1.0 ! « caller_get_posts » n’est plus recommandé. Utilisez « ignore_sticky_posts » à la place. in …/wp-includes/functions.php on line 3891

    Notice: WP_Query est appelé avec un argument qui est déprécié depuis la version 3.1.0 ! « caller_get_posts » n’est plus recommandé. Utilisez « ignore_sticky_posts » à la place. in …/wp-includes/functions.php on line 3891

    This is truly not at all useful to tell you that “somewhere” into several million of lines of code there is a deprecated call…

    I had hacked this into a previous version and imagine reported it.
    I had just added to references of the error, which more useful.

    Thanks to implement such enhancement into the next version.

    Because I cannot avoid to use debug mode to get good code, I need to hack again the core or seek old versions of core to find my hack.
    When done I will report here.

    Best regards

    Trebly

Viewing 2 replies - 1 through 2 (of 2 total)
  • I need to hack again the core or seek old versions of core to find my hack.

    No. What you need to do is determine which plugin (or your theme) is using a deprecated function and get it updated, not edit core files.

    This is truly not at all useful to tell you that “somewhere” into several million of lines of code there is a deprecated call…

    It isn’t about “hacking” the WordPress core, because there is nothing wrong with it. It’s a message about a theme or plugin that is using a deprecated function. That is all it is.

    • This reply was modified 7 years, 7 months ago by Clayton James.

    Another thing to remember is that what you are seeing is a PHP notice, not a message from WordPress itself.

    You need to follow Clayton’s advice and find out which plugin or theme is causing that. That’s done by very basic debugging of deactivating all plugins and changing to a default (Twenty*) theme. From there, re-enable everything one-by-one until you find out which one is causing that problem. That will narrow down your search to where you should actually be looking.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Debug mode : not useful “Notices”’ is closed to new replies.