Replaced the Table of Contents' thick rounded accent treatment with a quiet square hairline frame while retaining the title divider, active-state emphasis, semantic list styles, and theme inheritance.
Added a zero-specificity 1.5rem block-end spacing fallback to every rendered .acf-block; existing theme and block margins continue to take precedence.
Commits
Release 2.9.5: refine block spacing and TOC (803931a)
Gave the theme-native Table of Contents a restrained currentColor frame, stronger leading edge, title divider, and modest inset spacing without restoring plugin backgrounds, hard-coded colors, fixed typography, or custom markers.
Read full notes17 changes
What's Changed
Changed
Gave the theme-native Table of Contents a restrained currentColor frame, stronger leading edge, title divider, and modest inset spacing without restoring plugin backgrounds, hard-coded colors, fixed typography, or custom markers.
Optional semantic fallback styles for minimal themes. Settings → ACF Blocks License → Theme Compatibility Styles can load a small zero-specificity stylesheet for common semantic HTML inside ACF blocks. It is disabled by default and loads in…
Read full notes25 changes
What's Changed
Added
Optional semantic fallback styles for minimal themes. Settings → ACF Blocks License → Theme Compatibility Styles can load a small zero-specificity stylesheet for common semantic HTML inside ACF blocks. It is disabled by default and loads in both the editor and frontend only when enabled.
Every rendered acf/* block now exposes a predictable .acf-block class for theme authors, whether or not the fallback stylesheet is enabled.
Changed
The Table of Contents block now inherits its visual design from the active theme. Removed plugin-defined backgrounds, colors, borders, radii, fixed type sizing/casing, link decoration, hover fills, spacing, custom markers, dark-mode overrides, and scrollbar styling.
Numbered, bulleted, and plain list modes remain explicit. Ordered and unordered lists use native theme-aware markers, while plain lists stay marker-free.
The Accordion block is now entirely theme-native. Its native <details>/<summary> behavior needs no plugin stylesheet, so the CSS asset and metadata references were removed.
Tabs now ship only structural, state, accessibility, responsive, and style-mode rules. Removed the plugin palette, light/dark overrides, opacity system, decorative fills, transition effects, container spacing, and forced typography while retaining all four tab treatments and panel switching.
Section block CSS now covers structure only. Removed inactive default palette, dark-mode, width, spacing, and container rules. The template now emits its scoped wrapper and alignment classes so user-selected video and overlay backgrounds layer correctly without imposing a design.
Fixes the GT Link inserter for the core Button block while preserving the Button block's native link settings.
Read full notes5 changes
= 1.7.0 = = 1.7.1 = Fixes the GT Link inserter for the core Button block while preserving the Button block's native link settings.
What's Changed
Fixed The GT Link toolbar now works with the core Button block by updating the Button's native URL and rel attributes.
Improved Rich text and Button controls now share the same GT Link search popover, normalize rel attributes, and preserve noopener for buttons that open in a new tab.
Made Redis object-cache writes request-local immediately, changed add() and replace() to atomic Redis NX/XX operations, and honored forced backend refreshes. Owned outdated object-cache drop-ins now update atomically on plugin boot without…
Read full notes6 changes
Fixed
Made Redis object-cache writes request-local immediately, changed add() and replace() to atomic Redis NX/XX operations, and honored forced backend refreshes. Owned outdated object-cache drop-ins now update atomically on plugin boot without touching foreign drop-ins, then clear the exact alloptions, notoptions, and cron option-cache entries.
Added a Doctor warning for materially overdue scheduled events when request-driven WP-Cron is disabled. The warning provides a host-specific five-minute external flock runner and does not change DISABLE_WP_CRON.
Fixed wp gt-performance cloudflare purge, which previously fell through to Cloudflare rule synchronization without purging anything. It now supports a full-zone purge or one exact --page-url, reports Cloudflare API failures, and exits non-zero on invalid input.
Rejected unknown cache, queue, Cloudflare, database, and fleet actions before constructing services or performing work. Empty or malformed explicit URLs can no longer degrade into unintended full purges, nonnumeric queue limits now fail instead of processing an arbitrary batch, and action-specific options are no longer silently ignored.
Corrected the WP-CLI option documentation for action-based command families so WP-CLI can validate and display their positional actions consistently.
The migrator now strips the retired FAQ-schema flag from existing content. 2.9.1 made acf_accord_enable_faq_schema inert; this removes it (and its _acf_accord_enable_faq_schema field reference) from acf/accordion blocks when the migrator…
Read full notes21 changes
What's Changed
Changed
The migrator now strips the retired FAQ-schema flag from existing content. 2.9.1 made acf_accord_enable_faq_schema inert; this removes it (and its _acf_accord_enable_faq_schema field reference) from acf/accordion blocks when the migrator runs, so old posts no longer carry a key nothing reads.
Removals are reported under their own Retired FAQ schema flag removed category in the scan breakdown and per-post badges, rather than being folded into "Accordion fields fixed".
Notes
Expect a one-time jump in the migrator's affected-post count. Posts whose only issue is the stale flag now show up as needing migration. Rendering is unchanged either way — this is a data cleanup, not a fix for a visible bug, so it is safe to defer.
Accordion blocks with nothing to clean are left byte-identical and are not rewritten, so no post gains a revision for no reason.
Commits
2.9.2: strip retired FAQ schema flag from existing content (b2b86b5)
The Accordion block itself is unchanged — same markup, same styles, still searchable by "FAQ" in the inserter.
Read full notes20 changes
What's Changed
Removed
FAQ schema dropped from the Accordion block. Google no longer supports FAQ rich results, so acf/accordion no longer emits FAQPage JSON-LD and the "Enable FAQ Schema" field is gone from the block settings.
Existing posts need no migration: blocks that still carry acf_accord_enable_faq_schema set to 1 render normally, and the stored value is ignored — no schema is printed.
The block migrator no longer writes acf_accord_enable_faq_schema into blocks it converts.
Commits
2.9.1: drop FAQ schema from accordion block (20c57e7)
Standalone and fullscreen form pages no longer fall back to browser-default controls when the global or per-form built-in theme is disabled.
Standalone routes now always load the complete Core Forms design baseline and generated theme-token overrides because these pages do not render the active WordPress theme.
Changed
The default form theme now depends on the core form stylesheet so its layout primitives are always present.
Added regression coverage for standalone asset loading.