Breeze – WordPress Cache Plugin

Description

Breeze is a free, simple (yet powerful) and user-friendly WordPress Caching Plugin developed by the Cloudways team. It offers various options to optimize WordPress performance at various levels. It works equally great with WordPress, WordPress with WooCommerce and WordPress Multisite.

Breeze excels in the following areas:

• Performance: Breeze improves website speed and resource optimization. Other features include file level cache system, database cleanup, minification, support for Varnish cache and simplified CDN integration options.

• Convenience: Breeze is easy to install and configure directly from WordPress. Configuring Breeze is easy and most of the default options work well right out of the box. The recommended settings should work on all your WordPress websites seamlessly.

• Simplicity: Breeze is designed to be simple for all users. Just install and activate the plugin and you’ll see the results instantaneously.

What makes Breeze WordPress Cache Plugin awesome is that it comes with builtin support for Varnish. If Varnish is not installed on your servers, Breeze will utilize its internal cache mechanism to boost up your WordPress site performance.

FEATURES

• Seamless integration with Varnish Cache for efficient content delivery. No manual adjustments needed – all settings come pre-configured for your convenience.
• Optimize performance using Cloudflare’s caching capabilities. No specific Breeze configurations are needed – it works out of the box.
• Effortlessly integrate your preferred Content Delivery Network (CDN) for global content distribution with Breeze instead of using the the CDN providers’ plugins.
• Trim WordPress database bloat effortlessly. Breeze’s Database Options optimize and declutter your database, boosting performance by removing unneeded data like post revisions and trashed content.
• Take command over caching exclusions. With Breeze, you have the power to prevent specific URLs, JS files, and CSS files from being cached.
• Achieve smaller page sizes and faster load times through HTML, CSS, and JavaScript minification, including inline CSS and JavaScript minification.
• Load images when they’re visible, not all at once, for faster webpage performance by implementing lazy loading for images.
• Load JS files with deferred loading, enhancing overall performance.
• Supercharge your site’s speed with Breeze’s advanced preloading features: load fonts early, quicken link clicks, and enhance DNS requests for a seamless user experience.
• Master real-time interactions with Breeze’s Heartbeat API management. Fine-tune notifications, sales data, autosaves, and more to optimize WordPress performance by adjusting API call frequencies.
• Effortlessly manage Breeze settings using Import/Export. Download your configurations as a .json file for backup, or effortlessly import existing settings to quickly fine-tune your optimization.

Support: We love to provide support! Post your questions on the www.remarpro.com support forums, or if you are a Cloudways Customer you may ask questions on the Cloudways Community Forum.

Requirements

PHP 7.4, PHP 8 recommended for better performance, WordPress 6.0+

Installation

To install the plugin via WordPress Dashboard:

• In the WordPress admin panel, navigate to Plugin > Add new
• Search for Breeze
• Click install and wait for the installation to finish. Next, click the activate link

To install the plugin manually:

• Download and unzip the plugin package – breeze.1.0.0.zip
• Upload the breeze to /wp-content/plugins/
• Activate the plugin through the ‘Plugins’ menu in WordPress
• Access Breeze from WordPress Admin > Settings > Breeze

FAQ

Installation Instructions

To install the plugin via WordPress Dashboard
1. In the WordPress admin panel, Menu > Plugin > Add new
2. Search for Breeze
3. Click on install and wait for the installation to finish. Next, then click on the activate link

To install the plugin manually
1. Download and unzip the plugin package – breeze.1.0.0.zip
2. Upload the /breeze to /wp-content/plugins/
3. Activate the plugin through the ‘Plugins’ menu in WordPress
4. Access Breeze from WordPress Admin > Settings > Breeze

Does Breeze support Varnish and to what extent?

Breeze, by default, supports Varnish. It has been tested to be fully compatible with Cloudways Servers that come with Varnish pre-installed. If you are using hosting providers other than Cloudways, we suggest you confirm Varnish support with your hosting provider

Does Breeze support WooCommerce?

Breeze is fully compatible with WooCommerce, out of the box. It does not require any special configurations.

Does Breeze support WordPress Multisite?

Breeze is fully compatible with WordPress Multisite without the need for any extra configuration.

How does Breeze handle WordPress multisite?

Breeze handles all WordPress multisite instances globally. All the settings for multisite are now handled on the network level.

