Bricks 2.4 has reached the release candidate stage.
Since beta3, we’ve focused on stability and final refinements across the Builder, Bricks Browser, CSS Sync, forms, WooCommerce, and AI Abilities.
Highlights include a more polished Browser and media workflow, more reliable bi-directional CSS Sync, deferred Cloudflare Turnstile initialization, better management of SVG uploads in custom icon sets, and several smaller Builder workflow fixes.
Translation refresh
We’ve refreshed translations across all 43 bundled locales to provide a more complete, consistent, and natural experience throughout Bricks.
We’ve also removed the .po files from the main release ZIP, reducing its size by around 40%. This makes manual installation easier, particularly on sites with lower file upload limits. This does not affect how translations load in Bricks.
As with any release candidate, we recommend testing Bricks 2.4 RC in a local or staging environment, not on a production site.
Bricks 2.3.12 is a maintenance release with fixes and improvements across WooCommerce, components, Dynamic Data, templates, sliders, custom fonts, and the builder interface. It also restores WooCommerce’s native fallback for inaccessible Thank You pages, preserves quoted echo arguments in Form and Search fields, and improves Related Products, Upsells, and Cross-Sells with equal-height cards and responsive button controls.
This beta brings major improvements to Bricks AI Abilities, remote component libraries, expanded media management in the Bricks Browser, and a native File element. You can also edit custom CSS for a selected class directly in Class Manager and control when individual form actions run.
Improved AI Abilities
For Beta 3, we focused on making AI agents faster, more efficient, and more reliable when working with Bricks, based on testing and feedback from the previous betas.
Agents can work more efficiently across both new and existing sites. Creating or updating design systems, building or importing complete page designs, and making targeted edits now require fewer tool calls. Smaller responses also reduce token usage and the time needed to complete tasks.
HTML/CSS-to-Bricks conversion is also more accurate, helping agents produce better designs across desktop and mobile.
Beta 3 also adds an optional PHP execution ability for workflows the regular Bricks Abilities cannot cover. It lets the connected agent inspect plugins, hooks, scheduled events, logs, and WordPress data, troubleshoot runtime issues, and perform approved configuration or data changes. When enabled through the BRICKS_ENABLE_EXECUTE_PHP_ABILITY PHP constant, it provides full PHP execution access within WordPress, so it is disabled by default and should only be enabled on trusted staging or development sites.
You can now browse and import components from another Bricks installation directly in the Component Manager. Imports include nested component dependencies and referenced global classes, variables, color palettes, and optional images, so the component arrives with the design-system data it needs.
Remote templates now transfer their component dependencies too. Site owners can share templates and components through the same remote access settings as templates, exclude individual components, and review compatibility or naming conflicts before importing.
Media controls (i.e. Audio, Image, Video, SVG) now open the new Bricks Media Browser by default instead of the WordPress media modal. The Media view supports search and filtering, single and bulk selection, uploads, metadata editing, bulk actions, and usage review from the builder.
Media Health scans attachments for broken files, missing alt text, missing image sizes, oversized files, and obsolete formats. You can filter the library by these findings and resolve them from Attachment Details by adding alt text, generating image sizes, optimizing or converting images, and replacing or relinking files.
The available actions respect the current user’s media permissions. The updated selection flow also keeps attachment details and decorative-image settings available when inserting media.
You can add documents with a native File element instead of using Code or Shortcode elements. Choose a file from the Media Library, enter an external URL, or use dynamic data from a custom field.
The element can display the file name as a link, add a download button, and show PDFs in an optional browser-native preview with responsive dimensions. When an inline PDF cannot be displayed, visitors still receive an accessible link to open or download it.
You can edit custom CSS for the selected global class directly in Class Manager. This keeps class-specific declarations with the class editing workflow, without switching back to an element’s CSS control.
Individual form actions can now run only when their field conditions match. For example, a form can always send an enquiry email but add the submitter to Mailchimp only when a consent checkbox is selected.
Each action rule can check one or more fields with is, is not, contains, does not contain, is empty, and is not empty comparisons. Multiple conditions can use an AND or OR relation, while actions without conditions continue to run on every successful submission.
Precise Visibility Triggers for Viewport Interactions
Viewport interactions now include an Element visibility setting. Choose how much of an element must be visible before an “Enter viewport” or “Leave viewport” interaction runs, from any visible part at 0% to the entire element at 100%. Combine it with Root margin and custom targets for more precise animation timing.
WooCommerce v2 in Beta 3 adds dedicated Cart item data, Order item data, and Checkout account fields elements, plus new cart-item dynamic tags for unit prices and savings. Cart, checkout, and order layouts can now display product titles separately from variation and other item metadata, while Checkout and Account states gain more control over login behavior and header or footer visibility. If you set up WooCommerce v2 with an earlier beta, we recommend running the WooCommerce Setup wizard again to install the latest structures with these new elements and dynamic tags.
Other improvements and notable fixes
Flex and grid layouts now share the row and column gap controls, so switching the display mode keeps existing gap values visible and editable.
Typography control: Preview font-family on hover (enable via Bricks > Settings > Builder > Control panel)
Components that are not on the current page can now be previewed while editing them in Component Manager or the elements panel.
Component variants can now be reordered with drag and drop.
Unlinking a component that contains Nav (Nestable) no longer duplicates its nested elements.
Offcanvas direction is now responsive, allowing a panel to open from different sides at different breakpoints.
Unified Global Import & Export can now include builder interface configuration.
New Bricks settings “Auto-select first class” and “Disable auto-selecting last selected class”.
WooCommerce V2 cart, checkout, and order layouts can render product titles separately from variation and item metadata. New cart-item dynamic data covers unit price and savings values.
Checkout V2 and Account V2 state elements can now override header and footer visibility for individual states.
Checkout V2 now shows the editable Login Required state when guest checkout and account creation during checkout are disabled.
Bricks 2.3.11 improves accessibility for query filters, forms, and default page content, and reduces unnecessary taxonomy indexing on large catalogs. It also addresses regressions in component blocks, forms, and template-backed content.
