weeblrAMP comments and plugins

Comments

weeblrAMP introduces the ability for your visitors to comment on your AMP pages. While still complying with all commenting permissions you set in your WordPress admin, AMP pages can now both display and receives comments. This will work both when the AMP page is shown on your own site, or when displayed by Google from its AMP cache.

We currently provide support for 2 commenting systems:

• WordPress native comments
• Disqus

Leaving comments on AMP pages, whether with WordPress native commenting system or with Disqus, is only available in the regular edition of weeblrAMP. On the Community Edition, WordPress comments will be displayed only, and Disqus is not available.

WordPress native comments

The simplest way to go. It's enabled by default, so you basically do not have anything to do to enable commenting on your AMP pages if you use WordPress native comments.

Disqus

Disqus commenting system is fairly popular amongst WordPress users, but it also has the advantage of providing an AMP implementation, that allowed us to provide what we called a "hands-free" Disqus experience.

As Disqus is entirely javascript-based, they had to build specific AMP support, but they did so and it's been possible to implement Disqus commenting on AMP pages for a little while. However, this was pretty complicated, and required the following:

• insert some PHP code on your (AMP) theme to set Disqus parameters (namely the current page ID)
• create a small "relay" HTML file, containing some javascript and your Disqus shortname
• host this relay file from a separate domain than your site and over HTTPS

All 3 requirements made it rather complex to implement, including the need for a separate domain or subdomain.

Now we have made it simpler: all you have to do to add transparent Disqus commenting to your site is:

1. Enter your Disqus shortname
2. Click the Use Disqus AMP file from WeeblrPress button
3. Save settings

Assuming you have an active subscription with us, clicking that button creates a relay file for you, and hosts it on one of our domains, over HTTPS, and actually over a worldwide CDN, for speedy response.

You are not tied to us in any way however. Should you not want to use this service from us, you can host the Disqus relay file on your own server (still on a separate domain and over HTTPS). For your convenience, we create the Disqus relay file for you and you only need to click the Download Disqus file to get a suitable file (make sure to fill-in your Disqus shortname first). You can then copy it where you need and enter the corresponding URL in the Disqus endpoint input field.

When setting up Disqus, if Trusted domains are used, one should add the domain involved, but also the ampproject.org domain (or any other AMP cache you use), used when pages are viewed from the AMP cache

Plugins management

On the Comments and plugins configuration tab, you will also find a list of the plugins installed on your site. Many of them will not be needed on AMP pages, because of the AMP requirements, but weeblrAMP will normally simply not use them. However, some plugins may still perform what they do on AMP pages, and break them in the process. If this happens, just check their names in the list, and those plugins will be disabled when displaying an AMP page.

Theme management

Very much in the same as the plugins, it might be useful to entirely disable your theme when displaying an AMP page. This is not normally needed, but some themes may inject content into all pages, and this content will make your AMP pages invalid. If you experience such behavior, disable your theme on AMP pages using the corresponding setting:

Disabling the theme will also disable all plugins that are part of your theme. For instance, when using the Divi page builder as part of a theme, disabling the theme will also disable the page builder, which will prevent proper rendering and is therefore not recommended.
This will not happen if Divi is installed as a standalone plugin, separate from your theme.

Content processing

You can also disable processing for filters and shortcodes, or only a specific list of shortcodes: