Changelogs

A CSS declaration caused certain elements inside the Control Group title—such as style indicators—to become unclickable.

The latest ACF Pro release was escaping HTML in some group labels within the Theme Settings.

In some cases, SCSS code added in SuperPowerCSS was overriding native Custom CSS—even when the SCSS option was disabled in the Theme Settings.

Pasting or resetting styles via the contextual menus in both the Content/Style tabs and Control Groups now fully supports Bricks’ native Bulk Edit feature.

The Structure header icons have been restyled to match the same styles as the Element Panel icons.

Hovering over a global class in the Bricks class dropdown now previews the class on the current element—and on all selected elements when bulk edit is enabled.

A new option has been added to the Focus Mode message, allowing you to jump to the parent element without exiting the Focus Mode.

A new option has been added to the Focus Mode message, allowing you to automatically highlight the corresponding iframe section when focusing an element in the Structure Panel—keeping both views perfectly in sync.

You can now trigger Focus Mode by holding CMD/CTRL + SHIFT and clicking any element inside the iframe—not just from the Structure Panel.

When jumping tabs or elements, SuperPowerCSS could produce a significant layout shift. Now the experience should be a lot smoother.

A new option has been added to the Class Contextual Menu, allowing you to convert directional properties to logical properties—for the current element, its attached global classes, and all of its child elements.

A JavaScript error could occur when the UX Builder settings were empty, causing other functions to break.

Hovering over global classes within the class dropdown of Bricks didn’t trigger the preview inside the Iframe anymore.

Bricks 2.0 introduced new options for handling control group visibility. When the control group visibility was set to “always”, the layout of SuperPowerCSS could be broken when containing long CSS declarations.

Clicking on the dark mode switcher within the Color Manager no longer triggered the color scheme switch.

Renaming an ID or a class in the builder could trigger the keyboard shortcuts of the right shortcut panel and wrongly create elements in the Structure Panel.

This is a security update from the ACF team.

You can now set these settings in the native Bricks capabilities.

You can now set these settings in the native Bricks capabilities.

Several users shared concerns about relying exclusively on localStorage for saving builder UX settings. I may have been a bit overexcited about the benefits, like reducing database load and offering a snappier, more “live” experience, without fully considering edge cases. For example, some users constantly clear their browser cache, while others need to enforce consistent UX settings across all users of the site.

To address this, a new option “Save UX Settings in Database” has been added in the Theme Settings. It gives you control over where UX settings are saved.

• When enabled (default): Any UX setting you change in the builder is automatically saved to the database. On builder load, these database values override what’s in your localStorage, ensuring a consistent UX across all users, browsers, and computers – even after cache clears.
• When disabled: UX settings are saved only in the browser’s localStorage. This lets each user customize their own builder experience, reduces database usage, and keeps everything local. However, settings will reset to default if localStorage is cleared.

You can also manage, migrate, or reset UX settings through the tools in Theme Settings > Global Settings > Import/Export/Reset.

I believe both options have value – choose the one that best suits your workflow. 

You can now export/import/reset all the data related to the UX builder that has been saved to the database.

A new option in the Reset Settings allows you to remove all the Local Storage related to AT.

Visibility Floating bar could show wrong settings when hide/remove settings were set to false in the element object.

That error could be triggered when installing AT for the first time, before saving the Theme Settings.

In case you connected an element to a missing component, a JS error would be triggered and break some functions of AT inside the builder.

After updating to 3.3.1, the WordPress updater was still showing an available release to update.

Both “Filterable Structure Panel” and “Focus Mode” stopped working due to a typo in the code.

StickyCSS, Visibility Floating Bar & Tag Manager localStorage options weren’t correctly applied after builder reload.

The ‘Persistent Link Spacing’ tweak was previously always active, regardless of its setting in the Theme options. It now correctly respects your configuration.

When you apply a variable to any builder control using the AT Variable Picker, the expanded category of that variable is saved in LocalStorage. This means that the next time you reopen the Variable Picker on the same control, the previously selected category will automatically be expanded by default.