Is Breeze compatible with other WordPress Cache plugins?

We DO NOT recommend using two WordPress cache plugins at the same time on any WordPress website.
We strongly recommend that you use Breeze as the only cache plugin for your website. If there are any other cache plugins installed, please ensure that you have disabled them prior to proceeding with the Breeze installation.

Is Breeze compatible with HTTPS?

Breeze does not require any special configuration to work with HTTP or HTTPS pages.

Does Breeze have compatibility issues with other known plugins?

Breeze has been tested with popular plugins available on www.remarpro.com. Please feel free to report any incompatibilities on the WordPress Support Forums or on Cloudways Community Forum.

Does Breeze support CDN?

Breeze supports CDN integration. It allows all static assets (such as images, CSS and JS files) to be served via CDN.

What does Breeze’s Database Optimization feature do?

WordPress databases are notorious for storing information like post revisions, spam comments and much more. Over time, databases l become bloated and it is a good practice to clear out unwanted information to reduce database size and improve optimization.

Breeze’s database optimization cleans out unwanted information in a single click.

Will comments and other dynamic parts of my blog appear immediately?

Comments will appear upon moderation as per the comment system (or policy) set in place by the blog owner. Other dynamic changes such as any modifications in files will require a full cache purge.

Can I exclude URLs of individual files and pages from cache?

You can exclude a file by mentioning its URL or file type (by mentioning file extension) in the exclude fields (available in the Breeze settings). Exclude will not let the cache impact that URL or file type.

If Varnish is active, you will need to exclude URLs and file type(s) in the Varnish configuration. If you are hosting WordPress websites on Cloudways servers, follow this KB to exclude URLs from the Varnish cache.

Does it work with all hosting providers?

Breeze has been tested to work with all major hosting providers. In addition, major Breeze options such as Gzip, browser cache, minification, grouping, database optimization. CDN integration will work as expected on all hosting providers.

Where can I get support for Breeze?

You can get your questions answered on the WordPress support forums. If you are a Cloudways customer, please feel free to start a discussion at Cloudways Community Forum.

How can I test and verify the results?

You will be able to see the impact of the Breeze Cache Plugin almost immediately. We also recommend using the following tools for generating metrics:
Google Page Speed
WebPagetest
Pingdom

Does Breeze plugin work with Visual Builder?

Yes, Breeze Plugin is compatible with Visual Builder.

What popular CDN are supported by Breeze Plugin?

Breeze supports the following three popular CDNs:
MaxCDN
KeyCDN
Amazon Cloudfront

Does Breeze support Push CDN?

No, Breeze does not support Push CDN. However, you could use Breeze with Push CDNs using third party plugins.

Does Breeze Work With CloudFlare?

Yes. The process of setting up CloudFlare with Breeze is easy. Check out the following KnowledgeBase article for details.

How Breeze cache uses Gzip?

Using Gzip, Breeze compresses the request files, further reducing the size of the download files and speeding up the user experience.

Reviews

Value of Breeze is Questionable

lwoods September 30, 2024 1 reply

I get burned constantly when I update Breeze. And, it’s on different sites with different plugins. Breeze affects multiple plugins, and in some cases it is only is certain situations, so it is impossible to test for every situation where Breeze screws up stuff.

Excellent!

leodefaveri September 19, 2024 1 reply

Excellent work from the Cloudways team, as the plugin works perfectly with sites that are also outside the server. It’s the only one that worked correctly on a client in conjunction with varnish and CDN. Great work!

Issues, issues, issues.

cmyk2016 July 15, 2024 1 reply

I use Cloudways for multiple client websites and their hosting is excellent. But their default Breeze cache plugin is nothing but issues, and inconsistent ones at that. On one site the WP admin dashboard would simply be a blank screen, even though we could access the rest of the admin areas. On another site Breeze totally messed up the layout. Deactivating this plugin now on all sites and going with a different cache plugin. Don’t recommend using this.

Is a must-have for Anyone Looking to Boost their site’s Speed and Performance

DIGITAREZ May 29, 2024 1 reply

Easy to install and configure, it offers an intuitive interface for managing cache, optimizing files, and integrating with CDNs. With significant improvements in load times and PageSpeed scores, Breeze makes a noticeable difference. Its compatibility with Varnish Cache is a bonus for Cloudways users. Highly recommended for a seamless and efficient caching solution!

