Jetpack register_rest_route error

  • Resolved fredlightstone

    (@fredlightstone)


    2 weeks, 3 days ago

    Jetpack updated on my site today and the following error appeared in the admin dashboard: Notice: Function register_rest_route was called?incorrectly. REST API routes must be registered on the?rest_api_init?action. Instead route ‘site/update-historically-active-modules‘ with namespace ‘my-jetpack/v1‘ was not registered on this action. Please see?Debugging in WordPress?for more information. (This message was added in version 5.1.0.) in?/var/www/wptbox/wp-includes/functions.php?on line?6114

    Previously there was no error and I have tested plugins for conflicts. The only thing that works is deactivating Jetpack.

    Current list of plugins activated on my site:

    • Accessibility by Userway
    • Admin Menu Editor
    • Akismet
    • All in one seo
    • Better Admin bar
    • cartflows
    • elementor
    • elementor pro
    • Fancy Product Designer
    • Image optimizer by elementor
    • Jetpack
    • Mailpoet
    • Woocommerce
    • Woocommerce product addons
    • woocommerce shipping
    • woocommerce shipping and tax
    • Woopayments
    • WP File manager

    Theme: Hello biz

    • This topic was modified 2 weeks, 3 days ago by fredlightstone.
    • This topic was modified 2 weeks, 3 days ago by fredlightstone. Reason: The image and some crucial information did not appear on the post
Viewing 6 replies - 1 through 6 (of 6 total)

  • I’m getting the same error. It’s also messing up the spacing of my WordPress Dashboard.

    Thread Starter fredlightstone

    (@fredlightstone)

    It is nice to know that it is not just me.

    Thread Starter fredlightstone

    (@fredlightstone)

    @ferio252 I found out that you can hide the notification by going to the WP-Config.php wordpress core file and changing define( ‘WP_DEBUG’, true ); to define( ‘WP_DEBUG’, false );

    Since it is only a notification there will not be a major impact on your website.

    Plugin Support fujifika (a11n)

    (@fujifika)

    Hi there @fredlightstone and @ferio252 – thanks for flagging this!

    We’re aware of this notice, and you can safely disregard it—it doesn’t impact your site’s functionality. Hiding it as you’ve done is the recommended approach, and this will be fully resolved in the next version update.

    Appreciate your patience, and great job finding the workaround!

    If you have any other questions or need further assistance regarding this, feel free to respond here. If it’s a separate topic, please create a new forum thread so we can assist you more effectively, as we handle each case individually.

    Thanks!???

    Jeff Salazar

    (@jsierra1ronin)

    Hello @fujifika

    Has this issue been resolved?

    Plugin Support Chatoxz (a11n)

    (@chatoxz)

    Hi @jsierra1ronin,

    Sebastian here, I hope you are doing well.

    As Fujifika mentioned, the developers are already aware of and working to fix the underlying issue. We don’t have an ETA, but it should included in the next Jetpack version.

    That said, as this notice doesn’t affect your site’s functionality, you can hide the notice and keep using your site as usual. You can do that by replacing the next code line on your site’s wp-config.php file:

    define('WP_DEBUG', true);

    … with this:

    define('WP_DEBUG', false);

    Thanks for your patience.

    Warm regards.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.

Tags