[En attente du retour de l'utilisateur] 1.6.28 regression: dynamic toolset-blocks-styling CSS not generated

Hi Christopher, reporting back with a root cause.

TL;DR: it's a conflict with WP Rocket's JavaScript optimization, not a pure Toolset regression. On Toolset Blocks 1.6.27 the block CSS is delivered via JavaScript at runtime, and WP Rocket's 'Minify JavaScript files' and 'Load JavaScript deferred' EACH independently break that delivery (I tested every toggle combination). Note: the Toolset-side change was introduced somewhere between 1.6.13 and 1.6.27 — I skipped the versions in between, so I can't pin it to a single release; please don't read this as '1.6.28 introduced it'.

The mechanism, from the 1.6.27 source: per-block responsive CSS (e.g. the Grid block's grid-template-columns media queries) is base64-encoded by PHP into hidden <div class="tces-js-style-encoded"> elements, with an inline <script class="tces-js-move-to-head"> that calls toolsetCommonEs.styleToHead() to decode them into <style id="toolset-blocks-styling"> in <head> (see common-es/server/Block/Style/Loader.php and common-es/public/toolset-common-es-frontend.js). The static style.css isn't enqueued normally either — blocks/server/FrontendAssets.php prints its own lazy-load inline script (IntersectionObserver on [class^='tb-']) that injects the stylesheet on window load + scroll/intersection. When that JS chain breaks, no grid CSS is applied: the artist grid collapses to a single column with no card backgrounds and the style tag never appears.

What I ruled out: the sandbox test confirmed 1.6.27 works on a clean install; deactivating all non-Toolset plugins isolated WP Rocket as the conflicting plugin; 'Delay JavaScript execution' was already disabled and is not a factor; no single CSS option (Minify CSS, Optimize CSS delivery) has any effect. Excluding Toolset's external script files from WP Rocket's minify/defer exclusion lists did NOT help, which points at the inline scripts being mangled rather than the enqueued files.

Current workaround: WP Rocket stays fully active with JS minification ON, using the "Excluded Inline JavaScript" patterns toolsetCommonEs and toolset-blocks; only JS combining and JS deferral remain disabled. Grid renders correctly on Toolset Blocks 1.6.27 with this configuration.

It would be great to get an official compatibility fix — e.g. making the style injection resilient to minification/deferral (the move-to-head script silently no-ops when toolsetCommonEs is undefined at DOMContentLoaded), or documenting the exact WP Rocket exclusion. Happy to test a dev build.

Hi Christopher,

I can't install WP Rocket on the sandbox because there is no free version, and I'm not willing to use one of my paid license's site slots on a third-party sandbox.

To reproduce it, use a clean WordPress install with Toolset Blocks 1.6.27 and a WordPress Archive containing a Toolset Grid block, for example 4 columns on desktop and 2 on phone. In WP Rocket > File Optimization, enable "Minify JavaScript files," while leaving "Load JavaScript deferred" and "Combine JavaScript files" off. Deferral also breaks it independently.

The minifier mangles Toolset's runtime CSS-injection inline scripts: the <script class="tces-js-move-to-head"> call to toolsetCommonEs.styleToHead() that decodes the base64 block CSS into <style id="toolset-blocks-styling">, plus Toolset's lazy-load inline script for style.css. The style tag then never appears, and the grid collapses to one column with no card backgrounds.

Hi Christopher, I've narrowed this down. The issue does not reproduce on the sandbox because the sandbox is not running the same code as the 1.6.27 release on my site. The sandbox's "Toolset Blocks 1.6.27" is the Views codebase (main file wp-views.php) and ships no common-es library — so it prints <style id="toolset-blocks-styling"> server-side into <head> and never uses the runtime path. The genuine 1.6.27 release (downloaded from my Toolset account) ships common-es and delivers the grid CSS at runtime: base64-encoded <div class="tces-js-style-encoded"> elements plus <script class="tces-js-move-to-head"> calling toolsetCommonEs.styleToHead(). That runtime injection is exactly what WP Rocket 3.23.3.3's "Minify JavaScript files" breaks — with minify on (combine/defer/delay off, no exclusions), the style tag never appears and the grid collapses to a single column. Excluding toolsetCommonEs and toolset-blocks under "Excluded Inline JavaScript" keeps minification working with the grid intact on my site.

So the sandbox as provisioned cannot reproduce this issue — the code path involved doesn't exist in its build. For reference: with WP Rocket active on the sandbox, the test archive renders correctly at 4 columns whether JS minification is on or off; I've left the sandbox with JS minification off.