Nothing but Trouble

Klaus Hong April 19, 2024 1 reply

Cloudways hosting is excellent. However, the Breeze plugin is not. I am currently using Google GCP CO 2XL hosting, which costs about $400 a month and has great performance. Yet, when using the Breeze plugin, CPU usage easily spikes to 100% and crashes the site. It has also caused permission issues recently, adding to the stress. Interestingly, as soon as I deleted the Breeze plugin, the site loading speed improved and CPU usage decreased. Everything has gotten better, except for the fact that I now have to manually clear the Cloudflare cache.

Breaks website styling when using Spectra blocks

yiek8888 March 31, 2024 5 replies

Noticed the styling on my client’s website broke about once every 24 hours. Very frustrating to deal with. Opened a support ticket with Cloudways and honestly they have not been very helpful at all – I basically had to do all of the technical debugging to isolate this issue (even though I’m not really a web developer!) Inspecting the network traffic on my website, noticed that one of the css files generated by Spectra for Spectra blocks would 404 Not Found every 24 hours, which is when the Breeze plugin autocleared the cache. I checked in all of the settings of the cache and tried to figure out how to get Breeze to ignore caching certain directories – no dice. I have since removed Breeze from all of my Cloudways websites. The websites are now working without the styling issues from before. Too bad, I want to use Breeze since it is the recommended plugin by Cloudways – but as long as it breaks my site there’s no way it’s worth the frustration constantly having to fix my client’s site breaking.

Contributors & Developers

Changelog

2.1.15

• Fix: Addressed vulnerabilities related to Broken Access Control and Cross-Site Scripting (XSS) as discovered by Patchstack.

2.1.14

• Fix: The JavaScript warning related to missing href attributes for a link has been fixed.
• Fix: The cache issue has been fixed when updating a post on any sub-blog in the Multisite environment.

2.1.13

• Fix: The cache will be purged automatically when a scheduled post’s status changes to ‘Published’.
• Fix: Update the reference link in the Knowledge Base article under the ‘Never Cache URL(s)’ option in the ADVANCED OPTIONS tab.

2.1.12

• Add: Shop Managers can now use Purge All Cache option to clear website cache.
• Fix: Excluded wp-login.php from preload feature that fixes the problem with unwanted user logouts.

2.1.11

• Fix: The issue with the incorrect previous versions list under the Breeze Rollback Version Option has been resolved.

2.1.10

• Fix: The warning issue has been resolved during the product update process via WP-CRON.
• Fix: In some browsers, pushing the back button would take the user to the same URL. The issue has been resolved and the back button will work as expected.
• Add: The ability to clear the cache for individual WordPress default post types and custom post types has been introduced, offering users enhanced control over their caching strategy.

2.1.9

• Fix: Resolved an issue where images already in the viewport were not loading when JavaScript lazy-load was enabled.

2.1.8

• Add: Users now have the ability to roll back the plugin to previous versions.
• Fix: The file names previously generated by MD5 are now being generated by SHA512
• Fix: PHP Notice that was generated under specific conditions when using the “Never Cache URL(s)” option is no longer being displayed.
• Fix: The compatibility issue between Breeze and WP-Lister, a plugin developed by WP Labs, has been resolved.
• Fix: The conflict regarding the search query string between Breeze and FiboSearch – AJAX Search for WooCommerce has been resolved.
• Fix: Viewport image issues when lazy-load is enabled has been resolved.
• Fix: The issue with converting Hebrew characters in inline scripts to UTF-8 characters has been resolved.

2.1.7

• Fix: Enhancing WooCommerce Default Pages Exclusion Conditions from Cache.
• Fix: Lazy-load placeholder changed to base64 encoding in order to fix incorrect characters from displaying.
• Fix: Improving Compatibility of Delay All JS and Lazy Load Images Options with PHP 8.2
• Fix: The Purge Cache After option’s updated value is now accurately reflected when importing data through the Command Line Interface (CLI).
• Fix: In Multisite where a file permission warning is displayed upon plugin reactivation following deactivation has been addressed.

2.1.6

• Fix: Error when placing WooCommerce order on the checkout page.
• Fix: Issue when query strings contain uppercase letters.

