Great Plugin No doubt

Thanks for the review.

1. support for onesignal push notifications. (like amp plugin by kalidi)

We’ve been collaborating with OneSignal directly to make their first-party plugin AMP-compatible: https://github.com/OneSignal/OneSignal-Website-SDK/issues/615

(It’s been a few months since an update has been posted.)

2. adsense page ads, one has to compromise on his ads income.

For AdSense, you can use the Google Site Kit plugin: https://sitekit.withgoogle.com/

3. is there a way i can use other theme for AMP pagesin transistion mode. i am using other AMP plugin with ?amp in end on my other websites which i am thinking to migrate.

This is something we are working on for v1.6. It will be Reader mode, but you’ll be able to select another theme to use for AMP pages. Please watch for the 1.6-beta1 release this week: https://github.com/ampproject/amp-wp/releases

4. Native support for disqus , vuukle comment plugin

I recommend reaching out to the plugin author to make their plugin AMP-compatible if not already.

I was testing The Latest Beta Version of the Plugin, it is havibg everything that i was wishing.

some Points i want to bring to your notice:-

1. Previously in reader mode- buttons and some Blocks from other plugins were still appearing on AMPpages but Now they are not- (Previously Divi blocks were compatible with reader Mode but with new AMP plugin they are not)
2.Liveblog plgin is not supported now, but it was with old reader mode theme

Link to check

@lochanraj Thanks for the feedback and for testing.

1. Previously in reader mode- buttons and some Blocks from other plugins were still appearing on AMPpages but Now they are not- (Previously Divi blocks were compatible with reader Mode but with new AMP plugin they are not)

Which blocks specifically were not working? Which blocks are they on the non-AMP version? If you switch the Reader theme from Twenty Twenty to “AMP Legacy”?do they show up again?

2.Liveblog plgin is not supported now, but it was with old reader mode theme

Are you referring to the Liveblog plugin from Automattic? Where is this seen on your site? Again, does it work on AMP pages if you switch to the Legacy theme instead of another Reader theme?

It would probably be best to provide the details in a new bug report on GitHub: https://github.com/ampproject/amp-wp/issues/new?template=bug_report.md

The Liveblog plugin is working as expected for me when I selected Twenty Twenty as the Reader theme. The liveblog entries are rendered on the AMP page. It’s just that the form to create new entries is not displayed on the ANP page. But this is no different than today, even on the Legacy theme for Reader mode.

The Link which i prvided has blog block from elegant theme it was always occuring when reader mode is on even now when i moved back to it from Twenty twenty theme. I can also give some other links when different blocks were appering in reader mode but now not. you can check with AMP verson and without AMP verson.

https://latesttelly.com/the-kapil-sharma-show-is-back-after-lockdown-but-no-stage-audiences/

https://latesttelly.com/rising-star-india-how-to-vote-live-color-tv-app-tutorials/?amp

this one can give you fair idea on Buttons which i used from divi builder, it is still appearing when i go back to reader mode( as link)

If you switch back to the “AMP Legacy” theme then does the issue go away?

Also, is the issue also happening in Transitional template mode? If so, it may actually be an issue with Divi and how it integrates with the AMP plugin, and not an issue with the AMP plugin itself.

Otherwise, please open an issue on GitHub with screenshots and steps for how we can reproduce the issue: https://github.com/ampproject/amp-wp/issues/new?template=bug_report.md

We tested with Divi and found that it is fundamentally incompatible with AMP. It is adding a massive amount of CSS to the page (close to 1MB) whereas AMP limits the total to 75KB. The AMP plugin’s CSS tree shaker is able usually reduce the included CSS quite a bit, but 1MB is too much to successfully bring the CSS under the budget.

Additionally, Divi blocks appear to have some effect where they are initially hidden and then reveal themselves with some JavaScript-based fade-in effect when they scroll into view. On such a Divi-build page, if you turn off JavaScript you’ll see the same behavior: all of the blocks appear hidden. The AMP plugin strips out custom JS, so AMP pages in essence behave as non-AMP pages with JavaScript turned off in the browser.

So, you’ll need to disable AMP for pages that you’ve built with Divi. When editing a post in the normal WordPress editor, you can disable AMP by toggling off “Enable AMP” in the document settings.

Okay this clears my doubts. Appreciate your great support and Help. I am running your beta plugin on 3 of My sites. No Major issues i found. Also saw one good chage previously i had several warning for Image sizes for AMP pages in search console but they are gone now and i checked their validity as well. is it because i am using 2020 template or any changes in plugin?

That sounds about right. When selecting a Reader theme you’ll generally get better function and visual parity between AMP and non-AMP.

If anything else comes up, please open a new support topic so we can better assist you.

Thanks again for testing the beta!