Changelogs

With Bricks’ CSS sync enabled, converting an element’s UX values to CSS wiped both the controls and the CSS instead of converting them. The command is now unavailable while CSS sync is on, since the sync already keeps the two in step.

With an AT panel open on the right, the tooltips on Bricks’ toolbar were hidden behind it. The panels now sit below the toolbar so its tooltips stay readable.

Clicking a color in the Color Manager opened the picker behind the panel, so it was invisible. The picker and the other AT popups now open in front.

AT’s clean-up of unused global classes could run before Bricks had finished loading the page, which made it look at an incomplete list. It now waits for the data to be ready.

After editing the toolbar layout, the AT menu icon could vanish until the builder was reloaded. It now comes back on its own once the layout is applied.

Moving or hiding toolbar items in Bricks 2.4’s Builder Interface could make AT’s icons disappear, or leave several Responsive Sliders stacked on top of each other. AT now follows its icons wherever the items are placed.

Floating the structure panel used to free up its space for the canvas. In Bricks 2.4 that space stayed reserved and empty, and resizing the floating panel resized the empty strip instead. The canvas now takes the space back.

When the structure panel was set to float, the shortcuts sidebar next to it kept the height of the docked panel and stopped short. It now fills the floating panel.

Bricks 2.4 can place toolbars on any side of the screen, which left AT’s panels a little out of position: part of the panel behind them stayed visible. AT’s panels now measure the toolbars and cover the full area, and stop above a bottom toolbar instead of running underneath it.

AT’s element shortcuts sidebar was pinned to the edge of the screen, which in Bricks 2.4 is where the new side toolbar sits, so the two overlapped. The sidebar now sits inside the structure panel where it belongs.

Bricks 2.4 lets you move the panel and structure around. Doing so rebuilt parts of the interface and AT’s features quietly stopped responding inside them until you reloaded. AT now notices the change and reattaches itself.

Opening the builder could immediately mark the page as having unsaved changes, so you were warned about losing work you had not done. AT’s global classes clean-up now waits for Bricks to finish loading before it touches anything.

AT’s dark mode preview icon used to switch only AT’s colors on the canvas, leaving Bricks’ colors in light mode. It now switches both, and it follows Bricks’ own light/dark switch in the toolbar, so the preview always shows one consistent scheme.

AT’s dark mode toggles and buttons, and Bricks 2.4’s “Toggle – Mode” element, each used to switch only their own colors. Either one now switches both, so you can mix them on a page without half the palette staying behind. Your visitors’ choice is remembered by both.

Colors created in Bricks’ own Style Manager used to show up in AT as flat rows with no real value, with each shade listed twice. They now show their actual color, and their shades are grouped under the parent color like AT’s own.

Change a color in AT’s Color Manager and Bricks’ Style Manager follows immediately, and the other way round. The canvas updates at the same time, so you no longer have to save and reload to see where a color landed.

Until now AT’s colors showed up empty in Bricks’ Style Manager, with a notice asking you to convert them. They now appear with their real swatches in both light and dark mode, and you can edit them there if you prefer. Nothing about how your colors are stored has changed.

Bricks 2.4 can keep your UI controls and your custom CSS in step with each other. AT’s CSS editors now take part in that: type CSS in SuperPower CSS, Sticky CSS or the Class Manager and the matching controls update, and changing a control updates the CSS you see. Enable it under Bricks > Settings > Builder > CSS sync.

When AT activates or checks your license, it now makes sure it’s really talking to the Advanced Themer license server over a secure connection.

AT now reads its per-page settings more strictly, which closes off a class of attacks that relies on tampered stored data. This is a behind-the-scenes hardening, and your settings work as before.

When you import an AT settings file, only AT’s own settings are restored. A modified file can no longer change other WordPress settings. The imported values are also saved the standard WordPress way.

Saving changes to your child theme’s stylesheet now follows WordPress’s own rule for editing theme files, including sites where theme file editing is disabled. The WPCodeBox sync now only updates style snippets and never touches code snippets.

The Class Importer now only accepts normal web addresses for remote stylesheets. That blocks attempts to make your server read its own private files or reach internal network addresses.

If a custom query in the Query Manager had an error, technical details could be shown on the page. Errors now stay hidden from visitors, and the site’s normal error settings are always put back afterwards.