2.1.5

• Add: Implemented wildcard functionality in the Cache Query String.
• Fix: Updated CSS minification library.
• Fix: Successfully resolved the CSS calc function minification issue.
• Fix: Change the file extension of the cache file from .php to .html.
• Fix: Refactored the caching procedure for responses from any ‘edit’ type API requests.
• Fix: Enhanced cache mechanism on WooCommerce orders workflow.
• Fix: Enhanced the mechanism to automatically clear the archive cache whenever a term is updated.
• Fix: Enhanced the CDN URLs pattern to accommodate additional characters for top-level domains.

2.1.4

• Fix: Addressed a vulnerability discovered by CovertSwarm.
• Fix: Limited the thank-you message display to admin and super admin users after activating Breeze.
• Fix: Resolved file permission warning issues in the multisite network, ensuring seamless operation when adding a new subsite.
• Fix: Modified the Mobile Detect PHP Namespace in the third-party library to prevent conflicts with other plugins or themes, improving overall compatibility.
• Fix: Ignored images with both JSON and JSON encryption to prevent adverse effects on other libraries handling those tags, ensuring smooth functionality.
• Fix: Separated lazy load functionality for videos and iframes, providing increased control over website lazy loading behavior for a more optimized user experience.
• Add: Implemented distinct functionality for tags specifically with the ‘src’ attribute, excluding video tags with tags, enhancing flexibility and control over video elements.

2.1.3

• Fix: Functionality is improved to handle cases where no “HTTP_USER_AGENT” header is sent.

2.1.2

• Fix: Enhanced the conditions of device-based caching for users on the Cloudways Autoscale Platform.

2.1.1

• Fix: Resolve issue of Breeze plugin directory location.

2.1.0

• Add: Device-based caching for desktops, tablets, and mobile devices.
• Add: WordPress REST API Integration for cache purging.
• Add: Ability to set authentication key for REST API integration.

2.0.33

• Fix: Breeze plugin is now fully compatible with PHP 8.2 as all the compatibility issues are solved.
• Fix: Lazy load option is enhanced to ensure compatibility with diverse themes and avoid image or video loading conflicts.
• Fix: Host font locally option is improved to handle special characters effectively, enhancing font display.
• Fix: WooCommerce cart caching is prevented when the preload option is enabled, preventing unwanted cart data caching.

2.0.32

• Add: Now users can exclude their custom HTTP headers from caching when HTML minification is on. Simply pass your custom headers through the WP filter ‘breeze_custom_headers_allow’ for a more tailored and dynamic caching experience.
• Fix: Breeze now seamlessly supports both relative and absolute URL paths for preloading. Say goodbye to errors – and more assets effortlessly with the enhanced Breeze preload feature.

2.0.31

• Add: Breeze now supports the Aelia Currency Switcher for WooCommerce.
• Add: Breeze will automatically clear the cache for order products, homepage, and shop page if the “Out of stock visibility” option is enabled and the stock is no longer available.

2.0.30

• Add: Host Files Locally improve website speed by serving Google Fonts, Google Analytics, Facebook, and Gravatar files directly from your application’s local path.

2.0.29

• Add: Breeze now supports the latest version of the CSS minified library for superior performance.
• Add: Preload Link option is enabled by default now to boost your website performance.

2.0.28

• Add: JavaScript file deferred loading feature now supports external third-party files alongside WP Core, themes, and plugins files.

2.0.27

• Add: Installing and activating Breeze using WP CLI will now automatically add GZIP compression and browser cache rules to the .htaccess file. Similarly, deactivating and deleting Breeze using WP CLI will remove these rules from the .htaccess file.

2.0.26

• Fix: The issue caused by CLI plugin update, resolving error related to WP_Upgrader_Skin class requirement removal.

2.0.25

• Fix: Purging the cache from Breeze for WordPress Multisite applications will not purge the OCP cache.

2.0.24

• Fix: Handling of the ‘WP_Upgrader_Skin’ class for seamless update functionality via wp-cli.

2.0.23

• Add: Smart Cache Purge Configuration for Cloudflare is now available for Flexible Platform for Cloudways users.
• Add: Environment detection is now available for Cloudways users to automatically detect the platform, e.g., Flexible or Autoscale.
• Add: Filters are added to interact with the content buffer before cache files are created. Use a filter called “breeze_cache_buffer_before_processing” to interact with buffer content before performing any changes and “breeze_cache_buffer_after_processing” after markup changes are finished.

