Skip to content

v1.2.2 — div→block converter fix + Connect page-CSS panel

Choose a tag to compare

View all tags
@developer2013 developer2013 released this 17 Jun 13:02
v1.2.2
4eee25a

Two fixes from a sharp r/BricksBuilder report — thanks btolle89.

Fixed

  • HTML→Bricks converter: a plain <div> is no longer forced into a flex container. It was blanket-mapping <div> (and nav / header / footer / main / article / aside / figure) to a Bricks container, which is display: flex — so a plain block-flow wrapper silently inherited flex positioning it never had. It now maps those to a block (a real <div>) and only reaches for container when the resolved styles (inline or class-resolved from the provided stylesheet) actually lay it out as flex/grid.

Added

  • Connect: a "Plugin-managed page CSS" panel. The setup screen now lists pages that carry plugin-injected per-page CSS — the bundle stored in _bab_page_assets and echoed into <head> as <style id="bab-page-css-{ID}">. That CSS is intentionally not shown in the Bricks builder/settings/theme/class panels (it's for CSS variables, critical CSS and anything the assistant couldn't express via element/class settings), which is what made it feel like "CSS I can't find anywhere." It's read-only here (editable via bricks_update_page_assets), so it's no longer a black box.

Update the plugin: download bricks-api-bridge.zip below and update in WordPress (gets the page-CSS panel). The converter fix ships in the MCP server code — git pull the repo to pick it up. Full history in CHANGELOG.md.

Assets 3
Loading