WordPress.org
Get WordPress

Plugin Directory

Changeset 3163268


Ignore:
Timestamp:
10/05/2024 11:28:21 PM (18 months ago)
Author:
blizhost
Message:

Readme Update

Location:
blizhost-cache-purge
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • blizhost-cache-purge/tags/4.0.6/readme.txt

    r3163265 r3163268  
    8181
    8282= Is CloudCache compatible with all WordPress plugins and themes? =
    83 
    84 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.
    85 
    86 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.
    87 
    88 So we recommend that you always use well-known plugins and themes.
    89 
    90 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!
     83<strong>CloudCache</strong> is designed to be compatible with most WordPress plugins and themes, including popular ones like <strong>WooCommerce</strong>, <strong>Elementor</strong>, <strong>LiteSpeed Cache</strong>, and many others. However, some less optimized plugins or themes may not fully support caching technologies. These cases are rare, but it’s always a good idea to use well-maintained and optimized plugins to ensure the best performance and compatibility with high-performance systems like <strong>CloudCache</strong>.
    9184
    9285= Why doesn't every page flush when I make a new post? =
    93 
    94 The only pages that should purge are the post's page, the front page, categories, and tags.
    95 
    96 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.
     86<strong>CloudCache</strong> performs an intelligent cache purge, removing only the necessary pages to ensure updates are reflected without overloading the server. When you publish a new post, the pages purged include the homepage, the post itself, associated categories and tags, pagination pages, and <strong>sitemaps</strong>, among other relevant pages. This optimizes performance while ensuring that important updates are visible to your visitors.
    9787
    9888= Why doesn't my cache purge when I edit my theme? =
    99 
    100 Because the plugin only purges your <em>content</em> 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.
    101 
    102 If you use Jetpack's CSS editor, it will purge the whole cache for your site on save.
     89<strong>CloudCache</strong> automatically clears the cache when there are changes to your site’s <strong>content</strong>, such as editing pages, posts, or receiving comments. However, if you're simply <strong>editing</strong> the theme (e.g., modifying CSS or adjusting visual settings), the cache is not automatically cleared because the content remains the same. To reflect these changes, you can manually purge the cache. If you <strong>switch</strong> to a new theme entirely, <strong>CloudCache</strong> will automatically flush the entire cache for you.
    10390
    10491= How do I manually purge the whole cache? =
    105 
    106 Click the 'Purge CloudCache' button on the "Right Now" Dashboard (see the screenshot if you can't find it).
    107 
    108 There's also a "Blizhost CloudCache > Purge Entire Cache" button on the admin toolbar.
     92You can manually flush the entire cache by clicking the "Purge CloudCache" button on the WordPress dashboard or using the "Blizhost CloudCache > Purge Entire Cache" option in the admin toolbar.
    10993
    11094= I don't see a button! =
    111 
    112 If you're on a Multisite Network and you're on the primary site in the network, only the <em>network</em> admins can purge that site
    113 
    114 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.
    115 
    116 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.
    117 
    118 = Can I use this with a proxy service like CloudFlare? =
    119 Of course! Feel free to use with any proxy or CDN service.
    120 
    121 = How do I disable the CloudCache? =
    122 
    123 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.
     95If you're using a Multisite Network and you're on the primary site, only <strong>network</strong> admins can purge the cache for the main site. In subfolder networks, flushing the main site (`example.com`) also purges all subsites (like `example.com/site1`). This is done to prevent accidental cache flushes across the network.
     96
     97= Can I use this with a proxy service like Cloudflare? =
     98Absolutely! <strong>CloudCache</strong> is fully compatible with proxy or CDN services like <strong>Cloudflare</strong>, enhancing both the performance and security of your site.
     99
     100= How do I disable CloudCache? =
     101You can request the removal of <strong>CloudCache</strong> by opening a support ticket in the client panel. However, keep in mind that <strong>CloudCache</strong> significantly boosts your site's speed and traffic-handling capacity, making it up to 300x faster.
    124102
    125103== Changelog ==

  • blizhost-cache-purge/trunk/readme.txt

    r3163265 r3163268  
    8181
    8282= Is CloudCache compatible with all WordPress plugins and themes? =
    83 
    84 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.
    85 
    86 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.
    87 
    88 So we recommend that you always use well-known plugins and themes.
    89 
    90 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!
     83<strong>CloudCache</strong> is designed to be compatible with most WordPress plugins and themes, including popular ones like <strong>WooCommerce</strong>, <strong>Elementor</strong>, <strong>LiteSpeed Cache</strong>, and many others. However, some less optimized plugins or themes may not fully support caching technologies. These cases are rare, but it’s always a good idea to use well-maintained and optimized plugins to ensure the best performance and compatibility with high-performance systems like <strong>CloudCache</strong>.
    9184
    9285= Why doesn't every page flush when I make a new post? =
    93 
    94 The only pages that should purge are the post's page, the front page, categories, and tags.
    95 
    96 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.
     86<strong>CloudCache</strong> performs an intelligent cache purge, removing only the necessary pages to ensure updates are reflected without overloading the server. When you publish a new post, the pages purged include the homepage, the post itself, associated categories and tags, pagination pages, and <strong>sitemaps</strong>, among other relevant pages. This optimizes performance while ensuring that important updates are visible to your visitors.
    9787
    9888= Why doesn't my cache purge when I edit my theme? =
    99 
    100 Because the plugin only purges your <em>content</em> 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.
    101 
    102 If you use Jetpack's CSS editor, it will purge the whole cache for your site on save.
     89<strong>CloudCache</strong> automatically clears the cache when there are changes to your site’s <strong>content</strong>, such as editing pages, posts, or receiving comments. However, if you're simply <strong>editing</strong> the theme (e.g., modifying CSS or adjusting visual settings), the cache is not automatically cleared because the content remains the same. To reflect these changes, you can manually purge the cache. If you <strong>switch</strong> to a new theme entirely, <strong>CloudCache</strong> will automatically flush the entire cache for you.
    10390
    10491= How do I manually purge the whole cache? =
    105 
    106 Click the 'Purge CloudCache' button on the "Right Now" Dashboard (see the screenshot if you can't find it).
    107 
    108 There's also a "Blizhost CloudCache > Purge Entire Cache" button on the admin toolbar.
     92You can manually flush the entire cache by clicking the "Purge CloudCache" button on the WordPress dashboard or using the "Blizhost CloudCache > Purge Entire Cache" option in the admin toolbar.
    10993
    11094= I don't see a button! =
    111 
    112 If you're on a Multisite Network and you're on the primary site in the network, only the <em>network</em> admins can purge that site
    113 
    114 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.
    115 
    116 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.
    117 
    118 = Can I use this with a proxy service like CloudFlare? =
    119 Of course! Feel free to use with any proxy or CDN service.
    120 
    121 = How do I disable the CloudCache? =
    122 
    123 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.
     95If you're using a Multisite Network and you're on the primary site, only <strong>network</strong> admins can purge the cache for the main site. In subfolder networks, flushing the main site (`example.com`) also purges all subsites (like `example.com/site1`). This is done to prevent accidental cache flushes across the network.
     96
     97= Can I use this with a proxy service like Cloudflare? =
     98Absolutely! <strong>CloudCache</strong> is fully compatible with proxy or CDN services like <strong>Cloudflare</strong>, enhancing both the performance and security of your site.
     99
     100= How do I disable CloudCache? =
     101You can request the removal of <strong>CloudCache</strong> by opening a support ticket in the client panel. However, keep in mind that <strong>CloudCache</strong> significantly boosts your site's speed and traffic-handling capacity, making it up to 300x faster.
    124102
    125103== Changelog ==
Note: See TracChangeset for help on using the changeset viewer.