net

Still haven’t tested it in the production.

When comparing “Edge caching with plugin” and “Edge caching without plugin” section in the URL above, seeing the following difference:

• With plugin have “30 seconds or faster cache invalidation” instead of “Cache invalidation may take up to 30 minutes.”
• With plugin have “Bypass HTML caching for logged in users”. I suppose your plugin handles this already.
• With plugin have “Decrease load on origin servers. If a request is fetched from Cloudflare CDN Cache we skip the request to the origin server.” instead of “No decreased load on origin servers. If a request is fetched from Cloudflare CDN Cache we still require an origin response to apply cache invalidation logic.”

Didn’t mean to fake it just for fun. I thought Cloudflare uses it as a signal for certain APO functionality.

https://blog.cloudflare.com/building-automatic-platform-optimization-for-wordpress-using-cloudflare-workers/#edge-caching-with-plugin

• This reply was modified 4 weeks, 1 day ago by net.

Quite interesting. How about querying Cloudflare and if APO is enabled add header('cf-edge-cache: cache,platform=wordpress'); to make use of it, since we already have it in our plan? Does that make any sense?

That was really fast Shawn, many thanks ??

It’s?hard?to?believe?that you?can have complete APO?functionality?without?an?APO subscription?

Unlike Cloudflare APO, using a “cache everything” page rule doesn’t provide you with a global replication layer that automatically copies HTML to data centers around the world. With a “cache everything” page rule configured, a request to your site from Tokyo will only result in a page being cached in Tokyo. With APO, a request to your site from Tokyo will trigger Cloudflare to store the HTML page in Workers KV, which automatically replicates across Cloudflare’s global network within 60 seconds. To put it simply, APO effectively decentralizes your site’s origin by mirroring your site across Cloudflare’s global edge network.

Ref: https://brianli.com/cloudflare-apo-for-wordpress-misconceptions/

You?could?check?if?the?cron?job?is?disabled,?display?a?warning?about?it?in?the?settings,?and?deactivate?the?purge?on?cron?mechanism.

https://speedvitals.com/ttfb-test specifically mentions “Served by Cloudflare APO” when used on the website and this is a separate product: https://www.cloudflare.com/application-services/products/automatic-platform-optimization/

Need to use official plugin https://www.ads-software.com/plugins/cloudflare/ for it.

Does?your?plugin?support?APO?as?well?

Thanks for getting back to me.

Still experiencing?this issue.

Editors see “Content Aware” menu item with no subitems inside. It just links to /wp-admin/admin.php?billing_cycle=annual&page=wpcas-pricing

Tried changing add_menu_page parameter from $post_type_object->cap->edit_poststo 'manage_options', but it’s the same: https://github.com/intoxstudio/content-aware-sidebars/blob/0ad38180a2a3046d007028de0909466b0849fc60/admin/sidebar-overview.php#L45

Any workaround?

How about:

1) Querying some Ad Inserter global variable or

2) Calling some Ad Inserter function or

3) Using some filter to catch and save the info globally if ad position number 1 is disabled?

I confirm the issue has been fixed in 2.3.2. Many thanks @debaat!

Found that after running the redis-cli flushall command, identical errors occur.

As noticed in the other topic, commenting out wp_cache_flush_group( 'orphaned_counts' ) “fixes” things.

Does this actually mean that maxmemory 1536mb we are using is too high?

Adding media works properly in 2.3.1, but still seeing Uncaught SyntaxError: Unexpected token '&' error when accessing /wp-admin/edit.php

@amboutwe @tillkruess After commenting out wp_cache_flush_group( 'orphaned_counts' ) in the latest version 22.7, the issue is gone.

BTW, noticed that orphaned_counts is not present anywhere else in the code.

Of course, please let me know what to do.