Skip to main content

WordPress content

Bricks Builder in Core Forms

Insert Core Forms with a native Bricks element.

Bundled with Core Forms, the WordPress forms plugin with every premium feature in the box. No add-on tax.

Bundled, no add-on tax Unlimited sites

The Core Form element is a native Bricks Builder form element that places any Core Forms form in a layout without a shortcode. Drag it in, pick a form, choose whether to load the form theme, and style colors, fields and the submit button from the Style tab. A {cf_submission:field} token can print submitted answers in templates.

Bricks Builder support is built into Core Forms. Choose a form inside Bricks and render it without pasting a shortcode. It registers automatically when Bricks Builder is active, so there is no add-on or settings screen.

Fields, emails and actions are still built in Core Forms. The builder only places and styles the form, so the same form can live in several layouts.

Bricks Builder at a glance

Element
Core Form (General category)
Requires
Bricks active; registers automatically
Content controls
Form, show title, title tag, form theme
Style controls
Layout, colors, labels, fields, button, messages
Dynamic data
{cf_submission:field}
Assets
Loaded for forms in pages, templates and popups

Full reference: Bricks Builder integration

What you get

How Bricks Builder works in Core Forms

Native element

Bricks must be active; Core Forms registers its element and a dynamic data token automatically.

Form picker

Select the form in the element controls, choose whether this placement loads the Core Forms theme, and set colors, fields and the submit button in the Style tab.

One form, many layouts

Edit the form once in Core Forms and every page that embeds it updates.

Use cases

What people build with Bricks Builder and Core Forms

Contact form in a Bricks page

Drop the Core Form element into a section, choose the form, and it renders the same markup as the shortcode.

Forms in headers, footers and popups

Core Forms finds forms in active Bricks templates and popups and loads only the styles and scripts they need.

On-brand forms without custom CSS

Set an accent color and the focus ring, checkboxes and button glow follow it.

Submission detail templates

Print answers with {cf_submission:email} and similar tokens once your code tells Bricks which submission is in context.

Set it up

Connect Bricks Builder in 3 minutes

  1. 1

    Activate Bricks Builder

    Bricks must be active; Core Forms registers its element and a dynamic data token automatically.

  2. 2

    Add the Core Form element

    Edit a page in Bricks Builder, search the elements panel for Core Form, and drag it into the layout.

  3. 3

    Pick a form and publish

    Select the form in the element controls, choose whether this placement loads the Core Forms theme, and set colors, fields and the submit button in the Style tab. Check the live page before you publish.

Every setting, filter, and error message is documented in the Bricks Builder integration.

Good to know

Requirements and limits

  • Color, field and button controls set the form theme's CSS variables, so they do nothing when the form theme is off; typography controls work either way.
  • The element only places and styles a form: fields, emails and actions are still built in Core Forms.
  • The {cf_submission:field} token prints nothing until a filter supplies a submission for that context.
  • Until a form is selected, the live page renders nothing for that element.
FAQ

Bricks Builder integration questions

Do I need a shortcode to use Core Forms in Bricks?
No. Search the Bricks elements panel for Core Form, drag it into the layout and pick a form. It registers automatically when Bricks is active, with no settings screen.
Why don't my Bricks style controls change the form?
They set the form theme's CSS variables, so the theme has to be loaded. Set Form theme to Load the form theme on the element, or style the form with typography controls and your own CSS.
Can the same form look different on two pages?
Yes. The element's form theme choice and style controls apply to that placement only, and the form's saved setting stays untouched.
How do I show submitted values in a Bricks template?
Use the {cf_submission:field_name} dynamic tag and return the right submission from the cf_bricks_dynamic_submission filter. Without the filter, or with a wrong field name, the token renders empty. See the Bricks integration docs.
Does the element behave differently from the shortcode?
No. It renders the same markup as the [cf_form] shortcode and the block, so validation, conditional fields and actions behave identically.
Why is the Core Form element missing from the panel?
Bricks must be active on the site, because the element only registers when Bricks' element classes exist. Using Elementor instead? See the Elementor widget.

Bundled with every Core Forms license.

Bricks Builder and every Core Forms-built integration on this site are included with your license.