• Resolved Buckeye Interactive

    (@buckeyeinteractive)


    After an auto-update to 2023.1.0, our site started returning 500s on a few custom wp-json endpoints. I’ll include the error stack below. Disabling WP REST Cache fixes the issue so I just did that until you have a chance to take a look. Thank you!

    Fatal error: Uncaught TypeError: Argument 3 passed to WP_Rest_Cache_Plugin\Includes\API\Oembed_Api::process_cache_relations() must be of the type string, array given, called in /app/wp-includes/class-wp-hook.php on line 307 and defined in /app/wp-content/plugins/wp-rest-cache/includes/api/class-oembed-api.php:105 Stack trace: #0 /app/wp-includes/class-wp-hook.php(307): WP_Rest_Cache_Plugin\Includes\API\Oembed_Api->process_cache_relations(4181, Array, Array, ‘/wp-json/easton…’) #1 /app/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(”, Array) #2 /app/wp-includes/plugin.php(476): WP_Hook->do_action(Array) #3 /app/wp-content/plugins/wp-rest-cache/includes/caching/class-caching.php(872): do_action(‘wp_rest_cache/p…’, 4181, Array, Array, ‘/wp-json/easton…’) #4 /app/wp-content/plugins/wp-rest-cache/includes/caching/class-caching.php(173): WP_Rest_Cache_Plugin\Includes\Caching\Caching->register_endpoint_cache(’92b1e960e83bffa…’, Array, ‘/wp-json/easton…’, Array, ‘GET’) #5 /app/wp-content/plugins/wp-rest-cac in?/app/wp-content/plugins/wp-rest-cache/includes/api/class-oembed-api.php?on line?105

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Richard Korthuis

    (@rockfire)

    Hi @buckeyeinteractive

    Thank you for using our plugin!

    I am very sorry to hear you are experiencing this error with our plugin. However I am not sure what is causing this error. Could you tell me if you are using the filter wp_rest_cache/determine_object_type ? And if so what you have it return as object_type?

    Plugin Author Richard Korthuis

    (@rockfire)

    Hi @buckeyeinteractive

    We just released a new version of our plugin with a hotfix that should hopefully fix your error. Could you however please still answer my questions? It helps us understand the cause of this error and what we might do in the future to prevent it.

    Plugin Author Richard Korthuis

    (@rockfire)

    This thread has been marked as resolved due to lack of activity.

    You’re always welcome to open a new topic.

    Thanks for understanding!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Uncaught TypeError after 2023.1.0 Update’ is closed to new replies.