Only users who are allowed to upload media can save AI-generated images to the Media Library, and AT checks that each file really is an image before saving it.

Your OpenAI API key is now better protected. Only users with full builder access can use it, and it no longer appears in the source of the Theme Settings page or of the builder. To change it, type a new key. Leaving the field as it is keeps the saved key.

Some of AT’s background actions were also open to visitors who aren’t logged in, although only builder users need them. They’re now limited to logged-in users, which reduces what’s exposed on your site.

Values from the dark mode elements, the meta theme color, page transitions and the forced default color scheme are now cleaned before they’re added to your pages. Unexpected characters can no longer break your markup or be misused. Your pages look exactly the same.

The Variable Picker now looks up your Core Framework preset in the database the safe, standard WordPress way. Nothing changes for you: it’s a behind-the-scenes hardening.

When AT downloads a file from another website, it now checks that the connection is secure. It also gives up after 5 seconds, so a slow or unreachable site can’t make the builder hang.

Bricks now previews colors on hover in its own color picker, so AT’s version of this tweak for the Bricks picker has been retired. The hover preview in AT’s own color picker stays.

This builder tweak has been retired, as part of an effort to keep AT focused and lightweight alongside recent Bricks improvements.

This builder tweak has been retired, as part of an effort to keep AT focused and lightweight alongside recent Bricks improvements.

The copy of ACF PRO bundled with AT, which powers the Theme Settings page, is updated to version 6.8.10, with the latest fixes and improvements from the ACF team.

The accessibility label on the Dark Mode Button element had a stray character that made it invalid for screen readers. It’s now correct, so assistive technologies read the button properly.

If a popup wasn’t available (for example because its feature is turned off), trying to open it caused a JavaScript error. AT now skips it without an error.

When a file imported into AT couldn’t be read (Class Importer stylesheets, JSON variable frameworks, settings imports), AT could print a raw error message inside the builder or break some background requests. An empty file field could even crash the page on PHP 8. Failed imports are now handled quietly, without breaking anything else.

Stylesheets added to the Class Importer from a URL could stop the builder from loading, and uploaded ones were downloaded again from your own site every time the builder opened. Custom stylesheets with missing settings could fill your error log with warnings, and a damaged one could stop the builder from loading. Saving or deleting a stylesheet could also crash when it failed (for example because of folder permissions or a WPCodeBox issue). URL imports now work, uploaded files are read straight from your server (so the builder loads faster), damaged stylesheets are handled gracefully, and failed saves show a clear error message.

If you use Core Framework or an imported variable framework, the switch at the top of the Variable Picker was linked by mistake to the one in the Box Shadow Generator. Changing one could flip the other. Each switch now works on its own.

On some setups, especially sites behind Cloudflare or running a caching or optimization plugin, the Custom Components popup could interfere with how Bricks or those plugins process the builder page. That could break Bricks’ Cloudflare protection for the builder. AT no longer touches anything outside its own popups.

Switching between light and dark mode in the builder could show the wrong colors in sections set to a reversed or initial color scheme. The canvas now shows the palette each section is meant to have in both modes.

In Bricks 2.4, the zoom-out icon no longer lit up when zoom-out was on, so you couldn’t tell at a glance whether it was active. And if you left zoom-out on and reopened the builder, the canvas wasn’t zoomed out. Both are fixed: the icon shows its state again, and zoom-out applies as soon as the builder opens.

The Responsive Helper, which highlights the breakpoint you’re editing in the toolbar, stopped working after Bricks 2.4 changed its toolbar. It works again.

Bricks 2.4 redesigned its toolbar, and the icons AT adds to it (AT menu, Class Manager, Color Manager, zoom-out…) had stopped appearing. They’re back, in their usual places. This also works if you’ve moved the Bricks 2.4 toolbar to the bottom or to the side of the screen, and on older Bricks versions.

Each AT popup (Class Manager, Variable Picker, Grid Builder and so on) is now built separately. A setting or glitch in one popup can no longer affect another. This change happens behind the scenes, and the popups look and work exactly as before.

Bricks 2.4 opens the builder much faster than before, and AT used to show up a few seconds later, so the toolbar and panels popped in after the editor had loaded. AT now starts at the same moment as Bricks, and everything is in place when the loading screen goes away.

Fatal error on some sites when checking the ACF PRO license

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.