Changelog

This bug was related to syntax and was revealed by fixing a bug in the prior release. The syntax issue is now fixed and main colors render correctly in dark mode again. Shades were unaffected.

We have taken the first big step toward perfecting our front-end validation, which ensures that users are not able to save breaking values to the database. There are a few little validation quirks to work out before we can release step 2, which is the final step and will result in full front-end validation.

@concentric-radius; will now expand out the recommended code for creating concentric radii wherever needed.

We’ve fixed issues related to license activation for anyone using WordPress Studio.

We’ve updated the default behavior of auto radius to exclude the header. This will prevent logos from automatically having auto radius applied. Users will need to click the default reset icon next to the “Auto Radius Selectors” input under “Additional Radius Options” to receive this update on existing installs.

Rather than reloading the admin page, the toolbar link in the admin will now take users to the front-end and trigger the dashboard to open. This should reduce confusion and increase efficiency.

We fixed an issue with the hover label color on checkbox elements in Bricks forms not being styable from the dashboard.

Label padding was not updating via the dashboard, especially when “inside position” was used as the label position. This is now fixed.

.grid--auto-rows is a rarely used class that was causing all items in a grid to stretch (instead of just doing its intended job). This is now fixed.

.grid--auto-rows is a rarely used class that was causing all auto grids to go to a single column layout. This is now fixed.

Color partials were not receiving alt values when alt colors were activated. This only affected direct, static references to color partials (not color tokens in general) and is now fixed.

Added 100%, fit-content, min-content, max-content, and auto as quick-values in context menus for width inputs.

We added a 1px offset to the breakpoint-up mixin to ensure that there is zero overlap with max-width media queries.

Some users weren’t immediately sure what the hover icon was for. We’ve added a tooltip for clarity.

Note: A database backup is recommended prior to updating due to this bug fix.

This bug affected multiple different inputs where the SCSS variable has a blank value, expecting to get its default value from the dashboard. The default dashboard value is now pushed to the SCSS variable properly, fixing the issue with missing styles on upgrade.

This bug only affected upgrade installs and was fixable quickly by resetting the affected dashboard values, but the reset fix should no longer be needed.

This value slipped out of the context menu for a while, but it’s back now.

Auto-grid compatibility updates to grid classes weren’t pushed to Oxygen Builder’s overrides file. This is now fixed.

This new feature is found under Options > Experimental. It removes classes from the database when they’re deactivated in ACSS. This is a performance enhancement to make Bricks snappier and clean up the Bricks classes database.

Two caveats:

1. Users will need to reload Bricks to see the classes / palettes updated.
2. The system won’t remove ACSS classes that users added manually because the class IDs are unknown to us. If you added an ACSS class manually because it was missing at some point, we won’t have control over those manually-added classes.

There is still room for granular improvement here (e.g. active/inactive color logic for certain modules), so we’ll continue improving this over subsequent releases.

This is an experimental feature. Please make sure you have a backup before you try it, and let us know if you run into any issues.

This new control allows users to fine-tune the default aggressiveness of element stacking in Auto Grids.

Bricks Extras users and Bricks Score users reported a conflict with their interactive cursor element. This should be resolved now.

The @auto-grid recipe was out of sync with latest changes to Auto Grid. It’s now up to date again.

This option for color scheme was not being ported properly on upgrades from 2.x. This is now fixed.

Self explanatory.

We’ve resolved various console warnings that would occur on update.

Users can now choose to use global button styles for form buttons instead of managing form button styles separately. Each type of form button can have a global button style assigned to it. Supports all button styles including outline variants.

Since Smart Spacing only applies to top level elements, multi-paragraph blockquotes were not getting Smart Spacing applied. We’ve enhanced SS to include blockquotes.

In some uses of Auto Grid, items were stacking too soon. Not only have we fixed this, we’ve provided a new control so users can dial in the exact aggressiveness they want in their Auto Grids. This control is called “Aggressiveness” and it’s found in Layout > Auto Grid. And don’t worry, this is just for the default and can easily be overridden at the instance-level.

It was working in live preview, but wouldn’t commit new values to the database. This is fixed now.

• Menu dropdowns were getting contained inside the header and clipped. This is now fixed.

A bug was causing radius size variables to not load even when the “Generate Extra Radius” sizes toggle was on. This is fixed.