Changelogs

The “Color Popup set to RAW and displayed as a LIST” builder tweak has been removed. When enabled, it forced Bricks’ color popup to open in RAW mode and switch to a list view by default — but this override was getting in the way of Bricks’ native color picker, causing it to behave unexpectedly or stop working correctly in some situations. Rather than patch around it, we’ve deprecated the tweak entirely so the color picker can work exactly as Bricks intends.

If you had this option enabled, the color popup will simply revert to Bricks’ default behaviour.

The plugin tried to check whether it was running inside the Bricks builder by calling a couple of Bricks helper functions. In most cases this works fine, but in a few edge situations — the most common being when the WordPress Customizer hits an error and shuts down early — the plugin’s code ran before Bricks had finished loading. At that moment those helper functions didn’t exist yet, which caused a fatal PHP error and a broken page.

Since Bricks 2.3.3, a gap appeared on top of the structure panel. This has been fixed.

Fixed a JavaScript error that could occur when Bricks element objects don’t include a “children” property. Previously, several functions — including CSS generation, style overview rendering, and sticky CSS processing — assumed that every element would always have a “children” array, even if empty. When Bricks stopped providing this property by default, these functions would crash with “Cannot read properties of undefined (reading ‘length’)” errors. Safeguards have been added to all affected functions so they now check for the existence of the “children” property before attempting to access it.

Fixed a JavaScript error that could occur in recent versions of Bricks where color objects no longer include a “name” property. The plugin previously relied on this property being present when working with global colors, which caused “Cannot read properties of undefined” errors. A safeguard has been added so the plugin gracefully handles color objects regardless of whether the “name” property is defined.

Resolved PHP warnings that were triggered when processing global colors that had an incomplete definition object — specifically when the name property was missing or undefined. This could happen with corrupted or partially migrated color entries.

Fixed the keyboard shortcut for opening the Advanced CSS panel not responding to any key press. The shortcut key was correctly configured and displayed in the AT menu, but the actual handler to open the panel was missing from the keyboard shortcuts action map. The action has been added so the shortcut now properly opens the Advanced CSS overlay.

Fixed the Box Shadow Generator icon not being appended next to box-shadow controls in the builder panel. Bricks moved the controlkey attribute from the control element itself to a data-controlkey attribute on a parent wrapper, causing the icon initialization to silently fail. The code now falls back to looking up the nearest parent with data-controlkey when the direct attribute is not found.

Fixed an issue where clicking the Grid Builder icon next to the display dropdown would no longer open the AT Grid Builder overlay. This was caused by Bricks changing the DOM structure of the display control — the button class changed from visual-grid-builder-button to control-action-button inside a has-visual-grid-builder wrapper. The click handler has been updated to match the new structure, and propagation is now properly stopped to prevent the native Bricks grid builder from also opening.

Previously, when inserting a dynamic data token (e.g. Tags inserted from Dynamic Data now respect the current cursor position.) via the Advanced Themer Dynamic Data Helper, the token was always appended at the end of the input field. Now, the token is inserted exactly where your cursor is placed, giving you more control over where dynamic values appear in your content.

In some cases, third-party plugins (such as Doliconnect) could interfere with the Bricks builder state and corrupt the global classes data. This caused the Global Class Manager to crash or display incorrectly. Defensive checks have been added throughout the Class Manager to gracefully handle missing or malformed data, preventing runtime errors.

Bricks 2.2 updated its color control DOM structure, which broke the Advanced Themer color picker integration. The color input is now correctly detected with the updated markup.

On pages with large or deeply nested element structures, the Visibility Floating Bar could appear in the wrong position or overlap other UI elements. This has been corrected.

Unnecessary ACF license activation notices were being displayed in the admin area. These messages have been removed.

When applying stagger effects, a fatal PHP error (rtrim() expects a string, array given) could occur if an element’s styles were stored as an array instead of a string. This edge case is now handled correctly.

When external or restricted stylesheets returned a 403 Forbidden response, attempting to read their CSS rules would throw a DOMException. The plugin now safely skips inaccessible stylesheets without interrupting the builder.

On a fresh installation, before any theme settings had been saved, PHP warnings about undefined array keys were logged. Default values are now properly initialized even when no settings exist yet.

The contrast checker library could crash when encountering color values it couldn’t parse (e.g. CSS variables or non-standard formats). These errors are now caught and handled gracefully.

The Persistent Link Spacing Controls feature has been removed, as Bricks 2.2 now includes this functionality natively. All related code has been cleaned up from the plugin.

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.

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

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 some cases, enabling 3.3.8 would hide header/footer templates on the frontend.

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.