← Docs

Applying Smart Fixes safely

Smart Fixes let you resolve many findings with one click. They’re built to be safe to run on real client sites — nothing changes without a way back.

What happens when you apply a fix

Every Smart Fix follows the same four steps:

  1. Snapshot — the affected page’s Bricks data is saved before anything changes.
  2. Apply — only the elements named in the finding are modified. Nothing else on the page is touched.
  3. Verify — the plugin reads the data back to confirm the change landed as intended.
  4. Undo (any time) — every fix is reversible from the history panel, which restores the snapshot exactly.

Fix types

  • Safe auto — low-risk, mechanical changes (for example, swapping a hardcoded color for the matching variable). Safe to apply directly.
  • Review — changes where you’ll want to make a choice first (for example, naming a new global class before it’s created). You confirm the details in a preview before it runs.

The kill-switch

In Settings, the “Allow fixes to modify Bricks data” toggle is a hard global switch. Turn it off and no fix can write anything, no matter what — useful on production sites where you only want to scan and review.

Version safety

When a new Bricks version is released that the plugin hasn’t been verified against yet, Smart Fixes automatically switch to read-only until we confirm the update is safe. Scans keep working; your data is never modified by an unverified version.

Good practice

  • Work on a staging copy for the first pass on any important site.
  • Keep independent backups — Smart Fixes snapshot Bricks data, but they aren’t a replacement for a full site backup.