Critical error after the last update

Humm. What does the email you received say? Accessing the link in your email should allow you to enter recovery mode.

There would seem to be a PHP error, but you’ll have to provide more details for us to assist.

If you can provide more information about your site, especially your PHP error log, that would be most helpful. You can use this form: https://forms.gle/U8utQw1MjEEZrhYN9

These logs only appear when I try to install the latest version.
I had to remove the plugin, to get the site back up and running, or if I try to do a rollback, it works normally. Also test a clean installation and the problem persists.

Thank you for the quick response! The errors that appear are the ones below:

#0 /wp-content/object-cache.php(631): Redis->connect()
#1 /wp-content/object-cache.php(480): WP_Object_Cache->connect_using_phpredis()
#2 /wp-content/object-cache.php(173): WP_Object_Cache->__construct()
#3 /wp-includes/load.php(701): wp_cache_init()
#4 /wp-settings.php(131): wp_start_object_cache()
#5 /wp-config.php(104): require_once('/var/www/html/m...')
#6 /wp-load.php(37): require_once('/var/www/html/m...')
#7 /wp-blog-header.php(13): require_once('/var/www/html/m...')
#8 /public_html/index.php(17): require('/var/www/html/m...')
#9 {main}PHP message: PHP Fatal error:  Uncaught AmpProject\AmpWP\Exception\InvalidService: The service ID "paired_routing" is not recognized and cannot be retrieved. in /wp-content/plugins/amp/src/Exception/InvalidService.php:57
Stack trace:
#0 /wp-content/plugins/amp/src/Infrastructure/ServiceContainer/SimpleServiceContainer.php(39): AmpProject\AmpWP\Exception\InvalidService::from_service_id()
#1 /wp-content/plugins/amp/src/Services.php(55): AmpProject\AmpWP\Infrastructure\ServiceContainer\SimpleServiceContainer->get()
#2 /wp-content/plugins/amp/includes/amp-helper-functions.php(1861): AmpProject\AmpWP\Services::get()
#3 /wp-content/plugins/amp/includes/amp-helper-functions.php(744): amp_has_paired_endpoint()
#4 /wp-content/plugin

Please send your Site Health information via this form: https://forms.gle/U8utQw1MjEEZrhYN9

This will help us attempt to replicate your site setup so we can try to reproduce the issue.

Also, does error only occur when visiting an AMP page on the frontend? Or does it happen when accessing non-AMP pages or even the WP admin?

I just filled out the google form.

This occurs on the entire site. From backend and frontend, without or with amp. Only when I remove the current version that returns to work normally.
I also tested the github version two days ago and presented the same error. I cleared the site’s cache and nothing happens!

Thank you. However, there was a problem with the Site Health information you provided. All of the line breaks were removed for some reason, so it is very difficult to read.

Also, something else that would be very helpful if you could use the Health Check & Troubleshooting Plugin to isolate the specific plugin that is causing the incompatibility. We’ve put together a few steps in a guide. In Troubleshooting Mode, you can enable plugins one-by-one for you as an administrator in order to isolate which one is causing the incompatibility.

Also, the error you are reporting is something I had seen before, but I specifically had fixed it: https://github.com/ampproject/amp-wp/pull/5899

Perhaps there is a case that I hadn’t accounted for.

Also, the stack trace you provided is unfortunately cut off. It would be helpful if the entire stack trace could be provided.

Also, I can reproduce this error if I try calling is_amp_endpoint() (or its alias amp_is_request()) before the plugins_loaded action. Can you check your themes/plugins to see if any of them are calling that that function too early?

I use Newspapper which has a direct integration with AMP. Only if this plugin update is no longer supported. I’m going to disable the theme’s newsapper plugin.

If that doesn’t work, I have opened a PR which may address the problem: https://github.com/ampproject/amp-wp/pull/6181

Specifically, if you can just patch the amp_*_paired_endpoint() functions as shown here: https://github.com/ampproject/amp-wp/pull/6181/files

This should prevent the fatal error which may help identify what theme/plugin is calling the function incorrectly.

How I suspected! The standard tagdiv newspapper amp theme plugin is causing this problem.

Would there be any interim solution that I can implement? Or do I have to wait for the theme itself to update this function?

I made the changes shown at the link: https://github.com/ampproject/amp-wp/pull/6181/files

But he continued with the same mistake.

To confirm: if you deactivate the tagDiv Mobile Theme plugin, then an error no longer occurs?

If so, we’ll investigate what is going on with that plugin.

You may want to submit a support request to tagDiv as well.

Exactly! When deactivated, the error no longer occurs.

Hi, I am using tagDiv newspaper theme too. Could you solve the problem? I haven’t update amp yet. I don’t use the mobile version of the newspaper theme since the theme itself is already mobile-friendly. But, I am using AMP in the reader theme AMP legacy mode, which mode do you use amp currently?