开发者 | blizhost |
---|---|
更新时间 | 2024年3月10日 07:37 |
PHP版本: | 5.6 及以上 |
WordPress版本: | 6.3 |
版权: | http://www.apache.org/licenses/LICENSE-2.0 |
CloudCache is designed to be compatible with most plugins and themes, it works with the same basic principle of other caching systems, and many developers are concerned with creating cache-compatible plugins. But unfortunately they are not all, a minority does not care about performance. Because most sites are small and do not get much traffic, this is not a concern for these developers. So we recommend that you always use well-known plugins and themes. After all, if you care about speed and performance, it's not a good idea to have a plugin on your site that is not suited for high-traffic sites!
The only pages that should purge are the post's page, the front page, categories, and tags. When building out this plugin, there were a couple pathways on how best to handle purging caches and they boiled down to two: Decisions (the plugin purges what it purges when it purges) and Options (you decide what to purge, when and why). It's entirely possible to make this plugin purge everything, every time a 'trigger' happens, have it purge some things, or have it be so you can pick that purges.
Because the plugin only purges your content when you edit it. That means if you edit a page/post, or someone leaves a comment, it'll change. Otherwise, you have to purge the whole cache. The plugin will do this for you if you ''change'' your theme, but not when you edit your theme. If you use Jetpack's CSS editor, it will purge the whole cache for your site on save.
Click the 'Purge CloudCache' button on the "Right Now" Dashboard (see the screenshot if you can't find it). There's also a "Blizhost CloudCache > Purge Entire Cache" button on the admin toolbar.
If you're on a Multisite Network and you're on the primary site in the network, only the network admins can purge that site
On a subfolder network if you flush the site at example.com
, then everything under that (like example.com/site1
and example.com/siten
and everything else) would also get flushed. That means that a purge on the main site purges the entire network.
In order to mitigate the destructive nature of that power, only the network admins can purge everything on the main site of a subfolder network.
Of course! Feel free to use with any proxy or CDN service.
You can open a support ticket on the client panel requesting the removal of CloudCache. But it's important to note that this technology makes your site up to 300x faster and with support for high traffic.
home_url()
purgePost()
to validate page_for_posts