I am sick and tired

  • I would give 2.5 stars for the features, as they actually work in the real world.

    I have to give 1, because it is the 3rd time everything broke after an update (I am with this plugin since it was just a “baby” ). I get the feeling that the users’ voice cannot be heard by the ( two? ) companies behind this plugin.

    For the coders interested, this time I got all my AMP pages invalidated and out of google index ?? I believe the problem started past version 1.1.0 but I cannot pinpoint the exact version. The thing is that the plugin timeouts when trying to validate page/ fix erros and the fix (suggested for 0.8 version) doesn’t help either.

    For smaller projects I tried in the pasts AMP for WP and Better AMP, I guess I must look this way for our main project too.

    PS I used to believe, it’s from Automattic, of course it IS GOOD.

    • This topic was modified 5 years, 9 months ago by aimarv.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    @aimarv what mode of the plugin were you trying? Transitional/Native? We’re the timeouts happening when saving a post?

    it is the 3rd time everything broke after an update

    What specifically broke?

    I get the feeling that the users’ voice cannot be heard by the ( two? ) companies behind this plugin.

    Why do you get that feeling? You can see the support forums are actively responded to. Issues in GitHub are promptly resolved.

    I’ve been using this plugin since a baby too and the latest version (1.1.x) is much easier to work with, I used to have to develop all the templates to be specific for amp (i used a folder in my theme called amp-templates) this was a nightmare to maintain but now i work within the same workflow for the rest of the site and no more templates to track all the time. I find that the menu is always broken (no surprise really as theres 100’s of different ways to do a menu) but a simple snippet in the functions file fixes this, all i had to do was grab the id of the container and button and find the class that the site usually uses when the menu is opened/closed and voila. All other content is dealt with with no or very little effort.

    Between the use of the ‘test if page is amp and run this code otherwise that code’ and the menu fix you should be able to fix any issue i can think of. There are of course uses that are not what is normally expected but it is very easy to fix these by adding an amp script developed for this task (i’ve not had to since upgrading to 1.1.x but had a few i used in 0.7.2)

    I’ve also used a few other AMP plugins but this one is by far the easiest most time saving and best supported of any AMP plugin I’ve tried

    I’d highly suggest looking over this forum at similar issues you are having.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘I am sick and tired’ is closed to new replies.