Bricksforge MCP for its activation registry, popups and email templates

Launching a Bricksforge popup on one page, not the whole site

A popup in Bricksforge is two things: a Bricks template that holds the content, and a configuration that decides when and where it appears. Build or pick the template first with the Bricks abilities and publish it, then create the popup with bricksforge-create-popup. The template is checked at write time, and the trigger is one of pageLoad, click, scrollPosition or customTrigger, with its own parameters such as the scroll position.

Watch the defaults. A new popup is active straight away and displayOn defaults to entire_website, so a lead-capture popup meant for one landing page will appear everywhere unless the request says otherwise. Ask for displayOn specific_page with the page set, or create it with active false and switch it on after a look at the target page. Animation is one of five fade variants, and overlay and body colours fall back to Bricksforge's own defaults when not given.

Once it is live, bricksforge-get-popup is the diagnostic. It warns when the Popups tool is off, when template, displayOn or trigger is missing, when active is not true, and when the template it points at has since been trashed or unpublished. That last case matters: Bricksforge's popup endpoint serves the template to visitors whatever its status, so an unpublished draft can still show, and a trashed one shows nothing.

Switching a redesigned email over without a gap or a double send

The worked example above parks the original email while a copy is redesigned. Switching back to the new design has an order that matters. Two active templates that override the same email both fire, so the copy should only gain its conditions once the original stops overriding that email. Setting conditions through bricksforge-edit-email-template replaces the whole list, so send every email the copy should override, not just the one being added.

A safe sequence is: confirm the copy's design in the Email Designer, set its subject and conditions while it is still inactive, disable the original, enable the copy, then place a sandbox order and read the email that arrives. Between the disable and the enable, WooCommerce's default email goes out, which is a fallback rather than an outage. Keep the original until the new one has handled real orders; disabling costs nothing and deleting has no trash.

Cleaning up the Bricksforge registry on an inherited site

Over time Bricksforge sites collect tools and elements switched on for one experiment. bricksforge-list-tools and bricksforge-list-custom-elements turn the bare numbers into names, and report active ids the catalogue does not know as unknown_active_ids, which usually means a newer Bricksforge than the catalogue. Leave unknown ids alone rather than guessing what they are.

Tools and elements behave differently when switched off. Disabling a tool keeps its settings in brf_tool_settings and its data, such as form submissions, so re-enabling restores it. Disabling an element removes the settings stored on its registry row, including Pro Forms captcha and Stripe keys, and pages that use it keep the element but stop rendering it. Before disabling an element, search the Bricks pages for it and copy any keys from Bricksforge's screen.