Açıklama

🚀 Blizhost CloudCache Purge: Speed, Security, and Performance for Your WordPress Site

Blizhost CloudCache Purge is the essential plugin for those seeking speed, enhanced security, and optimized SEO for WordPress sites. Exclusive to Blizhost customers, this plugin integrates with CloudCache, a powerful and optimized solution for high-traffic websites, designed to significantly improve performance and protect your site from threats.

🎯 Why Use Blizhost’s CloudCache?

Extreme Speed: CloudCache delivers your site’s content directly from the server’s RAM, enabling loading speeds up to 300x faster.
Enhanced Security: Robust protection against brute force attacks, exploitable vulnerabilities, and unauthorized access attempts to administrative pages.
Optimized SEO: Loading speed is a crucial factor for Google rankings and other search engines. With CloudCache, your site becomes significantly faster, improving its ranking in search results.
High Performance under Heavy Traffic: Perfect for high-traffic sites, CloudCache ensures your site remains stable and fast, even during traffic spikes.
Built for HTTP: Unlike solutions such as Squid, Apache, or Nginx, CloudCache is 100% focused on the HTTP protocol, maximizing performance for WordPress sites.

🔒 Top-notch Security and Performance

CloudCache offers advanced protection, with features similar to services like Sucuri and Cloudflare, ensuring your WordPress site is secure and running at peak performance:

Brute Force Attack Protection: Prevents malicious login attempts to the WordPress admin area by limiting the number of failed access attempts.
Vulnerability Exploit Defense: Automatically monitors and blocks attempts to exploit known vulnerabilities in WordPress and its plugins.
DDoS Mitigation: Protects your site from distributed denial-of-service (DDoS) attacks, keeping it available even during malicious traffic surges.
Security Rules: Advanced filtering to block malicious traffic before it reaches your site.
Sensitive Page Protection: Additional security layer for critical areas, such as login and admin pages.

💡 Immediate Benefits of Blizhost CloudCache Purge

Automated and Intelligent Caching: Whenever you publish, edit, or delete a post, page, or comment, the cache is automatically updated, ensuring that changes are quickly and accurately reflected.
Full WordPress Compatibility: The plugin seamlessly integrates your WordPress with Blizhost’s CloudCache, optimizing both speed and security.
SEO Improvement: Site speed is a critical factor for SEO, and with CloudCache, you’ll experience fast and efficient loading, helping boost your rankings on Google.

🔧 How Does Blizhost CloudCache Purge Work?

Automatic and Intelligent Cache Clearing:
- The cache is automatically updated when you make changes to content, such as posts, pages, or comments. Relevant pages like sitemaps are also refreshed, ensuring that changes are reflected.
- When important settings like title, description, or modifications to the WordPress Customizer are made, the entire cache is cleared, ensuring that your site reflects all changes correctly.
Manual Cache Control:
- The cache can be manually cleared via simple buttons in the WordPress dashboard or toolbar, giving you full control over cache behavior.

🌟 What is CloudCache?

CloudCache is an exclusive technology from Blizhost, inspired by systems used by major companies like Wikipedia, The New York Times, Facebook, and Twitter. It delivers your site’s content directly from the server’s RAM, resulting in ultra-fast loading, ideal for high-traffic websites.

🧩 Full Compatibility with Plugins and Themes

The Blizhost CloudCache Purge is fully compatible with key tools in the WordPress ecosystem, including:

WooCommerce: For high-performance online stores.
Cloudflare: Integration with the CDN and security features.
All caching plugins: Including LiteSpeed Cache, W3 Total Cache, WP Rocket, and WP Super Cache.
AMP: Full support for Accelerated Mobile Pages (AMP).
Page Builders: Compatible with Elementor, Divi, WPBakery, and more.
Form Plugins: Such as Contact Form 7, Gravity Forms, WPForms, etc.

Note: This plugin was developed exclusively for Blizhost customers. Using it on other hosting providers will not bring the same benefits, as CloudCache was created to operate within our optimized infrastructure, ensuring speed, security, and support for high traffic.

Ekran Görüntüleri

‘Purge CloudCache’ button on the “Right Now” Dashboard

Yükleme

No WordPress configuration needed.

Requirements

Pretty Permalinks enabled
CloudCache enabled on your Blizhost account

Languages

English
Portuguese-BR

SSS

Is CloudCache compatible with all WordPress plugins and themes?: CloudCache is designed to be compatible with most WordPress plugins and themes, including popular ones like WooCommerce, Elementor, LiteSpeed Cache, 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 CloudCache.
Why doesn’t every page flush when I make a new post?: CloudCache 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 sitemaps, among other relevant pages. This optimizes performance while ensuring that important updates are visible to your visitors.
Why doesn’t my cache purge when I edit my theme?: CloudCache automatically clears the cache when there are changes to your site’s content, such as editing pages, posts, or receiving comments. However, if you’re simply editing 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 switch to a new theme entirely, CloudCache will automatically flush the entire cache for you.
How do I manually purge the whole cache?: You 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.
I don’t see a button!: If you’re using a Multisite Network and you’re on the primary site, only network 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.
Can I use this with a proxy service like Cloudflare?: Absolutely! CloudCache is fully compatible with proxy or CDN services like Cloudflare, enhancing both the performance and security of your site.
How do I disable CloudCache?: You can request the removal of CloudCache by opening a support ticket in the client panel. However, keep in mind that CloudCache significantly boosts your site’s speed and traffic-handling capacity, making it up to 300x faster.

