After updating wordpress 4.6+ amp breaks

Note that WordPress 6.4.0 had an issue with cURL that broke HTTP requests. This may be what you are experiencing, and you should make sure you update to WordPress 6.4.1.

Updated. All versions of WordPress above 4.6, including 4.6.1, break amp on 2 sites. This is caused by updating WordPress. If you don’t update WordPress, then amp works.

• Twenty SeventeenThis theme has been deactivated since last site scan.

After updating WordPress, the theme suddenly became incompatible.

Hello,

I would check your CSS budget, because the AMP framework only allows 75 KB CSS on each page, so the AMP plugin adds CSS optimizations, which are sometimes exceeded by third-party plugins or themes.

If you are not sure how to find exceeding CSS budget, follow the below steps:

1) Make sure you have enabled the AMP validation tool
Go-to: Users > Profile > check the checkbox for AMP Development tool > save

2) Visit AMP page exceeding CSS budget check Admin bar for AMP option locate submenu CSS budget and click on it (screenshot)

3) Locate the source of excessive CSS (screenshot)

4) If one of the plugins adds excessive CSS find an alternative plugin from the AMP ecosystem

You can learn more about the Reader mode video below:

• This reply was modified 1 year, 4 months ago by Milind More.

OK. I understand. The problem occurs precisely when updating the WordPress core.

Hello @wishlight

Can you please share your support UUID by visiting AMP->Support so we can guide you regrading CSS budget further

This is a demo site https://td1.pp.ua/ with zero settings. Same problem. I can give any access to it.

ampwp-a379b90a-9a2e-5548-a7f2-4ab550c390da

And this is ampwp-88d3d348-aaec-52dd-8186-6ad1b3b752cf for https://cleanland.pw/. It’s already working. It is not advisable to change anything radically.

Hello @wishlight

Thanks for sending the UUUID. Elementor is not fully AMP compatible at this time. As a result, you may encounter some validation errors and some Elementor features which may not render as expected in their AMP versions due to AMP’s removal of Elementor’s custom JavaScript. You can follow this GitHub issue for future updates on Elementor compatibility.

You can also try using the AMP Enhancer plugin, which adds a layer of AMP compatibility for Elementor and several other plugins.

AMP Enhancer is installed on both sites, but only works on one. I’m talking about simple blog pages that broke after updating the WordPress core.

https://td1.pp.ua/otklyuchenie-mocheviny-na-audi-a6-c7-3-0tdi/amp/ – this is not Elementor

Hello @wishlight

As mentioned before the WP bakery and the Elementor editors heavily relied on custom javascript, AMP Framework does not allow custom javascript so the AMP plugin blocks them from creating valid AMP pages, As you know only valid AMP pages will be saved in the AMP cache and served through Search Engine results.

You have given ID’s of two sites the above reply was for first site.

I did’t recevie any validation data for above site, can you please share screenshot of CSS budget? by following process mentioned in previous reply

Hi,

Same situation here after upgrading to WP 6.4.1

After some investigation, on our website random page, CSS usage is 9%, which isn’t surprising because it doesn’t load anything.

However, checking in the validated URL, it seems like the plugin does not find the correct paths, which is predictable by looking at the URLs.

Failed to fetch:
/wp-content/themes/twentyseventeen/core/inc/compatibility/gutenberg/assets/css/uncode-gutenberg-frontend.css?ver=3.4 (HTTP 404: Not Found)
/wp-content/themes/twentyseventeen/library/css/style.css?ver=1630411711
/wp-content/themes/twentyseventeen/library/css/uncode-icons.css?ver=1630411711
/wp-content/themes/twentyseventeen/library/css/style-custom.css?ver=1630411711

Looking in our server, twentyseventeen does not have a core or library file, or perhaps your plugin adds it in order to work with the default theme (non-AMP).

As previously said, this is linked to the WordPress 6.4(.1) update, because we’ve never encountered any issue with your plugin before.

Hello @lucawal

Please create a new support topic so we can discuss you issue specifically

Hi,

Up to you, but it looks like it’s the same issue.

Hello @wishlight As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.