2.0.22

• Fix: Issues with Lazy Load and Cross-origin have been fixed by rewriting the engine to avoid interfering with bad markup.

2.0.21

• Add: Moved the Cloudflare Cache option to Purge Modules for Cloudways users only.
• Add: Purge Varnish option will not be shown if varnish header not available.

2.0.20

• Fix: Fatal error displayed while editing WooCommerce attributes and other entities.

2.0.19

• Fix: Purge All Cache permalink for WordPress subdirectory installations.

2.0.18

• Add: Integrated Cloudflare Cache in Breeze for Cloudways users only.
• Add: s-maxage in cache-control of Response Headers.
• Fix: Stopped purging the OCP cache while cache purging from Breeze.
• Fix: Improved compatibility of Breeze with Woodmart theme.
• Fix: Improved compatibility of Breeze with Buddyboss theme.
• Fix: Preserving declared media for styles on combine CSS.

2.0.17

• Fix: P-Tag will not be added when Lazy Load Images and Cross-Origin Safe Links are enabled.

2.0.16

• Fix: Ninja Forms now works when Lazy Load Images and Cross-Origin Safe Links are enabled.
• Fix: All types of Google Tag Manager scripts will work with the “Delay JS Inline Scripts” option.
• Add: “Reset Now” option has been added for default settings. It can also operate with WP-CLI.
• Add: Enabled “Combine JS” option will disable “Delay JS Inline Script” or “Delay All JavaScript” and vice versa.

2.0.15

• Add: Internal cache Purge while changing Theme.
• Add: Internal cache Purge while using the options WP Customizer.
• Fix: Improvise handling of Optimize Database option under the Database Options Tab by adding a message and loading bar.
• Fix: Improvise the handling of the Request header while Varnish proxy behind and re-download necessary.

2.0.14

• Fix: Applied condition to look new Facebook feed link in the plugin Facebook for WooCommerce.

2.0.13

• Fix: DOMDocument class was removed while enabling the options Lazy Load Images and Cross-origin Safe Links.

2.0.12

• Fix: Synchronized the reset cache option of the Avada theme with Breeze.

2.0.11

• Add: Scanning of CDN URL to verify it is not malicious in the CDN.
• Fix: Improvised process of generating JS files from PHP files.
• Fix: Improvised handling of multi-byte characters, languages, symbols such as Unicode icons, etc.
• Fix: Improvised the functionality of the Defer option while using an external JS file.
• Fix: Enhanced the compatibility with Weglot Translate.

2.0.10

• Add: More options added in the Database option tab.
• Add: Display Autoload summary with Autoload total size as well as Autoload count.
• Fix: Enhance the functionality of the options Combine CSS and Inline CSS while CSS is generated by Elementor.
• Fix: Overwrite the TimeZone To UTC being sent out in ticket/order confirmations of The Events Calendar plugin.

2.0.9

• Fix: Added nonce check to import settings ajax request, in order to improve security and prevent cross-site requests.

2.0.8

• Fix: Enhance compatibility with the Pickingpal plugin to load the orders.
• Fix: Remove duplication header calls in Varnish requests.
• Fix: Invalid Certificate never accepted and its default value is TRUE now.
• Add: Include the option to Clear Object Cache.

2.0.7

• Fix: In some cases call to undefined function is_plugin_active() shows, it is fixed now by replacing it with a check for class_exist in CURCY and WOOCS plugins.

2.0.6

• Fix: Overwrites the TimeZone To UTC of The Events Calendar plugin.
• Fix: currency menu is cached with HTML, changing it with the currency is difficult in CURCY and WOOCS plugins.
• Fix: Preloading links that do not have “href“ attribute or the “href“ attribute contains the value “#” was displaying errors in the console log.
• Fix: Some inline javascript files were not displayed when the option “JS Files With Deferred Loading” had at least one value-added breaking functionality for other JavaScript scripts.

2.0.5

• Add: UI improvement to provide better accessibility and user experience.

2.0.4

• Add: Improve page load by delaying JavaScript execution. Delay JS is disabled by default for new installations.
• Fix: Added JavaScript checks to see if the sortable library is loaded or not, if not then the JS code that requires the library will not execute.
• Fix: Undefined variable in Breeze minification scripts.