İncelemeler

Bu eklenti için herhangi bir değerlendirme bulunmuyor.

Katkıda Bulunanlar ve Geliştiriciler

“Blizhost CloudCache Purge – Speed, Security, and Efficiency” açık kaynaklı yazılımdır. Aşağıdaki kişiler bu eklentiye katkıda bulunmuşlardır.

Blizhost

“Blizhost CloudCache Purge – Speed, Security, and Efficiency” 2 dile çevrildi. Katkıda bulundukları için çevirmenlere teşekkürler.

“Blizhost CloudCache Purge – Speed, Security, and Efficiency” eklentisini dilinize çevirin.

Geliştirmeyle ilgilenir misiniz?

Kodu görüntüleyin, SVN deposuna göz atın ya da RSS ile geliştirme günlüğüne abone olun.

Değişiklik Kaydı

4.0.6

Improvement in sitemap cleaning
Improvement in cache cleaning for scheduled posts
Improvement in cache cleaning for posts generated by dynamic content plugins
Improvement in cache cleaning when WooCommerce products are updated
Implementation of total cache cleaning when there are changes in the site’s title or description, WordPress updates, plugin or theme updates, or Customizer edits
Improved compatibility and cache cleaning when changes are made to the following plugins: Yoast SEO, Advanced Custom Fields, Gravity Forms, Rank Math SEO, WP Offload Media, Slider Revolution, All in One SEO Pack, Advanced Ads, Ad Inserter, AdRotate, Google Site Kit, Insert Headers and Footers, WP QUADS, Easy Google AdSense, Advanced Ads Pro, Ads Pro Plugin, WPForms
Code fixes to improve compatibility with the latest versions of PHP and WordPress

4.0.5

Fixed compatibility bug with PHP 8.1

4.0.4

Fixed an incompatibility bug that was preventing the execution of the current page when clicking on ‘clear cache’ and then performing actions with other plugins
Fixed a bug where ‘after_purge_url’ was not obtaining the result of the request

4.0.3

Fix bug that enabled CDN for external domains
Enable CDN for PNG images

4.0.2

Improved CDN resource compatibility with various themes and caching plugins
Support for PHP version 8.1

4.0.1

Remove version of Slider Revolution for security reasons

4.0.0

Fixed bug that removes URL from styles and scripts due to hashed version security

3.9.9

Remove version of WordPress from rss and header for security reasons
Improve WordPress Security

3.9.8

Fixed non-existent is_plugin_active function error

3.9.7

Fixed compatibility issues with the super-cache plugin and similar

3.9.5

Require Jetpack-connected plugin to use WordPress Image CDN feature

3.9.4

Fixed bug where CDN did not work for http protocol
Improved CDN url regex, filtering content through output buffer
Added option where you can disable CDN by DISABLE_WP_CDN

3.9.3

Improved http protocol of WordPress CDN for more compatibility

3.9.2

Improved WordPress CDN

3.9.1

WordPress CDN implemented

3.9

Plugin renamed for better understanding of this tool
Button on the admin toolbar has been improved

3.8

Purge the pagination pages of cache when a post is created or edited

3.7

Ignore “DONOTCACHEPAGE” on homepage and posts
Fixed bug where it was not possible to clear the cache outside the administrative area in some situations
Prevents requests sended to servers if the site is not hosted on Blizhost

3.6

Fixed bug that “DONOTCACHEPAGE” was not defined under certain circumstances

3.5

Fixed compatibility bug on sites hosted outside Blizhost (even without any effect)

3.4

Several enhancements to make Blizhost CloudCache compatible with various WordPress plugins and themes
Now the CloudCache can be skipped at the backend level
Added “DONOTCACHEPAGE” constant so plugins can specify pages that should not be cached
Forced cache cleanup now works for the entire domain

3.3

Improves plugin security when creating an API key if it does not exist
Support for WP-CLI commands and PHP > 5.5
Fix typo (on -> one)
Correct permissions on Multisite
Correct weird merge error
Fix formatting in Changelog
Allow filter for home_url()
Added wp-cli commands to flush specific URLs and wildcards
Requires wp-cli 0.25+ to work for WP 4.6+
Update purgePost() to validate page_for_posts
Add check for AMP
Purge ‘default’ AMP URL as well

3.2

Fix bug in permalinks notice
Sends the plugin version in the request to the Blizhost server to avoid conflicts

3.1

Fix infinite redirect loops when loading WordPress sites under CloudFlare

3.0

Automatic purge of sitemaps implemented

2.9

Checks if session was initialized before loading CSS

2.8

Change purge notice so it can be dismissed
Fix purging of deleted posts
Fixing i18n which wasn’t working and threw a error on sites without pretty permalinks

2.7

Fixed Blizhost logo on admin bar

2.6

Some language fixes
Fixed font style on admin bar

2.5

Minor fixes
Some language fixes
Blizhost logo changed from png to font style

2.4

Retain query params on purge
Do not use query part for regex purging
Allow CloudCache IP to be filtered.
Improve flushing for cases when there’s no Post ID
Add filter so other plugins can add events to trigger purge when they have no post ID
Add compatibility with Autoptimize so it flushes CloudCache when you flush their cache

2.3

Fixed language directory.
New tags.
Fixed Domain Path.

2.2

Translated to Portuguese-BR.

2.1

Fixed compatibilities issues.

2.0

Several performance upgrades, security and new filters added.

1.0

The code was clean, getting more consistent and adopting best code practices.