edkoon

Thought this topic was about wordpress amp errors, or did I miss something?

Yep.. I’m seeing 1/4 of my pages amp indexed this morning in gwt.

Another tidbit, if pasting your analytics code in Yoast Glue / Analytics area, that Script will toss up an error too. I use a CloudFlare app to insert my analytics code, but disabling cf apps drops tracking on amp pages. Hopefully JetPack stats will show any amp page activity.

Oh well, another sunny soon to be HOT day in paradise. ??

I managed to fix my amp validation errors. Most were CloudFlare related but an amp specific cloudflare page rule was used to turn off necessary services to fix script errors.

This post has a screen shot of the page rule needed to disable cloudflare services causing amp errors. https://www.docsplace.org/3657/03/amp-errors-and-cloudflare-incompatibility/

The plugin Clean Talk Anti-spam was temporarily deactivated but it’s developer Roman Safronov is working on a fix as i type this.

It does not make sense that Google is denying scripts. Not only CloudFlare which loads it’s resources via script command, and an anti-spam plugin (clean-talk) i use has an excellent firewall that blocks flagged ips before the page loads. Unfortunately it’s executed by a script command too.

In principal amp looks good – but Google is being too restrictive.

Oh well, another sunny day in paradise ??

From CloudFlare support:

I’ve been discussing AMP with the engineering department here at CloudFlare. In order to get AMP to work properly with your website, you will need to disable ALL performance features in the CloudFlare dashboard (Mirage, Polish, Email Obfuscation, Rocket Loader, etc.). At this time AMP breaks most of the CloudFlare features offered through the dashboard.

We are communicating with Google on this issue to figure out the best course of action. In the meantime you will need to choose to either disable AMP and keep the CloudFlare features active or disable all CloudFlare features and leave AMP active.

Google might end up dumping AMP like they did Authorship. We jump through hoops to get into compliance then wham, they slam the door shut.. LOL!

Oh well.. Just another day in paradise..

Gooma2, thanks for your reply.

I fired off a support question to CloudFlare since their main script is not allowed by amp. Hopefully they are working on a fix. As a hobbyist i cant afford to hire a developer to get in compliance.

Regards, Ed

Is anyone monitoring this support forum? I have identified two errors that are specific to CloudFlare and have corrected them. But other errors persist.

For anyone using CloudFlare it is required to disable url protocol rewriting in the CF plugin. Also use a page rule to disable CF RocketLoader on amp pages. More info is here: https://wpressurecooker.com/how-to-fix-cloudflare-and-amp-invalid-attribute-values/

Webmaster tools is identifying a url error i believe is in this AMP plugin: Invalid attribute values: src=//cdn.ampproject.org/v0/amp-anim-0.1.js

Regards, Ed

I dove into this last weekend. Installed this AMP plugin, then later installed Yoast Glue plugin. Glue is supposed to add the stripped out meta and og tags back. Glue also adds an Icon (32×32) as defined in Yoast SEO > AMP design tab.

Webmaster tools is showing a slew of amp specific errors, (incorrectly nested tags, required tag missing, invalid attribute value, prohibited attribute, and unknown syntax error) but when testing an amp specific post page in the dev testing tool, all i get is a featured image size warning. Deactivating Yoast Glue brings up a missing logo error. The logo is defined in Yoast SEO > General tab under company info, and is the correct size 60×600 as required.

Dang if i can figure this out. https://developers.google.com/structured-data/testing-tool?url=https%253A%252F%252Fwww.docsplace.org%252F2049%252F01%252Fwordpress-protocol-relative-urls%252Famp%252F

Any suggestions?

I’m seeing an og description but no meta description tag. Have Yoast SEO & Glue activated along with AMP plugin.

Also getting a slew of AMP errors in webmaster tools act on two sites. AMP is something new with lots of kinks to be ironed out, kind of like Authorship when it began. (Sigh!)

You can use Google’s testing tool to get more info on possible page errors. Mine check OK but still show errors in webmaster tools.
https://developers.google.com/structured-data/testing-tool/

Also this mod works great with this plugin. Make your WordPress site use protocol relative urls.

Quite useful for making a post or page accessible by standard http protocol. I use it for my webcams that do not support tls encryption.

I use this snippet in my wp-config file to force ssl admin.

define('FORCE_SSL_ADMIN', true);
if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https')
       $_SERVER['HTTPS']='on';

Otto, Well then something is mucked up when viewing emoji’s in Google Chrome browser. Using the ?? shortcode produces a “gray x on a black background” is that the emoji equivalent of :wink:? LOL!

Yea standards win all the time. But many older articles might not look good with the emoji default image. Oh well thanks for your plugin to enable the default old smilies.

As usual just my two cents worth as usual ??

I really don’t care about emoji either way. But i am concerned that to use default WordPress smileys another plugin must be used.

Make emoji a toggle on / off. And if emoji is on don’t overwrite the default smilie shortcodes.

Seems simple enough to me.

Hey Samuel Wood, your plugin works like a charm. My original similes are back. Thanks!