“script amp-onerror” is missing or specified incorrectly

Hello @uvozov

Thank you for the support topic, can you please send your site health information using this form so we can debug this further.

Hello @milindmore22

done

We’re experiencing the very same issue.

(on a related note: users of the Web Stories plugin also report the same issue and they have been advised that AMP upstream has very recently added amp-onerror validation, etc, causing issues in some circumstances).

Hello @gyrdnv

please send the information via this form so that colleagues can detect the problem faster.

For more information on the issue related to Web Stories, see https://github.com/google/web-stories-wp/issues/7763

In any case, the issue is being fixed by the AMP team on the validator side: https://github.com/ampproject/amphtml/issues/22543#issuecomment-849734114

In the meantime, what you can do is disable the AmpBoilerplateErrorHandler transformer using this plugin code:

add_filter( 'amp_optimizer_config', static function ( $config ) {
	$config['transformers'] = array_diff( $config['transformers'], [ AmpProject\Optimizer\Transformer\AmpBoilerplateErrorHandler::class ] );
	return $config;
} );

• This reply was modified 3 years, 10 months ago by Weston Ruter.

Thank you @westonruter

Please tell me how to do this and what will be the consequences?

Here’s a mini plugin that has that workaround: https://gist.github.com/westonruter/d13eb0175a22f83c41531e7d1a7071fd

The amp-onerror functionality is optional. It’s purpose is to make the page show faster when the boilerplate CSS can’t be removed during server-side rendering and the AMP runtime JS fails to load due to a network problem.

It was only recently added to AMP. More details can be found in https://github.com/ampproject/amphtml/issues/22543

It’s fine to disable until the validator fix is implemented by the AMP team.

I downloaded and installed the plugin. Sent the page for re-checking in the Google Search Console. I received the message “Unable to continue checking. The affected pages were found. Fix the problem and check again.”

Did I do something wrong?

Using the Google Search Console AMP Test tool, I just checked one such AMP page: https://uvozov.ru/uborka-snega-na-dorogah-spb/amp/

And it shows that it is a valid AMP page:

Nevertheless, for the homepage specifically I see that the non-AMP version has a link to an AMP version, but when attempting to go to https://uvozov.ru/amp/ it redirects me to https://uvozov.ru/

Perhaps you have elected to keep some invalid AMP markup which is causing this redirection? I suggest trying to click the “Validate URL” link in the AMP admin bar when on the homepage to investigate further.

Hello @westonruter

I’m sorry I didn’t answer. I was on vacation.

I checked the link in the AMP admin panel. Everything seems to be approved. Now, when switching to https://uvozov.ru/amp / the redirect doesn’t work.

However, the “script amp-onerror” error in the Google Search Console affects 4 pages already. (screenshot: https://joxi.ru/a2XYpqWuwN0JYA)

What are we doing wrong?

I found an error in the AMP admin panel. (screenshot: https://joxi.ru/82Q4dkehwlDqxm).

Humm.

Well I can see that a single blog post is successfully available as a valid AMP page: https://uvozov.ru/kak-ubirat-sneg-s-kryshi-chastnogo-doma/amp/

I can also see that https://uvozov.ru/?amp=1 returns a valid AMP page.

But https://uvozov.ru/amp/ does not, which is strange.

Nevertheless, I can see that if I add a random query string to the homepage URL then it returns a valid AMP page: https://uvozov.ru/amp/?foo

This seems to indicate a problem with your page caching. Or maybe it’s a problem with Rank Math? I seem to recall a compatibility problem there in the past. @milindmore22 may have more information.

However, the “script amp-onerror” error in the Google Search Console affects 4 pages already. (screenshot: https://joxi.ru/a2XYpqWuwN0JYA)

The AMP validator on Google Search Console will be updated by end of the week: https://github.com/ampproject/amphtml/issues/22543#issuecomment-852315041

In the meantime, my mini plugin should prevent the error from being detected: https://gist.github.com/westonruter/d13eb0175a22f83c41531e7d1a7071fd

Hello @westonruter

Do I understand correctly that now nothing depends on me and you need to wait?
Can you tell me how long it will take to return to this task?

As seen in the AMP core issue, the validator fix will be deployed by the end of the week. So there’s nothing you need to do for that.

Otherwise, there are outstanding issues with validation errors which can be seen here:

* Non-AMP: https://uvozov.ru/
* AMP but validation errors: https://uvozov.ru/amp/
* AMP and no validation errors: https://uvozov.ru/?amp=1

I’m not sure why /amp/ has validation errors but ?amp=1 does not. This is something to investigate further, as it may be a plugin conflict or an issue with your page caching plugin. @milindmore22 can assist you further debugging that.