Repository navigation
ACF Blocks v2.11.3
What's Changed
Fixed
-
Block stylesheets were never cache-busted by a plugin release. Core's
register_block_style_handle()reads$metadata['version']from block.json and falls back tofalse, which makeswp_register_style()stamp the WordPress version onto the URL. Every one of this plugin's block.json-registered handles was therefore versioned by core, not by the plugin: on this siteurl-preview.min.cssshipped as?ver=7.1for WordPress 7.1, and the files are servedpublic, max-age=31536000. The query string is the only thing that can retire a year-long cached copy, so a CSS fix in a plugin release stayed invisible to every reader who had already loaded the page until WordPress itself updated. The 2.11.2 contrast fix was landing this way — correct on disk and at the CDN, still broken in the browser of anyone who had visited before.A
block_type_metadatafilter now setsversiontoACF_BLOCKS_VERSIONfor blocks whoseblock.jsonlives inside this plugin, matching what the plugin's directwp_enqueue_style()calls have always passed. Blocks that other plugins register under theacf/namespace are left alone. Asset URLs now carry the plugin version and change with every release.Sites running GT Performance saw this compounded: its
assetVersionfilter rewritesverwhen it equals the core version, turning?ver=7.1into a stable hash. It was doing its job — hiding the core version — but the versioning underneath was already wrong, and the hash made the staleness harder to spot.
Commits
- 2.11.3: version block.json assets with the plugin, not with WP core (
a91797b) - 2.11.2: fix white-on-white URL Preview button in dark mode (
e40be8e)
Stats
- Commits: 2
- Changes: 11 files changed, 82 insertions(+), 10 deletions(-)
Plugin Info
- Blocks included: 29
- Requires WordPress: 6.0+
- Requires PHP: 7.4+
- Requires: ACF Pro 6.0+ or Secure Custom Fields
Installation
- Download
acf-blocks-plugin-*.zipfrom the assets below - Go to Plugins → Add New → Upload Plugin in WordPress admin
- Upload the zip file and activate