Support » Plugin: Go Fetch Jobs (for WP Job Manager) » Getting error: wp_no_robots is deprecated

  • Resolved bbtodd

    (@bbtodd)


    On job listings that have been imported I’m seeing this a lot:
    Deprecated: wp_no_robots is deprecated since version 5.7.0! Use wp_robots_no_robots() instead. in wp-includes/functions.php on line 4861

    On jobs that are input directly into this site I have not seen this error.

    So I scanned the fetch plugin folder for ‘wp_no_robots’ and I found this on line 81 of the file class-gofetch-frontend.php

    if ( $goft_wpjm_options->block_search_indexing ) {
    			wp_no_robots();
    			return;
    		}

    Is this causing the problem? Shouldn’t this use wp_robots_no_robots() instead?

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author SebeT

    (@sebet)

    Thank you for the heads up @bbtodd.

    You’re right. The recent WP update has deprecated that function. I’ll update the plugin to use the new ‘wp_robots_no_robots()’ ASAP.

    Thread Starter bbtodd

    (@bbtodd)

    Thanks for your quick reply. I saw there was an update to the Fetch plugins and I upgraded to Version 1.7.0.1 but I still see the wp_no_robots code in there.

    Do you know when this change will be pushed live?

    Thank you.

    Plugin Author SebeT

    (@sebet)

    I had version 1.7.0.1 already prepared, so I wasn’t able to do this change. I’m adding it to the next release, which include some additional fixes and changes.

    Note that if you have that warning showing on the frontend, it means that you have debug display enabled.

    I suggest you enable debug logging instead so that warnings are displayed on an external file instead of on screen.

    To disable warnings and enable debug logging instead follow these steps:

    1. edit your site ‘wp-config.php’ file (located on your site WP root)
    2. copy&paste these lines right BEFORE the line: /* That’s all, stop editing! Happy blogging. */

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

    3. Any errors should now be dumped to a new file named ‘debug.log’ located under ../wp-content/

    Thread Starter bbtodd

    (@bbtodd)

    🙏 Very helpful. Much Appreciated.

    • This reply was modified 1 month, 1 week ago by bbtodd.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.