Many AT options are now stored in your browser’s LocalStorage instead of the server’s database.

Why?
Because this approach simplifies the Theme Settings panel, which can be overwhelming for many users. It also helps in several key ways:

• Keeps UX settings consistent in the builder — even after a page reload.
• Reduces database bloat by moving browser-level preferences where they belong.
• Supports personalized UX for each user when multiple people work on the same site.

These LocalStorage options are strictly related to the UX inside the builder. They have no impact on your site’s frontend.

This is just the beginning — more UX settings will move to LocalStorage in future releases.

The “Link Spacing Controls” tweak has been renamed to “Persistent Link Spacing Controls.”
When enabled, changing the link type on a spacing control (e.g. unlinked, opposites, or all) will persist across all similar controls — even after reloading the builder.

The Visibility floating bar at the bottom of the structure panel was previously used to modify Advanced Themer’s custom Hide/Remove settings. Now that Bricks 2.0 includes native Hide/Remove functionality, the floating bar has been updated to control Bricks’ built-in visibility settings instead.

When the “Lock ID Style” tweak is enabled, the styling tabs in Quick Access are grayed out and disabled until the lock is removed.

AT no longer adds its own grid icon next to the Display control. Instead, if the tweak is enabled, it now leverages the native grid icon introduced in Bricks 2.0.

The Right Shortcuts Sidebar has a new look to match the overall Bricks 2.0 styles.

Previously, adding a Section element from the right shortcuts sidebar didn’t automatically open the left element panel — now it does, as expected.

You can now apply complex box shadows to multiple elements at once using the new bulk editing feature introduced in Bricks 2.0.

When you add templates to your page using the Quick Remove Template modal, all elements are assigned brand-new IDs to prevent potential builder conflicts caused by duplicate IDs.

When StickyCSS is running in Computed CSS mode, any style changes you apply to an element or class are now reflected live within the StickyCSS editor.

In some scenarios, enabling StickyCSS could cause the structure panel to become excessively scrollable, making elements inside it disappear.

Having CSS declarations within StickyCSS could cause the Visibility Floating Bar to disappear from the structure panel.

Previously, opening the CSS tab of an element or class would automatically hide StickyCSS to avoid conflicts with the custom CSS (or SuperPowerCSS) control. This behavior caused some UX confusion. Now, instead of hiding, StickyCSS automatically switches to Computed CSS mode, allowing you to see your CSS changes live within the StickyCSS editor.

The AT Main Menu has been slightly upgraded with two new features:

• Each tweak now includes a link to its official documentation on the website.
• A new “star” icon appears next to each tweak. Clicking these stars adds or removes the corresponding shortcut icon in the topbar.

Topbar shortcuts are now saved in LocalStorage, so any changes remain persistent after page reloads. As a result, the topbar shortcut options in the Theme Settings have been deprecated, since they can now be fully managed directly within the builder.

Adding Headers or Footers from the Community Templates via the Quick Remove Template modal would previously cause an error, preventing the import from completing successfully.

Bricks 2.0 now includes a native Hide/Remove Element feature. To migrate your existing settings from Advanced Themer to Bricks’ built-in functionality, a new converter has been introduced in the Theme Settings > Global Settings > Converters.

A new icon next to the Paste item within the contextual menu of the Structure Panel allows you to convert all the directional properties into logical ones on the fly!

ACF PRO is now upgraded to the latest available version.

Pressing CMD + F inside a CodeMirror instance would incorrectly trigger Quick Search instead of the editor’s native search function.

The tweak “Hide inactive Style accordion panel” has been deprecated since it’s been introduced natively in Bricks 2.0.

The tweak “Delete Wrappers & Move Children Up” has been deprecated since it’s been natively introduced in Bricks 2.0.

The tweak “Set SVG as the default library for Icons controls” has been deprecated since you can now manage the default library in the new Icon Manager in Bricks 2.0.

The tweak “Remove Default Libraries for Icons Controls” has been deprecated since you can now manage your libraries inside the new Icon Manager in Bricks 2.0.

