[Support request] Amp Errors

Home Forums Support [Support request] Amp Errors

Home Forums Support Amp Errors

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #817029
    Ed

    I am using WordPress 5.0.3 with GeneratePress 2.2.2 and GP Premium 1.7.7 with a GP Child Theme. I have also installed the official WordPress AMP plugin 1.0.2 and am seeing a number of errors associated with both GeneratePress and GP Premium. These include

    Any idea what is causing these and how I might resolve them?

    Thanks

    GeneratePress 2.2.2
    GP Premium 1.7.7
    #817093
    Tom
    Lead Developer
    Lead Developer

    Hi there,

    AMP wants minimal CSS and no javascript, which GeneratePress doesn’t support yet.

    We’re working on an AMP plugin that will integrate GP with the official AMP plugin. Hoping to have it ready soon.

    #817169
    Dean

    Hi Tom … the AMP project would be a perfect type of an example regarding blog content for GP customers like I mentioned the other day here;

    https://generatepress.com/forums/topic/receive-generatepress-news-and-updates/#post-815930

    … because, it’s my understanding that Google is trying to throw some of their weight behind this AMP technology standard, and may play a very important role in search engine ranking in the not too distant future … so for us GP customers, being informed on what’s coming down the pike with things like GP AMP technology would help us better prepare & steward our businesses better for important technological changes … plus; when non-GP customers see you professionally navigating these highly important changes in a strategic manner via your blog – it could win you a bunch of new customers too.

    #817199
    Ed

    Thanks Tom. The AMP plugin is stripping out what it doesn’t like. But it would still be nice not to have it generating errors for every page and post. And, FWIW, quite a few other plugins are doing the same thing, including JetPack.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.