Fatal error: Uncaught Error: Call to undefined function wp_is_serving_rest_reque

  • Resolved warhangel7

    (@warhangel7)


    3 days, 12 hours ago

    Hello!
    After updating to 5.3.4:

    Fatal error: Uncaught Error: Call to undefined function wp_is_serving_rest_request() in /var/www/…./wp-content/plugins/wp-cloudflare-page-cache/vendor/woocommerce/action-scheduler/classes/ActionScheduler_RecurringActionScheduler.php:29 Stack trace: #0 /var/www/…../wp-includes/class-wp-hook.php(306): ActionScheduler_RecurringActionScheduler->init() #1 /var/www/…./wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #2 /var/www/…../wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /var/www/…../wp-settings.php(623): do_action(‘init’) #4 /var/www/…../wp-config.php(95): require_once(‘/var/www/…..’) #5 /var/www/…../wp-load.php(50): require_once(‘/var/www/……’) #6 /var/www/…../wp-admin/admin.php(34): require_once(‘/var/www/……’) #7 /var/www/……/wp-admin/index.php(10): require_once(‘/var/www/……’) #8 {main} in /var/www/……/wp-content/plugins/wp-cloudflare-page-cache/vendor/woocommerce/action-scheduler/classes/ActionScheduler_RecurringActionScheduler.php on line 29

    The Call to undefined function wp_is_serving_rest_request() error occurs because a plugin is trying to use a native WordPress function that does not exist in my current WordPress version. (6.2.11)

    So, I think it would be better to limit updates on websites below version 6.5.0 or remove this function from 5.3.4…

Viewing 1 replies (of 1 total)
  • Plugin Support rodicaelena

    (@rodicaelena)

    1 day, 18 hours ago

    Hi there,

    Thank you for the detailed report.

    I’ve passed this on to our development team with all the details from your report, including your suggestions. I can’t promise a specific outcome or timeline at this point, whether we ship a compatibility fix, raise the plugin’s minimum WordPress requirement so the update is no longer offered to older sites, or both, is up to the team once they’ve reviewed it. I’ll update this thread as soon as I have an update.

    In the meantime, two things that will get you running again:

    1. Roll back to 5.3.3.
    2. If it’s an option for you, updating WordPress to a newer version also resolves it.
      Worth noting that 6.2.x only receives security fixes at this point, so moving to a
      current release is a good idea regardless; on a staging copy first, ideally.

    Kind regards!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.