Changelog

Apply global heading styles for any specific heading level to a custom selector while ensuring the output is confined only to properties with values set in the dashboard.

Read docs

Apply global text styles for any specific text level to a custom selector while ensuring the output is confined only to properties with values set in the dashboard.

Read docs

We now provide a custom control point for radio inputs and checkboxes in form elements.

Some smart spacing elements only contain top margin. Others, like figures, blockquotes, and lists, can contain top and and bottom margin.

When elements that contain both top and bottom margin are followed by elements with top margin, it can create duplicate margins.

This was previously solvable by setting a different block margin bottom value, but that’s not a very elegant or “smart” solution.

This feature introduces a new input that allows you to identify block margin elements so that Smart Spacing can remove the top margin from their adjacent siblings (don’t worry, we set a default for you).

MINOR BREAKING CHANGE: If you’re a user who noticed instances of duplicate margin and already accounted for them somehow, this update may cause a change in those margins. You should remove your manual overrides.

Additionally, you should check the value of your “list spacing (block)” input in Smart Spacing to see if it has the old default “0” as the second value. If it does, you can remove the “0.”

This feature improves the accuracy of smart spacing and removes rare instances of double margin.

This improves compatibility with other plugins as well as the WordPress Interactivity API.

There was an issue where the custom dashboard shortcuts panel wouldn’t open on some installs. This is now fixed.

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.