Tweaks related to the Code Element have been deprecated since it’s now natively integrated in Bricks 2.0.

“Hide in the builder / Remove from the frontend” are now native functions in Bricks 2.0.

The “Hide Element” item within the contextual menu of the Structure Panel has been removed since it’s been natively integrated on Bricks 2.0.

Bricks 2.0 introduced the new Quick Access sidebar in Bricks 2.0 – the “Left Tabs Shortcuts” tweak has been deprecated.

“Indicators of styles inherited from a class” has been deprecated since it’s natively available in Bricks 2.0.

The Elements Manager within the AT Theme settings has been deprecated since it’s now been introduced natively in Bricks 2.0.

Previously, the Theme Settings included an option to choose the style indicator color (colored or grey) in the Structure Panel. To simplify decision-making in the Theme Settings, this option has been removed — the colored indicator is now applied by default.

Previously, the Theme Settings included an option to set the default mode of the Tag Manager (None, Overview, or Developer). This option has been removed, as modes can now be managed directly within the builder. Your selection is saved to LocalStorage, making it persistent across page reloads.

Previously, the Theme Settings included an option to set the default number of columns in the Elements list view. This option has been removed, as column settings can now be adjusted directly within the builder. Your selection is saved in LocalStorage, ensuring it remains persistent across page reloads.

The CSS code within the trigger classes has been updated to give more flexibility when nesting multiple triggers inside the same container.

The --animation-delay-multiplier variable was set to 0 by default, which caused confusion when attempting to override --animation-delay—it had no effect unless the multiplier was manually adjusted first.

.at-anim-repeat was toggling the wrong class when leaving the viewport, and thus stopped working correctly.

The Variable Color Picker wasn’t working inside the builder anymore due to a typo in the JS function.

This version introduces a full set of CSS variables, utility classes, and recipes to create highly customisable CSS animations for your elements.

In some cases, hitting the semicolon key inside SuperPowerCSS could mess up the cursor position.

The exposed H/S/L variables for root global colors were incorrectly printed for light/dark variants.

Enabling or disabling the color picker in Theme Settings had no effect, as it was erroneously tied to the CSS Variable setting.

In Strict Editor View, some control groups in the element panel were hidden despite having active controls within them.

The Quick Access tab introduced by Bricks in version 2.0-RC was conflicting with the existing “Left Tabs Shortcuts” feature of AT.

The “Theme Variables” function was calling a static variable that had been removed in version 2.0-RC, and thus generated a fatal error on the frontend.

Previously, shade generation was limited to root colors. Now, you can generate shades from any color in the Color Manager, enabling fully nested color scales. Colors are displayed in a tree structure to clearly represent each level of the hierarchy.

Transparent variations in the Color Manager now display a checkboard background to clearly indicate opacity levels.

The nested colors created in the Color Manager are now displayed in the Color Picker for all three available views (Column, Grid & List).

Hovering over the color variables within the Color Picker temporarily applies the variable to the selected field; however, this function slows down the overall performance of the modal. In this version, the overall performance of the Color Picker has been improved.

When clicking an element inside the preview window (iframe) could lead to focusing the element without adding the first unlocked global class as active.

Text nodes that weren’t wrapped in a text tag, such as <p>, <span>, or <h*> could cause issues during the HTML parsing since the div element doesn’t support text content in it. Now, all the tagless text nodes are automatically wrapped in a <span> tag to avoid conversion issues in Bricks.

If you activated the WP Admin bar inside the builder view, the close button of the Quick Remote Templates was hidden behind the admin bar.

Parsing the HTML in the Generated Code tab could visually show the changes, but would be reset on reload if no other control was changed during the session.

The Extend Classes & Styles modal was returning a JS error since the modal’s DOM has been conditionally loaded in version 3.1.

The Find & Replace modal was returning a JS error since the modal’s DOM has been conditionally loaded in version 3.1.

WP Dashboard was still showing an update alert after updating to v3.2.2.