Changelogs

Incorrect version of builder.css could cause the server to misidentify the file and fail to parse it as CSS.

A conflict with the newly released WordPress 6.9 caused all AT styles to be loaded inside the iframe instead of the builder window, breaking the overall builder experience.

Previously, the version tag displayed in the Theme Settings had to be updated manually for each release, which could lead to mismatches between the actual version and the shown tag. It is now generated automatically by the plugin’s build scripts.

In Mobile-First environments, some SCSS code inside the Advanced CSS modal could fail to be included inside the Editor.

A CSS conflict with the Frontend Admin plugin could lead to hide the Theme Settings of Advanced Themer.

If Bricks left behind any orphaned elements, the Structure Helper could trigger a JavaScript error that prevented the modal from opening properly.

Following recent security enhancements by the ACF team, the ACF Pro version bundled with AT has been updated to 6.6.2.

In the some cases, enabling 3.3.8 would hide header/footer templates on the frontend.

Imported classes from the Class Importer in the Theme Settings could sometimes be removed from the elements they were applied to in the builder.

Minor UX issues in the builder related to specific css applied when pseudo-element shortcut were not active.

Forcing the color Theme to dark in the Theme Settings > Global colors could potentially fail and still show the light theme.

When setting the base breakpoint to Mobile First in Bricks, CSS declarations saved inside the page.css stylesheet of Advanced CSS were applied correctly in both the builder and the frontend, but disappeared from view after refreshing the builder.

The keyboard shortcuts for the builder tweaks Grid Guides, Xmode, Contrast Checker and Darkmode weren’t triggering the corresponding functions since version 3.3.

Fixed an issue where the Color Picker library used by the Color Manager was rounding hex values too aggressively when converting to RGB, resulting in possible slightly incorrect color outputs.

Fixed a PHP warning that could appear on first installation before Theme Settings were saved.

A recent change in Bricks 2.1 lead to breaking the AJAX call to the remote templates, thus the Quick Remote Template feature stopped working correctly.

In the Class Manager of AT, renaming a global class while the class was active in the builder could possibly revert to the old name as soon as another class was being activated.

When the event of the AT variable picker was set to “right-click”, clicking on the native Bricks CSS icon to open the native variable dropdown would also trigger the variable picker from AT.

In the Plain Classes modal, editing, removing, or adding a class did not update the editor correctly unless the ‘Edit Bulk’ mode was enabled.

A new option in the Strict Editor’s builder tweaks has been added to hide the Quick Access Bar for all editors on the site.

A new option in the Strict Editor’s builder tweaks has been added to hide the Search Box in the Element panel.

A new option in the Strict Editor’s builder tweaks has been added to hide the Elements States within the Structure Panel for all editors on the site.

A new option in the Strict Editor’s builder tweaks has been added to hide the Element Panel’s header for all editors on the site.

A new option in the Strict Editor’s builder tweaks has been added to hide the Element Actions in the Preview window for all editors on the site.

A new option in the Strict Editor’s builder tweaks has been added to hide the Contextual Menus for all editors on the site.

When you add global classes to an element through the Plain Classes modal with Bricks’ “Bulk Edit” feature enabled, those classes will be correctly applied to all selected elements.

All GPT-5 models are now available in the list of selectable models under Theme Settings > AI Options.

The following tweaks were previously enabled by default on new installations:

• StickCSS (Structure Menu)
• Visibility Bar (Structure Menu)
• Responsive Slider (AT Main Menu)
• Responsive Helper (AT Main Menu)

However, they often caused more confusion than benefits, as many users struggled to find where to disable them. For this reason, they are now turned off by default.

Previously, when adding Custom CSS to page.css in the Advanced CSS modal with a specific breakpoint active, the code could be applied to that breakpoint’s settings instead of the base. Now, all CSS added to page.css is always applied to the base breakpoint, regardless of which builder breakpoint is active.

In the initial version of the new ‘Content/Style Tabs Context Menu’ tweak, the script sometimes failed to correctly distinguish between settings belonging to a Class and those belonging to an ID when a global class was active. This caused unexpected results when copying and pasting settings between elements.

Previously, if users converted directional properties into logical properties, there was no way to undo the change. A new button has now been added in the Converter tab, allowing you to revert all logical properties on your site back to directional properties.

In some cases — especially when clicking inside the preview window — the global class wasn’t correctly applied to the Element panel, which could cause unexpected issues.

Since the Bricks 2.0 update, the color indicators (green/red) for locked and unlocked global classes in the Element Panel were no longer working.

When the Plain Classes modal was set as the default class picker in Theme Settings, the native Bricks class lock icon in the Element Panel became unclickable since Bricks 2.0.

Due to changes in how Bricks 2.0 saves custom CSS values to the database, code added in SuperPowerCSS could sometimes fail to save correctly on page reload.

Since Bricks 2.0, the option to generate a global query from the Native Query popup was missing.

Since Bricks 2.0, the Global Query List icon — used to assign a global query to an element — was missing.

Occasionally, reopening the Class Manager in CSS View would display a blank CSS editor until a key was pressed and remount the content of the Global Class.

Due to changes in Bricks 2.0, editing the custom CSS of a global class via the AT Class Manager could cause incorrect rendering in the builder and prevent the changes from being saved correctly to the database.

Previously, we added an inline display: none style to Dark Mode buttons and toggles to prevent FOUC on page load. However, this also removed them from the accessibility tree, making the elements unfocusable via keyboard.

In the Structure Generator Modal, dropping an image into the dropzone input did not correctly send the image data to the prompt, preventing the ‘image to code’ feature from executing.

All toolbar icons for features now managed directly through the new builder capabilities in Bricks 2.0 have been removed. The remaining icons are those loaded by Bricks by default, regardless of the user’s role capabilities.

The option to disable specific elements for Editor roles is now handled by Bricks 2.0’s built-in improvements and has therefore been deprecated.

The editor builder tweak ‘Reduce Left Panel Visibility’ is now incompatible with Bricks 2.0’s new role capabilities system and has therefore been deprecated.

Since Bricks 2.0 now allows opening code editors in full screen natively, the Code Element tweaks have been deprecated.

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.