• Resolved gooma2

    (@gooma2)


    Hi,

    I saw that in the installation instructions, you mention to use Native or Paired mode, but when I’ve tried each, my site is broken. Once I go back to Classic mode all is well again and with all my AMP pages.

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Hi @gooma2,
    Thanks for letting us know about this. It must be frustrating.

    You mentioned that the site is broken in Native and Paired mode.

    Could you please elaborate on this? Is there a PHP error, or does your site not display or work as expected?

    It looks like it’s running Classic mode now, understandably ??

    Thanks, @gooma2

    Plugin Author Weston Ruter

    (@westonruter)

    If the style of your site looks broken in the new Native/Paired modes, then it is likely that your theme has too much CSS for the plugin to reduce to 50KB.

    Thread Starter gooma2

    (@gooma2)

    I’ve also forwarded this to the developer of the site, but as many people use their themes you may be hearing this alot.

    The site itself is broken down like one of those old html ones from the 1980’s.

    I too have this issue but Google is treating it very harshly. Switching from Classic to Paired results in Google removing the page from its index. Switching it back results in re-indexing in a few weeks.

    Be aware that his is the kiss of death for any type of site depending on its AMP pages being found.

    Google Search Console started reporting AMP issues with over 200 posts using Hueman Theme.

    Specifically the error is:

    Linked AMP version is invalid
    It won’t appear in Google Search results. Learn more

    Error started appearing 1/28 now affecting 215 posts.

    # SITE_URL: https://thumbwind.com
    # HOME_URL: https://thumbwind.com
    # IS MULTISITE : No

    # THEME | VERSION : Hueman Pro | v1.1.10
    # WP VERSION : 5.0.3
    # PERMALINK STRUCTURE : /%year%/%monthnum%/%day%/%postname%/
    # 16 ACTIVE PLUGINS :
    – Ads.txt Manager (version 1.1)
    – Akismet Anti-Spam (version 4.1.1)
    – AMP (version 1.0.2)
    – Easy Add Thumbnail (version 1.1.1)
    – Forty Four – 404 Plugin for WordPress (version 1.4)
    – Glue for Yoast SEO & AMP (version 0.4.3)
    – Jetpack by WordPress.com (version 6.9)
    – Media File Renamer Auto (version 4.5.2)
    – Nimble Page Builder (version 1.4.7)
    – Regenerate Thumbnails (version 3.1.0)
    – Revive Old Posts (version 8.1.8)
    – WooCommerce (version 3.5.4)
    – WooCommerce Services (version 1.18.0)
    – WooCommerce Stripe Gateway (version 4.1.14)
    – WP Ultimate Exporter (version 1.4.3)
    – Yoast SEO Premium (version 9.5)

    # PHP Version: 7.0.33
    # MySQL Version: 5.5.5-10.2.15-MariaDB-log
    # Web Server Info: nginx

    # WordPress Memory Limit: 256MB
    # PHP Memory Limit: 256M
    # PHP Upload Max Size: 2047M
    # PHP Post Max Size: 2047M
    # PHP Upload Max Filesize:2047M
    # PHP Time Limit: 1200
    # PHP Max Input Vars: 6144
    # PHP Arg Separator: &
    # PHP Allow URL File Open:Yes
    # WP_DEBUG: Disabled

    # Show On Front: posts
    # Page On Front: (#0)
    # Page For Posts: (#0)

    Plugin Author Pascal Birchler

    (@swissspidy)

    @thumbwind You seem to have lots of plugins installed and lots of interactive functionality on your site (dropdown menus, newsletter popups, lazy-loading images, related posts carousel, Jetpack comments, etc.). That means lots of potential conflict areas for AMP compatibility.

    I suggest you to switch over to Paired mode and then use the validator in the plugin settings as well as the validator at https://validator.ampproject.org/ to check for specific error messages. Especially the validator on the plugin’s settings screen is useful as it tells you the plugin/theme most likely causing the issues. If you stumble upon such a plugin, you can contact its developer to see if they can make their code AMP-compatible.

    Sure…Be Aware that all plug-ins have been verified as compatible with my version of WP.

    If I make the switch to Paired with AMP then unless something has changed Google will de index my pages.

    I’ve utilized the AMP validator on this URL still in classic:

    https://thumbwind.com/2019/02/09/consumers-energy-wind-farms/amp

    And it passes fine Could it be the Hueman theme I’m using? Or Yoast?

    • This reply was modified 5 years, 9 months ago by thumbwind.
    • This reply was modified 5 years, 9 months ago by thumbwind.
    Plugin Author Pascal Birchler

    (@swissspidy)

    It could be anything. That’s why I recommend you to use the AMP validator in the plugin’s menu in WordPress admin under AMP -> Validated URLs.

    Now I turned on Paired an got the following error from wordpress.com

    Paired mode activated! However, there was an error when checking the AMP validity for your site. Internal Server Error

    Now I see the following errors…which Google did too!!

    The mandatory tag ‘head > style[amp-boilerplate]’ is missing or incorrect. MANDATORY_AMP_TAG_MISSING_OR_INCORRECT
    line 378, column 234

    The mandatory tag ‘noscript > style[amp-boilerplate]’ is missing or incorrect. MANDATORY_AMP_TAG_MISSING_OR_INCORRECT
    line 378, column 234

    The mandatory tag ‘noscript enclosure for boilerplate’ is missing or incorrect. MANDATORY_AMP_TAG_MISSING_OR_INCORRECT
    line 378, column 234

    Plugin Author Weston Ruter

    (@westonruter)

    Note the “Internal Server Error”. Please look at your PHP error log for what is going on.

    Not sure of where to find the PHP (or any) error logs on a premium wordpress.com account.

    Plugin Author Pascal Birchler

    (@swissspidy)

    You should be able to contact their support for that.

    As for the other error messages, it’s hard for us to help you there since the site is currently in Classic mode so we can’t inspect it. Do you perhaps have a staging site we could access?

    Do these errors still happen when temporarily disabling all other plugins and using a different theme? This way we could try to nail this down.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Native or Paired Mode breaks site’ is closed to new replies.