Skip to main content

What's new

The highlights of each release, in plain language and filtered to what you'll actually notice. The complete technical changelog lives on GitHub.

0.59.0 — July 2026​

This release was battle-tested against three real production sites (an agency site, a sports club, and a recruiting platform) — every improvement below was found and verified on real data.

Your site keeps its look​

  • Custom fonts now migrate. Font files and font families arrive on the Etch site as native WordPress fonts — including modern variable fonts. Previously the fonts step silently never ran and the target fell back to system fonts.
  • Typography stays intact. A parked, unused Bricks theme style could previously override your real site typography on the target (suddenly everything rendered in the wrong font). Only theme styles that are actually active on your site are converted now.
  • Buttons keep their colours and classes. Several conversion bugs could rename, drop, or recolour button classes — an "action" red button could arrive as a pink "primary" one. Fixed.
  • Automatic.css v2/v3 sites keep rendering on ACSS 4. ACSS 4 no longer generates some colours and helper classes older sites rely on. The migration now detects exactly what your content uses and carries those pieces over from your source site automatically.
  • Menus arrive as working menus — dropdowns and mega menus open and close, the mobile burger opens the mobile menu, keyboard access works. Previously navigation arrived as a static block with every panel permanently expanded.

More reliable migrations​

  • Taxonomies migrate again. Categories, tags, and custom taxonomies were silently skipped in earlier versions — now they arrive, including the assignments to your posts.
  • JavaScript in code elements actually runs on the Etch site now.
  • Media transfer is more robust: fixed downloads failing on non-standard ports (common in staging and Docker setups), broken attachment entries no longer produce false "media missing" errors, and secure connections are verified properly with a safe fallback.
  • A migration no longer reports success when content is missing. If the target reports incomplete content, you now get a clear error with the target's own diagnosis instead of a green checkmark.
  • Migrations can't hang forever anymore. Stuck batches recover on their own, and the final waiting step has a time limit with a clear error message instead of waiting indefinitely.

Clearer help when something goes wrong​

  • Database setup problems, finalisation failures, and connection issues now show detailed error messages that link directly to the matching page in this documentation.
  • Lots of under-the-hood hardening for shared hosting environments (nginx, restrictive database users, stricter security setups).

0.58.0 — July 2026​

  • Validated end-to-end against real production Bricks sites, including a Meta Box-heavy site.
  • Custom breakpoint setups no longer flip ACSS media-query shorthand in the wrong direction.
  • Finished migrations show real item counts instead of "0/0".
  • Removed misleading warnings about elements that actually convert fine.

Older releases​

See the full technical CHANGELOG on GitHub for everything before 0.58.0.