dbevort

Update: Please ignore this post.

I found out that is was Cloudflare who is the culprit here, not Super Cache, that is incompatible with the AMP plugin. When you have Cloudflare do a whole-page cache, the redirect is baked into the page if opened previously in desktop mode. We’re close to just dumping AMP, nothing but trouble.

Thanks for quick answers.

In our case our main site (non-WP) is set to “cache everything”, and we made a page rule for the WP “/blog” site for “standard” cashing. The APO feature doesn’t seem to make any difference, no cache hits. Does the page rule interfere with the APO function? What is the right setup?

Here is the header for one of the blog pages:

HTTP/2
200
date: Fri, 09 Oct 2020 13:23:22 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d3b94eae144a300f335033c133fb2e2da1602249801; expires=Sun, 08-Nov-20 13:23:21 GMT; path=/; domain=.&&&&&.com; HttpOnly; SameSite=Lax
cf-ray: 5df86a6b9edbdfd3-FRA
link: <https://www.$$$$$.com/blog/wp-json/&gt;; rel=”https://api.w.org/&#8221;, <https://www.$$$$$.com/blog/wp-json/wp/v2/posts/13853&gt;; rel=”alternate”; type=”application/json”, <https://www.$$$$$.com/blog/?p=13853&gt;; rel=shortlink
vary: Accept-Encoding
cf-cache-status: DYNAMIC
cf-edge-cache: cache,platform=wordpress
cf-request-id: 05af20d7430000dfd387a12200000001
expect-ct: max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct&#8221;
x-via: speedwp/origin,bypass
server: cloudflare
alt-svc: h3-27=”:443″; ma=86400, h3-28=”:443″; ma=86400, h3-29=”:443″; ma=86400

Same here, with 3.8.3 installed, still doesn’t detect. FYI, WP runs our /blog site, if that makes any difference.

Ok, it solved it so far that I could do the indexing after a reset, without errors, in troubleshooting mode. However, the error still persists when troubleshooting is turned off. I have not had time to figured out what conflict that causes the the plug-in to fail.

Thanks Priscilla,

Starting the plug-in in WP troubleshooting mode with all other plug-ins deactivated, made it possible to do the update (“Start processing..”).

Thanks!

• This reply was modified 4 years, 1 month ago by dbevort.

Same here. In our case our /blog is a WP site having the plug-in installed. The plug-in seems to work fine and be connected to CF, from inside WP.