See the CommerceGurus Turbo Update Guide to get the latest version of the plugin. If you’d like to be alerted when major CommerceGurus Turbo updates are available sign up to our newsletter.
Remember to fully clear all caching plugins after updating.
Your saved Lazy Load exclusions now work, and the most important images load first
Lazy Load now applies the exclusions that you save, and the first images in your content load first. With the CDN Enabler plugin, Page Cache now serves your CDN URLs to every visitor.
Action needed: After the update, click Purge All Cache in the Turbo menu on the WordPress toolbar. Until you purge, cached pages keep the old behaviour.
Improved
- Lazy Load: Leading Images now go to the first images in your page content, so the images that shoppers see first load first. This helps your Largest Contentful Paint (LCP). Images in the navigation, sidebars, footers and widget areas no longer take a slot. On Shoptimizer, the hidden mega menu images and the sticky header logo no longer take the slots from the first products on the shop page.
- Lazy Load: Images in sidebars, footers, widget areas and upsell sections are now lazy loaded, so the first page load downloads less. The product gallery is now the only built-in exclusion.
- Lazy Load: For developers: the
cgturbo_critical_image_parent_exclusionsfilter now also sets which containers get no Leading Images slot. Code that replaces the list, instead of adding to it, now changes Lazy Load too. - Preload: Critical Images now skips images in the main navigation. The preload links go to your logo and the first image in your content, not to hidden menu images.
- Preload: Hero images now load at once, so their high priority takes effect. This covers sections with the class hero-section or page-hero, and each Parent Selector rule with High priority under Fetchpriority Selectors.
- Preload: The first featured image on a page, such as a blog post image, now loads at once with a high priority. It is often the largest image at the top of the page.
- Global: Turbo is now compatible with WooCommerce 11.3.
Note: To keep sidebar, footer, widget area or upsell images eager, add the container class, for example .sidebar, .site-footer, .widget-area or .upsells, to Parent Container Exclusions. You find it under Advanced LazyLoad Options on the Lazy Load Optimizer page.
Fixed
- Page Cache: With the CDN Enabler plugin, every visitor now gets your CDN URLs. Before, only the first visitor after a purge got them, and later visitors loaded files from your own server. Turbo now also purges all its caches when you save the CDN Enabler settings.
- Lazy Load: The Parent Container Exclusions and Pattern Exclusions that you save now take effect. Before, Turbo ignored them and lazy loaded those images anyway.
- Lazy Load: Parent Container Exclusions now work on any element, such as a list, a link or a nav element. A selector with a special character, such as a slash, no longer turns off all the other exclusions. The Parent Selector rules on the Preload Optimizer page and the parent exclusions of Cloudflare Edge Images use the same matching.
- Lazy Load: Leading Images set to 0 now lazy loads every image. Before, Turbo still kept 2 images eager, or 4 on shop and category pages.
- Lazy Load: An image that you exclude, or that your theme already gives a high priority, no longer uses a Leading Images slot. The slots now go to the images that need them.
- Lazy Load: Responsive images with WebP or AVIF versions (picture elements) that load at once now keep those versions. Before, the browser loaded the fallback image, which is usually larger.
- Preload: Direct Selector rules under Fetchpriority Selectors now work. Before, a rule with a dot or a hash sign never matched. High applies to the first matching image, and Lazy Load keeps that image eager. Low and Auto apply to every matching image, link or script.
Note: Selectors now match a whole class name or ID only. A saved selector such as footer no longer matches the class site-footer, so use the full class name. In Fetchpriority Selectors, a name without a dot or a hash sign now matches a class only, not other text in the tag such as a file name.
Learn more
Cart Aware Caching keeps your store fast for shoppers with items in their cart
The new Cart Aware Caching setting serves cached pages to shoppers with items in their cart and refreshes their cart after the page loads. Cloudflare Edge Cache connects again on Free plans, and a guest's CommerceKit wishlist no longer goes into the cache.
Action needed: If you use the wishlist of the CommerceKit plugin, click Purge All Cache in the CG Turbo menu on the WordPress toolbar after the update. Until then, pages that Turbo cached before the update can show the wishlist state of one guest to other visitors.
New
- Cache Rules: Logged-out shoppers with items in their cart now get cached home, shop, category and product pages with the new Cart Aware Caching setting, so the store stays fast for the shoppers closest to a purchase. Turbo then refreshes the cart count, total and mini-cart in the header, and Cart, Checkout and My Account stay uncached.
- Cache Rules: The Cart Aware Caching card shows the status of each cache layer that your store uses. When a layer is out of date, the card tells you what to do, for example apply the new Nginx snippet and reload Nginx.
New setting: Cart Aware Caching is on the Cache Rules tab of the Settings page, and it is off by default. It needs WooCommerce and Page Cache or Cloudflare Edge Cache, and turning it on purges the full cache.
Note: With Cart Aware Caching and Cloudflare Edge Cache on, Cloudflare no longer skips the cache for every WooCommerce cookie, only for the ones that Turbo knows. If another plugin sets a cookie that starts with
woocommerce_and changes your pages, add that cookie under Custom Patterns in Cookie Bypass Patterns.
Improved
- Page Cache: For developers: the
X-CG-Cache-Bypassheader now gives fixed cookie reasons, such ascookie:customandcookie:cart_session, and no longer shows your custom bypass patterns. - Cloudflare Edge Cache: When a Transform Rule of another site or tool in your Cloudflare zone uses a function that your plan does not allow, Cloudflare also refuses the Turbo rules. The error message now names those rules, so you can update or delete them in Cloudflare and then click Sync rules.
- Global: Turbo is now compatible with WooCommerce 11.1.
Fixed
- Page Cache: With the Apache/LiteSpeed delivery method, a change to a cache setting, such as a cookie bypass pattern or a path exclusion, now updates the Turbo rules in
.htaccessat once. Before, the old rules stayed in use until you installed the rules again. - JavaScript: The PayPal button on product pages now works with Delay JS in Delay All mode and the reCAPTCHA check of the WooCommerce PayPal Payments plugin. Before, the button failed with a "jQuery is not defined" error.
- Cloudflare Edge Cache: On a Cloudflare Free plan, you can connect Edge Cache again, and Repair missing rules works again. Connected stores need no action, because Turbo updates its Cloudflare rules by itself after the update.
- Cloudflare Edge Cache: Links with tracking parameters, such as
utm_source, now keep the other parameters intact, such as the sort order or a product filter. Before, a tracking parameter between two other parameters could join them, so shoppers saw the default sort order or lost a filter. - Cloudflare Edge Cache: Cloudflare rule health now shows the current state of your rules right after an update, not up to six hours later. When no rule is missing, Repair missing rules now checks your rules and shows the result.
- Global: A guest's wishlist state from the CommerceKit plugin no longer goes into the page cache or the Cloudflare edge cache. Before, other visitors could see the wishlist buttons of that guest on a cached page.
Learn more
Turbo now keeps the Cloudflare rules of each site separate
Each site now changes only its own Cloudflare rules, and a staging copy no longer changes your live store. This release also fixes product badges, the price filter and variation images.
New
- Cloudflare Edge Cache: A new rule health panel shows whether your Cloudflare rules are in place. Verify rules checks them without changing them, and Repair missing rules recreates only the rules that are missing.
- Cloudflare Edge Cache: WordPress Site Health (Tools > Site Health) now also checks the Cloudflare rules of Turbo.
- Status: The Cloudflare Edge Status card now also shows the health of your Cloudflare rules.
Improved
- Cloudflare Edge Cache: When you turn Cloudflare Edge Cache on or off, sync your rules or disconnect, Turbo now shows the progress and the real result.
Fixed
- CSS: Product badges of the CommerceKit plugin and out-of-stock notices of the Shoptimizer theme now stay in place before the shopper interacts with the page. Before, Trim Styles could remove their styles on some category pages.
- JavaScript: The WooCommerce price filter now shows its styled slider as soon as the page loads. Before, with Delay JS on, shoppers saw two plain price fields until they interacted with the page.
- Cloudflare Edge Images: On variable products, the product gallery now updates correctly when a shopper chooses or clears a variation. Before, Turbo could change a WooCommerce gallery script and cause a JavaScript error.
- Cloudflare Edge Cache: When several sites share one Cloudflare zone, each site now changes only its own Turbo rules. Before, one site could overwrite the Turbo rules of another site in the same zone.
- Cloudflare Edge Cache: A copy of your store on another domain, such as a staging site, no longer changes the Cloudflare rules of your live store or purges its cache. Turbo pauses Cloudflare changes on the copy and shows the reason on the Cloudflare Edge Cache page.
- Cloudflare Edge Cache: With Cloudflare Edge Cache off, Turbo no longer adds its Cloudflare rules again when you save Cache Rules settings or reactivate the plugin.
Note: You do not need to reconnect Cloudflare after the update: Turbo checks your connection and keeps it when your rules are healthy. If the Cloudflare Edge Cache page shows Connection paused, it tells you why.
Learn more
Click Queue is now on by default, so early clicks are not lost on new stores
On new stores, Turbo now keeps the clicks that shoppers make while delayed JavaScript loads, and replays them when the scripts are ready. Existing stores keep their Click Queue setting.
Improved
- JavaScript: On new stores, clicks that shoppers make while delayed JavaScript loads are no longer lost, because Click Queue is now on by default. Click Queue also turns on when you reset the JavaScript settings.
- JavaScript: For developers: a theme or plugin can now keep its ready controls, such as a menu or cart button, out of Click Queue. It cancels the
cgturbo-before-queue-activationevent, and the control then responds to the first click at once.
Note: Existing stores keep their Click Queue setting. To change it, select Delay JS on the JavaScript Optimizer page, then use Enable Click Queue in Delay Settings.
Stable menus and working first taps while delayed styles and scripts load
Menus and sticky headers now stay stable while delayed styles load, and the first tap on a menu works with Click Queue. Trim Styles no longer leaves parts of the page without styles.
New
- CSS: For developers: the new
cgturbo_local_stylesheet_mappingsfilter maps stylesheet URLs to folders on your server. Trim Styles can then read stylesheets that a CDN serves.
Fixed
- CSS: With Delay Original Stylesheets, menus, sticky headers and other interactive parts of the page now stay stable when the full styles load. Turbo now applies all delayed stylesheets at the same time, then lets these parts adjust to the new layout.
- CSS: With Trim Styles, a stylesheet that Turbo cannot read on your server, for example one that an offload plugin stores in the cloud, now loads at once. Before, Turbo delayed it without its styles in the Used CSS, so parts of the page could show without styles.
- CSS: With Trim Styles and the Complianz plugin, a cookie banner that a shopper dismissed now stays hidden on the next pages. Before, it could show again until the full styles loaded.
- JavaScript: With Click Queue on, the first tap on a menu button, an add-to-cart button or another control now works when the delayed scripts load. Normal links now open at once, and quick repeat taps on the same control count as one.
Learn more
Delay JS and Defer JS now run scripts in the right order
Turbo now runs delayed and deferred scripts in the right order, so fewer features break. Page Cache now updates your WordPress configuration for you, and Elementor pages keep their styles when you save Turbo settings.
New
- JavaScript: If your store still uses Curated exclusions for Delay JS, a new Legacy Curated mode card lets you switch to Delay All or Defer Standard in one click. Curated keeps working until you switch, but you can no longer select it.
- JavaScript: For developers: the new
cgturbo_js_compatibility_dependenciesfilter tells Turbo about a script dependency that WordPress does not know about.
Improved
- Page Cache: Less setup: turning Page Cache on now adds
WP_CACHEtowp-config.php, and turning it off removes it. If Turbo cannot change the file, Page Cache stays off and a message tells you what to do. - JavaScript: Defer Inline Scripts is now on by default for new setups, so inline scripts run in the right order with the other deferred scripts. When you switch to Defer JS, Turbo now also selects Standard and turns on Defer Inline Scripts.
- Cloudflare Edge Cache: Turning on Cloudflare Edge Cache no longer asks you to set
WP_CACHE, because Edge Cache does not need it. - Global: WordPress now stops you from activating Turbo on a WordPress version older than 6.7.2. Turbo has needed WordPress 6.7.2 or later since version 0.9.0.
- Global: Saving Turbo settings no longer empties the WordPress object cache or the caches of other plugins, so your store stays fast after a change.
- Global: For developers: Turbo no longer fires the
cgturbo_clear_third_party_cachesaction when you save settings.
Fixed
- Page Cache: Turbo no longer adds a second
WP_CACHEdefinition whenwp-config.phpalready has one, which caused PHP warnings. A notice now asks you to set the existing definition totrue. - JavaScript: With Delay JS or Defer JS on, each script now runs after the scripts that it needs, in the same order as on the page. Before, some features could break with errors such as
wp is not defined. - JavaScript: When you exclude a script from Delay JS or Defer JS, Turbo now also loads the scripts that it needs, such as jQuery, at once. Before, the excluded script could run before them and fail.
- JavaScript: Pages now keep their layout when Defer JS and Defer Inline Scripts are on together with Delay Original Stylesheets.
- Global: With the Elementor plugin, pages keep their styles after you save Turbo settings. Before, each save deleted the Elementor CSS files that cached pages still used.
- Global: When the Elementor plugin clears its CSS files, or you save an Elementor template, Turbo now purges all its caches so that pages get the new styles.
Learn more
Turbo no longer causes PHP notices after activation or on PHP 8.5
This update stops two notices that Turbo caused: one after you activated Turbo on a WooCommerce store, and one on PHP 8.5 when admins viewed pages with the admin bar.
Fixed
- Global: Turbo no longer causes the WordPress notice "Translation loading for the woocommerce domain was triggered too early" after you activate it. Before, stores with WooCommerce and
WP_DEBUGon showed or logged this notice. - Global: On PHP 8.5, the Turbo cache controls in the admin bar no longer cause a "Using null as an array offset is deprecated" notice. Before, each page view by a logged-in admin added this notice when Page Cache or Cloudflare Edge Cache was on.
Images added by Load More and infinite scroll now appear, plus three Weglot fixes
Images that your store adds after the page loads, for example with a Load More button, now appear. This release also fixes three problems with the Weglot plugin, and Turbo is now compatible with WordPress 7.1.
Action needed: Check that Dynamic Content Detection is on in the Lazy Load Optimizer page if your store adds products after the page loads, for example with a Load More button. Then purge all caches with CG Turbo > Purge All Cache in the admin bar, so that cached pages get these fixes.
Improved
- Lazy Load: Dynamic Content Detection is now on by default for new installations. Existing stores keep their saved setting.
- Global: Turbo is now compatible with WordPress 7.1.
Fixed
- Page Cache: With the Weglot plugin, shoppers on a translated page now get the translated text from the cache. Before, cache warming could store the page in the original language under the translated URL.
- Page Cache: With the Weglot plugin, Turbo no longer shows the notice that
advanced-cache.phpneeds to be updated again and again. - JavaScript: With the Weglot plugin, translations now work when Delay JS is on. Turbo no longer delays the Weglot script.
- Lazy Load: Images that your store adds after the page loads, for example with a Load More button or infinite scroll, now appear when Dynamic Content Detection is on. Before, the setting had no effect, so these images could stay as empty placeholders.
Learn more
Support for the Weglot plugin, exclusions for category archives, and an Elementor fix
Turbo now keeps a separate cache for each Weglot language, and you can exclude category, tag and other archive pages from optimizations. This release also fixes Elementor pages with curated Delay JS and works alongside the WordPress.com page cache.
Action needed: If your store is on WordPress.com hosting, turn off Page Cache on the Page Cache page. WordPress.com already caches your pages, and the other Turbo optimizations keep working.
New
- Global: With the Weglot plugin, each language now gets its own cached pages, so shoppers see every page in their language. When you update a page, Turbo now also purges and warms its translated pages.
- Global: With the automatic redirect of the Weglot plugin on, pages without a language in the URL now skip the cache. Weglot can then still send each visitor to their browser language.
- Global: You can now turn off Turbo optimizations for one category, tag or product category archive. Edit the term in the WordPress admin and use the CG Turbo box, which has the same options as on posts, pages and products.
- Global: For developers: the new
cgturbo_is_optimization_excludedfilter turns off an optimization for any request, for example an author or search archive. Thecgturbo_exclusion_taxonomiesfilter sets which taxonomies get the CG Turbo box.
Note: Weglot support works when your languages use subdirectories of your domain, such as
/fr/. Pages of languages on a separate domain are not cached, and the Status page lists these languages.
Improved
- Page Cache: Pages that ask not to be cached, for example with
DONOTCACHEPAGEor aCache-Control: no-storeheader, now stay out of Page Cache and Cloudflare Edge Cache. This keeps pages that other plugins mark as private out of the cache. - Page Cache: When another cache plugin, such as the WP Rocket plugin, controls
advanced-cache.php, the Page Cache page now names it and offers a Replace with CG Turbo button. After you replace the file, the WP Rocket plugin no longer puts its own file back. - Page Cache: On WordPress.com hosting, Turbo now leaves the host's page cache in place, and the Page Cache page tells you to turn off Page Cache. Purge All Cache in Turbo now also clears the WordPress.com cache.
- Global: Exclusions in the CG Turbo box of the page that you set as your Posts page now apply to your main blog page.
Fixed
- CSS: Excluding a page from Delay Styles now keeps Used CSS on for that page. Before, it turned off both.
- JavaScript: With Delay Behavior set to Use Curated Exclusions, Elementor widgets now load at once. Turbo now keeps all the scripts that the Elementor, Elementor Pro and Pro Elements plugins need out of Delay JS.
- JavaScript: Excluding a page from Delay JS now keeps Defer JS on for that page, and the other way round. Before, either exclusion turned off both.
- Preload: With Lazy Load on, Critical Images now also preloads images inside a
<picture>element, such as WebP images. This can improve your Largest Contentful Paint (LCP). - Global: Purge All Cache in the WordPress admin bar now also works on admin screens. Before, it only worked when you viewed your store.
- Global: Browser translation tools, such as Google Translate, no longer crash the Turbo admin pages. These pages now stay in their original language.
Faster cached pages on Apache and LiteSpeed servers, and no more 403 errors
With the Apache or LiteSpeed serve mode, the web server now serves every cached page directly, without 403 errors. Stores with a separate domain for each language now show the correct language, and Turbo is now compatible with WooCommerce 11.0.
Action needed: If the Serve mode on the Page Cache page is Apache/Litespeed (
.htaccess), click Install Rules once after the update. If it is Nginx, copy the new Nginx Snippet into your server configuration.
Improved
- Page Cache: For developers: the
X-CG-Cache-Sourceresponse header now showslitespeedwhen a LiteSpeed server serves the cached page. It showsphp-wpwhen WordPress built the page and saved it to the cache. - Global: Turbo is now compatible with WooCommerce 11.0.
Fixed
- Page Cache: With the Apache/Litespeed (
.htaccess) serve mode, visitors no longer get a "403 Forbidden" error instead of a cached page. - Page Cache: With the Apache/Litespeed (
.htaccess) serve mode, the web server now serves all cached pages directly, so pages load faster. Before, only the homepage was served this way, and the other pages went through PHP. - Page Cache: On stores with a separate domain for each language, for example with the WPML plugin, visitors on the other domains now see pages in the correct language. Before, they could get a cached page of the main domain.
- Page Cache: With the Apache/Litespeed or Nginx serve mode, more visitors with tracking cookies, such as the Facebook click cookie, now get the fast web server cache. Before, some cookie values matched the bypass cookie patterns by chance.
- Page Cache: Verify Configuration no longer shows a false warning that the Apache rules are not installed, right after you install them.
- Page Cache: When you deactivate Turbo, it now removes its rules from the
.htaccessfile.
Learn more
Images with Cloudflare Edge Images now download once, and at the right size
With Cloudflare Edge Images on, Critical Images now preload the same image that the page shows, and lazy loaded images get responsive sizes. Images from the CommerceKit plugin now load through Cloudflare Edge Images too.
Improved
- Cloudflare Edge Images: With the CommerceKit plugin, product gallery images, gallery video posters and Sticky Add to Cart images now load through Cloudflare Edge Images, so shoppers download smaller files. This also applies to the images that load when a shopper picks a variation.
- Cloudflare Edge Images: For developers: an image that an exclusion skips now gets the
cgturbo-cf-excludedclass, so you can see why it loads from your server. - Global: The Turbo pages for each feature, such as Page Cache and Lazy Load Optimizer, now show a loading message while their settings load. After the first page, the other pages open without a wait.
Fixed
- Preload: With Cloudflare Edge Images on, Critical Images now preload the same image and sizes that the page shows, so the browser downloads the image once. Before, it also downloaded the original image from your server, which slowed down your Largest Contentful Paint (LCP).
- Preload: Parent Selector rules under Fetchpriority Selectors now work with an ID, such as
#hero. A class now matches the full class name only, so.herono longer also matches.hero-banner. - Preload: When you view your store logged in, avatars in the WordPress toolbar no longer take the Critical Images slots.
- Cloudflare Edge Images: Lazy loaded images now get responsive sizes, so phones download a smaller file. Images also keep their largest WordPress size, so high-resolution screens show a sharp image.
- Global: Purge All Cache, Purge This Page and the Edge status in the CG Turbo menu on the WordPress toolbar now work with every theme. Before, with some themes, the purge links did nothing and the Edge status did not load.
Learn more
Cloudflare Edge Cache fixes for GTranslate stores, account API tokens and sitemaps
Cloudflare Edge Cache now works on GTranslate stores with many languages, accepts Cloudflare account API tokens, and updates its Cloudflare rules for you after a Turbo update. This release also fixes sitemap caching and several status messages.
Improved
- Page Cache: For developers: the new
cgturbo_wp_config_pathsfilter sets where Turbo looks forwp-config.php, for hosts with an unusual folder layout. - Cloudflare Edge Images: Product gallery images now get Cloudflare Edge Images by default, so shoppers download smaller gallery images. If Skip WooCommerce Gallery is on in your settings, turn it off to get this.
- Cloudflare Edge Images: The image domains of another CDN now go in Allowed Image Source Domains, under the new Enable Custom CDN Domains (Advanced) toggle. The help text now explains how this list differs from the Image Transformation Domain.
- Cloudflare Edge Cache: When a Turbo update changes the Cloudflare rules, Turbo now updates the rules in Cloudflare for you. You no longer need to click Sync Rules after an update.
Fixed
- Page Cache: The badge next to Enable Page Cache now shows the real state of the drop-in: installed, missing, update available or conflict. Before, it looked only at
WP_CACHE, so it could be wrong. - Page Cache: Turbo no longer shows a wrong
WP_CACHEwarning just after activation. Before, the warning showed even when Turbo had already addedWP_CACHEtowp-config.php. - Cloudflare Edge Images: Images now load when you enter the Image Transformation Domain as a domain name only, without https. Before, Turbo made broken image URLs from such a domain.
- Cloudflare Edge Cache: Cloudflare Edge Cache now works on stores that use the GTranslate plugin with many languages. Before, the Turbo rules could grow too long, and Cloudflare refused them.
- Cloudflare Edge Cache: XML sitemaps, feeds,
robots.txtand JSON files now stay up to date. Before, the Turbo static file rule could keep them in the Cloudflare cache for up to a year. - Cloudflare Edge Cache: You can now connect with a Cloudflare account API token, and spaces around a pasted token no longer break the connection. Before, only user API tokens worked.
- Activity: The Event Log now shows debug entries only when Enable Debug Logging is on and the Debug Log Level is Debug. Before, debug entries filled the log.
- Status: The Cloudflare Edge card no longer says Not connected when your Cloudflare API token only lacks the Analytics: Read permission. The Status and Activity pages now tell you to add that permission to show edge metrics.
- Global: When Turbo purges a file URL, such as a sitemap, or a URL with a query string, it now clears the right cached copy. Before, Turbo added a slash to the end of the URL, so the old copy stayed in the cache.
Learn more
Turbo now works with the GTranslate plugin
Turbo now keeps the GTranslate language switcher working and does not cache translated pages. This release also fixes blank product gallery thumbnails with Delay JS on.
Action needed: If the GTranslate plugin serves your translations from language subdirectories or subdomains, update your cache rules once. Click Sync Rules on the Cloudflare Edge Cache page, and with an Apache or Nginx serve mode, click Install Rules or copy the new Nginx snippet on the Page Cache page.
New
- Status: A new GTranslate row on the Status page shows whether Turbo's safeguards for the GTranslate plugin are on.
- Global: Turbo is now compatible with the GTranslate plugin. The language switcher works with Delay JS and Defer JS on, and Turbo does not cache translated pages, so shoppers always get the right language.
Fixed
- JavaScript: With Delay JS on, WooCommerce product gallery thumbnails now show at once. Before, they could stay blank until the shopper interacted with the page.
- JavaScript: All delayed scripts now run, even when one of them does not finish loading. Before, one stalled script could stop the scripts after it.
- Status: Copy Diagnostics now lists plugins that are network active on a multisite network as active. Before, the report showed them as inactive.
Learn more
Fixes for the Page Cache, product galleries with Delay JS, and CSS cache buttons
With Delay JS on, the WooCommerce product gallery now shows at once and interactive blocks work. Some pages with lazy loaded images now get cached, and the CSS cache buttons work on hosts with a strict firewall.
New
- JavaScript: For developers: the new
cgturbo_core_gallery_exclusionsfilter sets which WooCommerce product gallery scripts Delay JS does not delay.
Fixed
- Page Cache: With Image Lazy Loading on, pages that have an image with a width or height such as
width="auto"now get cached. Before, an error stopped Turbo from storing these pages. - CSS: The Clear Used CSS Cache button and the Clear buttons in the Parsed CSS Cache table now work on hosts with a strict firewall. Before, some hosts blocked these buttons with a 403 error.
- JavaScript: With Delay JS on, the standard WooCommerce product gallery and its thumbnails now show at once on product pages. Before, with Delay All Scripts, they appeared only after the shopper interacted with the page or the delay timeout ended.
- JavaScript: Interactive WordPress blocks, such as the Accordion block, now work for logged-out visitors when Delay JS is on.
Stronger security for Turbo, and diagnostics that include your settings
This release makes Turbo more secure and adds your settings to the diagnostics, with your Cloudflare token hidden. Scripts that run WP-CLI commands which purge or delete data must now confirm them.
Action needed: WP-CLI commands that purge all caches, import settings or delete data now ask for confirmation. If a script runs
wp cgturbo purge,purge-and-warm,log-clear,import-settings,reset-cf-connection,edge-cache delete-rules,page-cache dropin-uninstallorpage-cache apache-uninstall, add--yes, or the command stops and does nothing.
Note: Turbo now needs WordPress 6.7.2 or later and WooCommerce 10.5 or later.
New
- Cloudflare Edge Cache: If Turbo can no longer read your saved Cloudflare API token, an admin notice now asks you to enter it again, so Cloudflare Edge Cache does not stop without a warning. This usually happens after someone changes
AUTH_KEYorSECURE_AUTH_KEYinwp-config.php. - Status: Copy Diagnostics now also includes your Turbo settings, so support can find the cause of a problem faster. Turbo hides your Cloudflare API token and zone details, and messages that you send from the Help page include the same settings.
Improved
- Cloudflare Edge Cache: Turbo now never saves your Cloudflare API token as plain text or with a weak key. When your server cannot encrypt the token, Turbo shows an error that tells you how to fix it, for example with the
CGTURBO_CF_API_TOKENconstant inwp-config.php. - Settings: For developers: the cache warmer now only warms pages on your own domain. It skips other URLs that the
cgturbo_warm_urlsfilter adds, and logs each one on the Activity page. - Global: Turbo now accepts plugin updates only from commercegurus.com over HTTPS, which protects your store from fake update packages.
- Global: Turbo now hides API tokens, license keys and passwords in its debug log, and blocks direct web access to its log files on Apache servers.
- Global: For developers:
wp cgturbo import-settingsnow ignores the Cloudflare API token and zone, and the option that deletes all Turbo data on uninstall. Turbo shows a warning for each value that it ignores. - Global: Turbo is now compatible with WordPress 7.0.
- Global: Turbo is now compatible with WooCommerce 10.7.
Fixed
- Page Cache: When Turbo turns on
WP_CACHEinwp-config.php, the file now keeps its owner and permissions. - Activity: The downloaded log is now a plain text file with one event per line, so you can read it and send it to support. Before, it was one long line of quoted text.
Learn more
More admin messages now use the full plugin name, CommerceGurus Turbo
A small update to the admin wording. Turbo works on your store as before, and you do not need to do anything.
Improved
- Global: More admin messages now use the full plugin name, CommerceGurus Turbo, for example on the Dashboard and the Settings page. Nothing changes in how Turbo makes your store faster.
Turbo now requires PHP 8.3 or later
This release raises the minimum PHP version for Turbo to 8.3. Check your PHP version in Tools > Site Health > Info before you update.
Action needed: Turbo now requires PHP 8.3 or later. If your store runs an older PHP version, ask your host to upgrade PHP before you update Turbo.
The Status page now shows when your site connects through a whitelisted domain
This release makes the license status clearer. Sites that connect through a whitelisted domain now see that on the Status and Help pages, not an active subscription.
Fixed
- Status: The License card now shows when your site connects through a whitelisted domain, and the Help page says the same. Before, the card showed an active subscription for these sites.
Safer Page Cache setup and plugin activation
Turning on Page Cache no longer risks breaking your WordPress configuration file. Activating Turbo now also makes Page Cache changes only when Page Cache is on.
Fixed
- Page Cache: Turning on Page Cache no longer breaks
wp-config.phpon some sites. Turbo now adds itsWP_CACHEline on a separate line, so the next line of the file stays intact. - Page Cache: With Page Cache off, activating Turbo no longer adds
WP_CACHEtowp-config.phpor installs theadvanced-cache.phpfile. Turbo now makes these changes only when Page Cache is on. - Global: After you upload Turbo as a zip file in WordPress, the Activate Plugin button now activates Turbo. Before, the button could point to a different file in the Turbo package.
The Dashboard intro video now shows its correct length
This small update corrects the length shown on the intro video on the Dashboard. You do not need to do anything after the update.
Fixed
- Dashboard: The intro video on the Dashboard now shows its correct length, 3:14.
No more false output buffer errors on file downloads, and a new intro video
Turbo no longer logs false output buffer errors when customers download files that they bought. The Dashboard has a new intro video, and its documentation and changelog links now open the Turbo pages.
New
- Dashboard: The Dashboard has a new Turbo intro video, with captions on.
Fixed
- Dashboard: The documentation and changelog links on the Dashboard and the Help page now open the Turbo pages. Before, the changelog link opened the Shoptimizer changelog.
- Activity: Turbo no longer logs false output buffer errors for pages with query strings that bypass the Page Cache, such as downloads of files that customers bought. Before, these errors could also show an output buffer conflict warning in the WordPress admin and on the Status page.
Learn more
One-click Turbo updates for stores connected to CommerceGurus
Turbo now checks your CommerceGurus subscription, so connected stores can update Turbo with one click. Your license does not change which Turbo features work.
New
- Status: The License & Updates card now shows your connection, your subscription and the latest Turbo version.
- Status: When Turbo cannot reach CommerceGurus, the License & Updates card shows how old the saved license status is. After 48 hours, Turbo no longer counts the site as connected until a check succeeds.
- Global: Turbo now checks your CommerceGurus subscription, so connected stores can update Turbo with one click on the WordPress Plugins screen. Your license does not change which Turbo features work.
- Global: When an update is available and your site is not connected, the Plugins screen now says that one-click updates need a connected CommerceGurus account. It links to the Turbo Help page.
Note: If the Status page shows "Not connected", use the "Connect at commercegurus.com" link on the License & Updates card.