2.0.3

• Fix:All ajax actions are now restricted to the users that have manage_options capabilities. Vulnerability discovered from patchstack team.
• Fix: Administrator has only capable to handle manage_options by default.
• Fix: Added restriction to option-tabs-loader.php, if the user does not have manage_options capability, then the tabs will not load.

2.0.2

• Fix: Atarim – Client Interface Plugin conflict with UI of Breeze in the admin area.
• Add: Make LazyLoad for iframes compatible
• Add: Control WordPress Heartbeat API. Users can disable it, independently on the admin, post editor page, and frontend.
• Add: DNS prefetch on pages.
• Add: Improve the handling of warning message while permission is not correct.

2.0.1

• Fix: Improved handling of minification in Never Cache URL(s) option.

2.0.0

• Add: Implement a new UI interface.
• Fix: Duplicate script while using the option Move JS Files to Footer.
• Fix: Improvise the optimization of WordPress core functions to clean the database correctly.
• Fix: Implement condition in .htaccess rules while disable “mod_env”.
• Fix: Compatibility issue with Facebook For WooCommerce plugin.

1.2.6

• Add: Varnish cache will be clear while plugin deactivate.
• Add: Enable cache for specific user role.
• Add: Disable Emojis to reduce request
• Add: Delete breeze options values from database on plugin deletion.
• Fix: Compatibility issue of map short codes with GeoDirectory plugin.
• Fix: Compatibility issue with Ad Inserter plugin.
• Fix: Compatibility issue of minification with Beaver Builder Plugin.
• Fix: Compatibility issue of JS scripts with AMP Plugin.
• Fix: Reduce cookie life time span while user posts a comment.
• Fix: HTML elements filtered from RestAPI end point of lazy-load scripts.
• Fix: Config file of each subsite save with appropriate ID in advance cache file.
• Fix: Google Analytics script exclude from Minification.

1.2.5

• Add: URLs containing query strings will not be cached by default.
• Add: Ignore specific query strings while serving the cache to improve performance.
• Add: Ability to cache URLs with specific query strings variables.
• Add: Cache handling of URLs having multiple parameters in one query string.
• Add: Exceptional Cache handling for case where permalink is set to PLAIN, which includes links for POST, PAGES, ATTACHMENTS, CATEGORIES, ARCHIVES.

1.2.4

• Add: Functionality to clear ALL cache via Command Line Interface (wp-cli).
• Add: Functionality to clear Varnish cache via Command Line Interface (wp-cli).
• Add: Functionality to clear Internal cache via Command Line Interface (wp-cli).
• Add: While the file Permission is not correct, the warning message has been added.
• Fix: Compatibility with Coming Soon Page, Maintenance Mode & Landing Pages by SeedProd.
• Fix: improve the handling of warning undefine array key of delay JS script while enable debug mode.

1.2.3

• Add: Addition in Media assets rules for browser cacheable objects.
• Add: Addition in Font assets rules for browser cacheable object.
• Add: Addition in Data interchange rules for browser cacheable objects.
• Add: Addition in Manifest files rules for browser cacheable object.
• Add: Addition in Gzip compression rules.
• Fix: Improvise the handling of the Request header while the varnish is disable
• Fix: Improvise the condition of Option “Enable cache for logged-in users”

1.2.2

• Add: Export settings via Command Line Interface (wp-cli).
• Add: Import settings via Command Line Interface(wp-cli).

1.2.1

• Fix: improve the handling of warning undefine index of lazy load image while enable debug mode.
• Add: Enable/Disable option of Delay JS inline scripts.

1.2.0

• Add: “noreferrer noopener” attributes tag on external links when process HTML for caching.
• Add: Preload fonts allow to text remain visible during webfont load.
• Add: Preload key request of fonts OR CSS file which load fonts from local resource.
• Add: Preload links allow to enable preload next page of application.
• Add: lazy load display images on a page only when they are visible to the user.
• Add: Minimize the impact of third-party code.

1.1.11

• Fix: Improved handling of forms using nonce in Permalinks and Options pages.

1.1.10

