• Hi,

    Please could you tell me why I’m correctly logged with global API, it’s green with APO, but in the cloudflare.com backend it get this message:
    Note: The WordPress plugin was not detected on belmont-web.com.

    Check again.

    No matter what I do it’s not working

    Thanks for your help

Viewing 14 replies - 1 through 14 (of 14 total)
  • Same

    Same on groomershop.ru ??

    Response for “Check again”:

    {
      "result": {
        "id": "automatic_platform_optimization",
        "editable": true,
        "value": {
          "cf": true,
          "enabled": true,
          "wordpress": true,
          "wp_plugin": false
        },
        "modified_on": null
      },
      "success": true,
      "errors": [],
      "messages": []
    }
    • This reply was modified 4 years, 1 month ago by Mikhail Alferov. Reason: add response

    Resolved!

    I use filter in functions.php file to hide WP version on RSS/Feed-page:

    add_filter('the_generator', '__return_empty_string');

    I comment this string of code.

    // add_filter('the_generator', '__return_empty_string');

    Then edit (update) main (front) page of site.

    Try “Check again” in CF Backend and got: “WordPress plugin successfully detected on groomershop.ru.”;

    Probably, the best way to get a green check mark is CF Backend for APO is:

    • Delete or comment the ‘the_generator’ filter code (if you use this filter) in functions.php.
    • Edit or update front page.
    • Disable APO in the WordPress backend.
    • Enable APO in the WordPress backend.
    • Press “Check again” in CF Backend: tab Speed – Optimization – Automatic Platform Optimization for WordPress

    I have the same issue, and I don’t use this ‘the_generator’ filter…

    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.

    I use genesis theme on mykalvi.com , the issue is not resolved yet. I’ve tried turning off APO in WordPress and enabling it on Cloudflare.

    Any work around to resolve this would be appreciated.

    Thanks.

    v3.8.3 of the plugin should be released soon and should resolve some of the issues with this. See this PR for more info: https://github.com/cloudflare/Cloudflare-WordPress/pull/301

    If after updating to v3.8.3 you still are having issues, please let us know.

    HI @ggalow I have v 3.8.3 of the plugin and still have the issue. to be clear, plugin is installed and activated, and switched on in CF, but there’s a note against the item: Note: The WordPress plugin was not detected on labourdonnerie.com. Check again.

    additionally, i’m getting a ‘forbidden’ message in wp admin on the plugin settings page: https://tinyurl.com/y68fp9fq

    • This reply was modified 4 years, 1 month ago by pluggyboy.
    • This reply was modified 4 years, 1 month ago by pluggyboy. Reason: added screenshot of wp-admin
    Thread Starter TedSwiss

    (@tedswiss)

    No improvement by my side either with 3.8.3…You got us used to better!

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

    Thread Starter TedSwiss

    (@tedswiss)

    Hi @ggalow, this is a paid plugin so it would be normal to have a working plugin or at least tell us what’s wrong to solve this problem ?!

    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

    jondaley

    (@jondaley)

    3.8.6 installed here. Same error, though I also get a blank page on the cloudflare page within wordpress (no errors to the log, HTTP 200 returned).

    Different problem, or same thing?

    The “check again” button sends a request to / on www and non-www versions of the site, seems like a check to /wp-admin or login, or a plugin-specific page would make more sense.

    UPDATE: it doesn’t work when W3 Total Cache is installed. I don’t know which is better, for my site, I can’t use any page caching, because every page is dynamic, and all users are logged in, so I’m guessing that I’m better off using Total Cache for its object cache, etc. I have already made custom page rules on the cloudflare to cache whatever I can.

    • This reply was modified 4 years ago by jondaley.
Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Note: The WordPress plugin was not detected’ is closed to new replies.