Static home page with Polylang

Please share a screenshot of the AMP plugin’s settings screen. Are you in Transitional mode or Reader mode?

@westonruter they are the same – Reader.
https://prnt.sc/po6y0w

OK, this has only been tested in Standard/Transitional mode. Reader mode support would likely come as part of https://github.com/ampproject/amp-wp/issues/2202

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

@westonruter thanks, I’ll wait for an update. Keep in touch.
Thanks.

p.s. I’m right that Standard and Transitional modes are for AMP-first websites only?
It could be useful for news websites etc?

I mean eCommerce, corporate websites should use reader mode, right?
Just to add AMP support to some pages for Google.

Standard mode is our recommendation for all sites that have compatible themes and plugins. Transitional mode is the next-best recommendation, when your themes/plugins are mostly compatible but you need some invalid AMP markup for desktop visitors. We only recommend Reader mode when your site’s themes/plugins don’t work Standard/Transitional modes.

So Standard and Transitional modes are applicable to any type of site.

That being said, the WordPress ecosystem for e-commerce is not very AMP-compatible yet. Nevertheless, you could still use AMP in Standard/Transitional modes but you just need to turn off AMP for the product post type and cart pages.

@westonruter but if we don’t want to go fully on AMP.
It says that all pages will return AMP in Standard/Transitional mode and AMP will be canonical.

@nikitasp I suppose that description is somewhat misleading. It should say that every URL is available to be served as AMP. By default in Standard and Transitional mode, every URL is available as AMP. But you can select a subset of your site to be AMP by unchecking the below checkbox: “Serve all templates as AMP regardless of what is being queried.” You can then just select the “Singular” template if you only want AMP for single posts and pages, just like Reader mode only supports.

@nikitasp thanks for information.
But Standard mode move all website to AMP (no matter if the checkbox Serve all templates as AMP regardless of what is being queried. is checked), I’ve checked it right now.

Transitional works with 2 versions, but AMP version seems to not working with our stylesheet file (style.css). Maybe because of SVG file in it.

Anyway we have 153,3kb style.css file size, so we should use reader mode to replace unnecessary functions and styles. Am I right?

Thanks.

Standard mode and Transitional mode will make all templates available in AMP, but you can control which templates are served as AMP by unchecking that checkbox.

But yes, if your theme is not compatible (as it seems since you have that large stylesheet) then Reader mode is the best option for you now.

@westonruter hi there!

Sorry for being annoying, but shall I wait for the solution?
There was a lot updates already, but seems the solution was not pushed.

Thanks.

The fix for Standard/Transitional mode have been pushed. The fix for Reader mode would likely come as part of https://github.com/ampproject/amp-wp/issues/2202 so you can follow that issue for updates.

@westonruter hi!

Using the link I can see that the issue is closed, is that right?
But the issue is still there.

Maybe I should do something or this is some misunderstanding?
Thanks.

The fix for Standard/Transitional mode is fixed. If you are using Reader mode, then it’s like the issue remains.

@nikitasp Please share a screenshot of your Polylang settings.

It turns out there is a compatibility problem between AMP and Polylang here. I’ve identified the issue and opened a pull request in Polylang to fix: https://github.com/polylang/polylang/pull/425

You can try applying the patch there to your site to confirm the fix. If you can report your testing results on the pull request that will assist with getting it merged and into the next release of Polylang, I presume.