WPForms Styler

Embed an existing WPForms form and customize its appearance directly in Bricks. The styler renders the source form; it does not replace WPForms's form builder, submission handling, or email configuration.

Setup and First Use


Before starting, enable the relevant element or feature family under Bricks → BricksUltimate → General Elements, save, and reopen the Bricks editor. Integrations also require their corresponding plugin to be active.

  1. Install and activate WPForms, then create and save the form in that plugin. Test its basic behavior before styling.
  2. Enable WPForms Styler under Bricks → BricksUltimate → General Elements and reopen the editor. The integration may be unavailable if its required plugin is inactive.
  3. Add (BU)WPForms Styler. Start with Source Type set to Choose from dropdown and select the saved Form.
  4. Style the form wrapper, labels, input fields, submit controls, and available feedback groups.
  5. If the form should change per record, switch Source Type to the available dynamic/custom-field mode and provide the intended form ID source.
  6. Save and test the frontend at desktop and mobile widths, including invalid input and a successful submission.

Controls and Settings


ControlPurpose and usage
Source Type / FormChoose a saved WPForms form for static placement, or the supported dynamic mode for record-specific forms.
Dynamic sourceCustom Field reads a current post or supported term meta key containing the WPForms form ID. The result must be a scalar ID for a form that exists on this site.
Wrapper / Input stylesUse width, spacing, typography, padding, backgrounds, borders, shadows, placeholders, and focus styles where offered. Avoid a fixed width that exceeds the form container.
Show title / Show descriptionControl form heading and description output and their typography.
Labels and help textStyle sublabels, asterisks, descriptions, and description padding while preserving meaningful labels.
Radio/CheckboxSet spacing, size, label typography, and alignment for supported controls.
FeedbackUse the available message and error groups and test their rendered states rather than styling only an empty form.

WPForms Styling Scope


The element renders the selected WPForms shortcode. Form fields, available field types, conditional logic, spam protection, payment processing, notifications, and confirmations remain WPForms responsibilities and can depend on its edition. If a modern WPForms theme or custom stylesheet overrides appearance, inspect selector priority before adding broad site-wide CSS.

Dynamic Forms and Template Context


Store the form ID in the correct record metadata and preview a record that contains it. A post-based field and a term-based field are not interchangeable. Test at least two records with different IDs and one without a value. Keep one unambiguous source; do not assume an empty field will select a useful default form.

Submission, Email, and Accessibility


Configure recipients, sender settings, confirmation text, consent, spam protection, and any SMTP integration in WPForms or the relevant site email setup. Styling cannot repair mail delivery. Keep actual labels and clear error text; placeholders alone are not sufficient labels. Test keyboard focus and conditional fields. For popup/off-canvas use, test initialization on the first open and after AJAX updates.

Practical Example


Create a newsletter or contact form in WPForms, hide its form title only if a suitable page heading already exists, style the visible labels and submit button, and test success and required-field errors.

Troubleshooting


  • Form missing: activate WPForms, save a form, enable the styler, and reopen Bricks.
  • Wrong form: inspect Source Type and the resolved form ID for the current record.
  • Some fields ignore styling: inspect third-party field markup, the selected style group, and competing form-plugin CSS.
  • Validation or email fails: test the original form and its processing/mail settings independently of BU styling.

Related Documentation