Release notes
Changelog
All V1 editor, rendering, translation, and support updates are consolidated in 1.1.30.
Maintenance release 1.1.30 Canonical V1 maintenance release
Automatic CSS 4 editor parity
Gutenberg now chooses and applies the active site styles more reliably, so previews better match the published Bricks output.
- Fixed Automatic CSS 4 editor asset selection, including the typography and default button-link cascade.
- Prevents empty style placeholders and duplicate style responses from changing the editor cascade.
- Reduced Gutenberg-only layout differences around GutenBricks blocks and nested editor mounts.
Editor reliability
Preview updates are less likely to leave a newly inserted block or the post editor in an inconsistent state.
- Improved render readiness so an incomplete preview does not create an unnecessary dirty state.
- Keeps preview refreshes isolated from other GutenBricks blocks on the page.
InnerBlocks
Configured default children now appear at the right time without overriding deliberate edits.
- New blocks receive configured default InnerBlocks after their template settings are available.
- Preserved intentional InnerBlocks removals through preview refresh, save, and reload.
Translation content
Safer handling of editable GutenBricks content during multilingual workflows.
- Improved restoration of editable text, links, buttons, image details, and nested content after a provider update.
- Preserved template references and block metadata when translated block markup is rebuilt.
Safer translated templates
Translation updates now preserve authored content and avoid unsafe partial replacements.
- Avoided partial updates when a translated field or block structure cannot be mapped safely.
- Rechecked the target post before writing so a delayed provider update does not overwrite a newer edit.
- Improved translated-template aliases and kept provider save callbacks re-entry safe.
Direct support contact
A clearer route for bug reports and support requests from the WordPress settings screens.
- Bug reports can now be sent directly to [email protected].
- Updated the Custom CSS support link to use the same address.