Subdomain / Page Rules / Cache Rules

Hello,

Here are some answers for you questions:

1. The Global API token is used only for accessing Cloudflare services for the selected domain on the plugin dashboard. When you press Purge Cache, we send a request to Cloudflare to purge the cache for that domain.
2. Inside the Rules tab, we set only the Cache Rules marked with [DO NOT EDIT] WP Super Page Cache Plugin rules for. Setting up the rules manually is for cases when you have something complex that our plugin does not cover.
3. Just to confirm — was the plugin only used in the staging environment, and were the other two rules manually added on the live site? If you want these rules to be applied automatically, you’ll need to install the plugin on the live site as well. However, be sure to delete the manually created rules if you plan to replace them with ones generated by the plugin, to avoid any potential conflicts.

Thank you!

Reading your reply, it sounds like we should also de-activate the manually created Cache Rule for using the “Remove Cache Buster Query Parameter” feature that we created per the guidelines on this page

Yes. That guide was created before we added the support for Cache Rules in Rules. Old versions of the plugin were using this feature: https://developers.cloudflare.com/cache/how-to/cache-rules/examples/cache-everything/

When looking at the header of the staging site, it looks like both Cloudflare APO and Super Page Cache are active at the same time on the staging site. How can this be avoided?

Are both of them installed on staging? Our plugin only creates the Cache Rule (prefixed with [DO NOT EDIT] WP Super Page Cache Plugin). If you were using Cloudflare APO before on staging, maybe some settings are still in place.