This release tackles many current issues and adds plenty of improvements and some exciting new features to Bricks.

It’s a big one—around 80 changes in total. So, we’ll first release a beta for you to test and provide feedback via email or the forum. Please don’t use this beta on any live sites!

The manual download for this beta is available at https://my.bricksbuilder.io/?beta=1.9.8

CSS Variables Manager

After introducing the global class manager in Bricks 1.9.5, we now extend the global style management capabilities of Bricks to CSS variables with the introduction of the new global variables manager 🤩

Documentation: https://academy.bricksbuilder.io/article/global-variables-manager/

Code Element: Support Dynamic Data

The Code element now supports parsing dynamic data.

To remain backward-compatible and avoid breaking any existing code with the new parse, you have to explicitly enable the new “Parse dynamic data” setting, as shown in the screenshot.

You’ll also notice another new setting named “Suppress PHP errors”. Enable it if you don’t want any potential PHP errors inside your Code element to be visible on the front end of your live site.

Duplicate Pages/Templates

Do you have an existing page, built with Bricks or Gutenberg, that you want to duplicate, including all its post meta, terms, etc.?

You can now do this with Bricks, either in the WordPress dashboard by hovering over the page title and clicking the “Duplicate” link or inside the builder under the “Pages” panel.

Please use this new built-in duplicator instead of third-party solutions to ensure that unique element IDs are properly generated for your duplicated pages, templates, etc.

The duplicated page/template will be saved as a draft.

Style Tab & Breakpoint Setting Indicators

The trusty setting “dot” indicator was only available next to individual settings. You can now quickly spot if the element or global class you are editing contains settings on any breakpoint. And if any styles are set under the “Style” tab.

NOTE: The little “dot” that indicated the “Base breakpoint” in the builder toolbar has been changed to a “line” below the breakpoint icon. This way, we can use the “dot” indicator throughout the builder to denote properties that “have settings.”

New Spacing Control UI (margin/padding)

As the new variable picker requires additional space inside the panel, we had to rethink certain controls, such as the spacing control used for margin, padding, and border width.

You can still access the previous spacing control by clicking the “toggle” icon. 😎

Cache remote templates

Previously, remote templates were requested every time you opened the template manager in the builder, which was a bit excessive. So now, all remote templates are cached locally on your machine for seven days via IndexedDB.

More flexible echo function name checks

If you are using a lot of DD echo tags on your Bricks site, you can now take advantage of a more flexible way to whitelist and check the function names you want to call through the echo tag via regex patterns or 100% custom checks. Learn how, plus code examples, at https://academy.bricksbuilder.io/article/filter-bricks-code-echo_function_names/#patterns

New custom JavaScript events

We prepared the following three new custom JavaScript events for you:

  • bricks/tabs/changed
  • bricks/accordion/open
  • bricks/accordion/close

There’s also a new Academy article listing all custom JavaScript events Bricks provides at https://academy.bricksbuilder.io/article/custom-javascript-events-in-bricks/

Full v1.9.8 changelog

Quick hotfix release as Bricks 1.9.7 caused an issue with adding/updating the postmeta for users without builder access. This was caused by one of the new security additions in 1.9.7.

Full v1.9.7.1 changelog

The update we provided on February 13th with Bricks 1.9.6.1 was a quick and effective answer to the vulnerability reported on February 10th. It successfully tackled the urgent issue and also initiated a broader initiative to strengthen Bricks’ security rather than representing the final phase of our security enhancements.

We’ve dedicated the past four weeks to a thorough review and enhancement of our entire codebase. Our goal was clear: develop a solution for code execution that maintains the advanced code functionality you rely on while elevating Bricks’ default security level to new heights.

This 1.9.7 update is the result of this effort. It introduces a suite of new security features and improvements.

It also addresses a smaller, possible authenticated issue discovered while working on 1.9.7, which requires a contributor role or above, bad intentions, and a code execute user to perform certain additional steps. There is no need to panic or update in the next 5 minutes, but we recommend updating as soon as you have the chance.

If you experience any problems after updating, please reach out to us via email at [email protected].

Before you update, please take a full backup of your site!

The significant changes of this update could impact your site’s functionality. A backup ensures you have a safe point to revert to if necessary. Please do not skip this critical step.

Continue reading the full changelog entry with all details by clicking to link below …

Full v1.9.7 changelog

We just released a mandatory security update with Bricks 1.9.6.1. 

A leading security expert in the WordPress space just brought this vulnerability to our attention, and we instantly got to work, providing you now with a verified patch.

As of the time of this release, there’s no evidence that this vulnerability has been exploited. However, the potential for exploitation increases the longer the update to 1.9.6.1 is delayed.

We advise you to update all your Bricks sites immediately.

Key Instructions

Update Now: Update all your Bricks sites to the latest Bricks 1.9.6.1 as soon as possible. But at least within the next 24 hours. The earlier, the better.

Backup Caution: If you use website backups, remember they may include an older, vulnerable version of Bricks. Restoring from these backups can reintroduce the vulnerability. Please update your backups with the secure 1.9.6.1 version.

Updating is straightforward and can be done with one click right from your WordPress dashboard. It should not affect your site’s functionality.

If you have any questions or experience any functionality loss after the update, please email our customer support at [email protected].

How to update Bricks

1. One-Click Update from WordPress Dashboard

Navigate to Appearance > Themes in your WordPress dashboard.

Locate Bricks, and if the update notification for 1.9.6.1 is visible, click to update.

If you don’t see the update notification:

Go to Dashboard > Updates and click on the “Check Again” link. Once the update appears, proceed to update Bricks.

2. Manual Update

If the one-click update does not work or you prefer a manual update, visit your Bricks account at https://my.bricksbuilder.io/ and download the latest version of the Bricks theme (1.9.6.1).

Back in your WordPress dashboard, go to Appearance > Themes, click “Add New” and then “Upload Theme”.

Select the ZIP file you just downloaded and install it. Overriding your existing version of Bricks if asked.

Better to be safe than sorry

While addressing security concerns is an integral and regular part of maintaining any WordPress-based theme or plugin, approaches to communication about these updates can vary.

We believe in being extra cautious — it’s better to be safe than sorry. Keeping our community informed and engaged ensures you’re always up to date and your site remains secure.

We encourage you to share this update with fellow Bricks users to help maintain a secure community for everyone.

Time to update,
Thomas & team

Full v1.9.6.1 changelog