Viewing 11 replies - 1 through 11 (of 11 total)
  • @gbengard thanks for your topic.

    Are you currently using an AMP-compatible theme (and plugins)?

    If not, using the plugin in transitional mode could lead to some of these visual discrepancies since the plugin will limit CSS (to 75KB) and remove invalid markup (like custom JavaScript) on AMP pages adhere to the AMP Specification.

    I see a few references to the Newspaper theme in your source code which leverages its mobile theme to generate its own AMP templates. You may want to reach out to their support team to ensure it is configured properly on your site.

    Thread Starter gbengard

    (@gbengard)

    Thank you for your response, @reneesoffice

    The AMP pages were working fine before installing the Pagespeed ninja plugin. The pages are working fine on desktop but the amp pages are not.

    The problem is with the plugin and not the theme.

    Also, I have uninstalled the plugin but the error still persists.

    @gbengard thanks for the additional information.

    Just to confirm: after uninstalling the PageSpeed Ninja plugin the issue still persists?

    Thread Starter gbengard

    (@gbengard)

    Yes

    Are you able to to safely switch to a default theme to see if the issue occurs there?

    Thread Starter gbengard

    (@gbengard)

    Is there a way I can purge AMP cache?

    Plugin Author Weston Ruter

    (@westonruter)

    I’m not seeing any issue now at https://www.techidence.com/?amp

    Any page caching you have must have expired so the issue is no longer showing up.

    Thread Starter gbengard

    (@gbengard)

    Thank you, @westonruter

    Unfortunately, I can still see same issue at my end.

    Plugin Author Weston Ruter

    (@westonruter)

    I’m seeing two different pages being generated based on the user agent. If I request https://www.techidence.com/?amp with a Desktop user agent, I see:

    But with a mobile user agent, I see:

    Notice the error message appearing in the version served the mobile user agent.

    In the source code, there are a couple error messages:

    • Error: <strong class=”td-wp-booster-title”>wp_booster error:<br>td_api_base::mark_used_on_page : a component with the ID: td_style is not set.<br>/var/www/wptbox/wp-content/themes/Newspaper/includes/wp_booster/td_api.php (rara-error)
    • Error: <strong class=”td-wp-booster-title”>wp_booster error:<br>Missing parameter: ‘file'<br>/var/www/wptbox/wp-content/themes/Newspaper/includes/wp_booster/td_autoload_classes.php (rara-error)

    What is this wp_booster?

    Lastly, I’m also seeing in the footer:

    <script type="text/javascript" async="" src="//g.ezoic.net/ezosuigeneris.js"></script>

    Ezoic is not compatible with the AMP plugin which you can see from https://www.ezoic.com/compatibility/

    Do the issues go away if you turn off Ezoic?

    Thread Starter gbengard

    (@gbengard)

    Thanks, @westonruter for this.

    The WP-booster is part of the newspaper theme, I don’t know what it is?

    I’ve disabled the Ezoic plugin, only using Ezoic CDN.

    Plugin Author Weston Ruter

    (@westonruter)

    I suggest reaching out to tagDiv support for assistance with Newspaper and AMP-compatibility.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘AMP Pages are broken’ is closed to new replies.