Undefined constant ERROR_TYPE_REST

Resolved

(@alduinwf)

Hello,

Apparently, the recent update to Jetpack 16.1 introduced an error that results in a large number of WordPress emails reporting a technical problem with the site. A cron job I’m running via WP-CLI also throws essentially the same error.

The error appears to be caused by a reference to a constant that is not defined:

Ein Fehler vom Typ E_ERROR wurde in der Zeile 57 der Datei [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php verursacht. Fehlermeldung: Uncaught Error: Undefined constant Automattic\Jetpack\Connection\Error_Handler::ERROR_TYPE_REST in [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php:57
Stack trace:
#0 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(488): Automattic\Jetpack\Connection\Client::remote_request()
#1 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/traits/trait-wpcom-rest-api-proxy-request.php(106): Automattic\Jetpack\Connection\Client::wpcom_json_api_request_as_blog()
#2 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/traits/trait-wpcom-rest-api-proxy-request.php(149): Automattic\Jetpack\Publicize\REST_API\Proxy_Requests->proxy_request_to_wpcom()
#3 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-connections.php(159): Automattic\Jetpack\Publicize\REST_API\Proxy_Requests->proxy_request_to_wpcom_as_blog()
#4 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-connections.php(129): Automattic\Jetpack\Publicize\Connections::fetch_site_connections()
#5 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-connections.php(40): Automattic\Jetpack\Publicize\Connections::fetch_and_cache_connections()
#6 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-connections.php(77): Automattic\Jetpack\Publicize\Connections::get_all()
#7 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-publicize-base.php(1347): Automattic\Jetpack\Publicize\Connections::get_all_for_user()
#8 [path]/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-publicize/src/class-publicize-base.php(1290): Automattic\Jetpack\Publicize\Publicize_Base->any_connection_has_custom_template()
#9 [path]/wp-includes/class-wp-hook.php(341): Automattic\Jetpack\Publicize\Publicize_Base->register_post_meta()
#10 [path]/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#11 [path]/wp-includes/plugin.php(522): WP_Hook->do_action()
#12 [path]/wp-settings.php(771): do_action()
#13 [path]/wp-config.php(48): require_once('...')
#14 [path]/wp-load.php(50): require_once('...')
#15 [path]/wp-login.php(12): require('...')
#16 {main}
  thrown

Some information about the environment:

WordPress-Version 7.0.3
Aktive Theme: My theme (Version )
Current Plugin: Jetpack (Version 16.1)
PHP-Version 8.3.33

I’m seeing this on multiple websites.

Thank you for looking into this!

Viewing 7 replies - 1 through 7 (of 7 total)

Plugin Support Alin (a11n)
(@alinclamba)

1 month, 1 week ago

Hi @alduinwf,

Thanks for reporting this and for including the full error details.

We’ve confirmed an issue in Jetpack 16.1 that can trigger this Undefined constant ERROR_TYPE_REST fatal error while Jetpack is being automatically updated.

The error happens during the update process itself and should stop once the update has completed. Our developers have already prepared and merged a fix, and we’re working on a point release to prevent this from happening during future updates.

So if Jetpack 16.1 is now fully updated on those sites and they’re otherwise working normally, there shouldn’t be anything you need to change on your end.

Thanks again for bringing this to our attention!

Thread Starter alduinwf
(@alduinwf)

1 month, 1 week ago

Hi @alinclamba,

Thank you for your response. I can confirm that the upgrade to 16.1.1 was uneventful and has not triggered any further emails. 🙂

Plugin Support Tamirat B. (a11n)
(@tamirat22)

1 month, 1 week ago

Thanks for coming back to confirm, and glad that sorted it out. If anything similar turns up again, please start a new thread and we will pick it up there.

If you are finding Jetpack valuable, please consider leaving a review.

Best,

elgopa
(@elgopa)

1 month ago

its not sorted out yet…..
Plugin Support Josh (a11n)
(@vitkory)

1 month ago
Howdy @elgopa

Thanks for chiming in. Since this thread was resolved for the original reporter after the Jetpack 16.1.1 update, could you start a new thread with your specific details? That way we can properly track and troubleshoot your situation.

When you create the new thread, please include:
- Your current Jetpack version
- Your WordPress and PHP versions
- The full error message you’re seeing
- When the error occurs (during updates, normal browsing, etc.)
We’ll pick it up from there!
elgopa
(@elgopa)

1 month ago

sorry, not going to make a new thread.

i had to delete yetpack, so no error messages neither to report

Plugin Support Josh (a11n)
(@vitkory)

1 month ago

@elgopa – no worries. If you want to try again with Jetpack in the future, feel free to reach out to us directly in the future, that would be the best way for us to assist you as we can get more information and debug alongside you.

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.