ReleaseWPChangeSync 2.0 is here →
Guides/Custom Fonts and Bricks Capabilities

Custom Fonts and Bricks Capabilities

Move custom fonts and capability-based Bricks settings without breaking target environments.
Updated 5 June 2026·Task guide

Outcome

Custom fonts, font files, and Bricks capability settings such as SVG uploads, maintenance bypass roles, and code execution move intentionally between sites.

Video walkthrough

▶

Video walkthrough coming soon.

The YouTube embed will appear here.
Risk level

High. Capabilities and code/SVG settings can be security-sensitive. Review production settings manually.

Before you start

  • Know whether the target should inherit capability settings from the source.
  • Check whether font files already exist on the target.
  • Confirm code execution and SVG policies are acceptable for the target environment.

Steps

  1. Include custom fonts with template releases
    Templates that depend on custom fonts should ship with the custom-fonts integration.
  2. Review capability settings separately
    Do not blindly overwrite production security settings.
  3. Dry-run font imports
    Check whether existing media/font files will be reused by slug/path.
  4. Verify the Bricks font picker
    After import, confirm custom fonts appear and render.
  5. Verify security-sensitive capabilities
    Review SVG, code execution, and bypass roles after import.
Capabilities can be security-sensitive
Treat Bricks capability sync like configuration migration, not design content. Production may need stricter settings than staging.

Code basis

WPChangeSync 2.0 reworked custom fonts with CPT handlers and font file import/export, and includes Bricks capability settings in push/pull and storage flows.

$pathstringRequired

Absolute path of the directory to write the snapshot to.

$modestringOptionaldefault: two-way

Sync direction — push, pull or two-way.

$gitboolOptionaldefault: false

When true, commits the snapshot to the repository after writing.