• Fix: Apply deferred loading at individual file.
• Fix: exclude feed url generated by plugin “Facebook for WooCommerce”.
• Fix: purge site cache in subfolder.
• Fix: Inventory stock now updated at the Cart page.
• Fix: Improved Support for the new version of the WooCommerce Booking Calendar plugin.
• Add: Compatible with EDD and cartflow plugins.
• Add: pages include shortcode has been exclude by Breeze.

1.1.9

Add: Improved handling of minification for Query stirng based exclusion in Never Cache These URLs option.
Add: Increase compatibility with Multilingual .

1.1.8

• Fix: Cache refresh issue when Varnish is disabled.
• Fix: Replaced functions deprecated in WordPress 5.5 that were causing warning messages.
• Fix: Replaced deprecated minification libraries to improve compatibility with PHP 7.x onward.
• Fix: resolved the warning generated by the Query Monitor plugin.
• Add: compatibility with PHP 7.4

1.1.7

• Fix: Add HTTP and HTTPS for validation of CDN integration.
• Fix: Custom settings for multisite will be reapplied after Breeze reactivation.
• Fix: General improvements to improve support for the WooCommerce Booking Calendar plugin.
• Fix: Improved handling of minification for Wildcard based exclusion in Never Cache These URLs option.

1.1.6

• Add: Wildcard (.*) based exclusion of pattern URL strings in Never Cache These URLs option.
• Fix: Improved validation for CDN integration.
• Fix: General improvements to support for Elementor Forms/Elementor Pro and CDN integration.

1.1.5

• Fix: Revised duration for browser cacheable objects

1.1.4

• Fix: PHP Fatal error while running commands through WP_CLI

1.1.3

• Fix: Undefine error for inline JS when JS Group file is enabled.
• Fix: Several files displayed when Group Files was enabled.
• Fix: Varnish auto purge slowed down admin area while varnish is not running.
• Fix: PDF files are not downloadable with CDN enabled.
• Fix: miscellaneous UI issues.
• Add: The Google Analytics script/tag is now excluded form Minification.
• Add: Option to enable cache for admin user.
• Add: Handling of 404 error of JS/CSS/HTML when cache files are not writeable.
• Add: Exclude @import directive from CSS Minification.

1.1.2

• Fix: Improved handling of exclusion of CSS and JS while Minification and Group Files options are enabled.
• Fix: Allow wildcard (.*) based exclusion of pattern files/URIs in exclude JS and exclude CSS fields.
• Fix: Increase the duration for leverage browser cacheable objects

1.1.1

• Fix: Removed the use of remote JS. Now uses built-in version of jQuery Libraries.

1.1.0

• Add: Optional separate cache settings for subsites.

1.0.13

• Fix: Validation of nonce.
• Fix: Remove duplication of calls in Varnish purge requests.

1.0.12

• Fix: Deprecated create_function

1.0.11

• Fix: Change wp_redirect to wp_safe_redirect to fix redirect vulnerability of URL

1.0.10

• Add: Allow Purge Cache for Editors role.

1.0.9

• Add: Option to move JS file to footer during minification
• Add: Option to deffer loading for JS files
• Add: Option to include inline CSS
• Add: Option to include inline JS

1.0.8

• Fix: Cache exclusion for pages that returns status code other than 200

1.0.7

• Fix: Grouping and Minification issues for PHP 7.1
• Fix: Cache purge after version update issue
• Fix: Increase in cache file size issue.
• Fix: Server not found error notification
• Fix: Default WP comments display not require cache purge

1.0.6

• Fix: All Multisite are now handled globally with settings being handled at network level

1.0.5

• Fix: Issue with JS minification

1.0.4

• Fix: Browser Cache issues with WooCommerce session
• Fix: Clearing Breeze rules from .htaccess upon deactivating of GZIP/Broswer Cache
• Fix: Regex fix for accepting source url’s without quotes while enabling minifcation
• Add: FAQ section added

1.0.3-beta

• Fix : Disabled browser cache for WooCommerce cart, shop and account pages
• Fix : Removal of htaccess when disabling browser cache and gzip compression options
• Fix : CDN issues of not serving all the configured contents from CDN service

1.0.2-beta

• Fix : Compatibility issues of WooCommerce

1.0.1-beta

• Fix : Purging issue to allow only admin users to Purge
• Add : Feedback link

1.0.0

• Add : First Beta release