Gravity Forms Styler

Embed an existing Gravity Forms form and customize its appearance directly in Bricks. The styler renders the source form; it does not replace Gravity Forms'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 Gravity Forms, then create and save the form in that plugin. Test its basic behavior before styling.
  2. Enable Gravity Forms Styler under Bricks → BricksUltimate → General Elements and reopen the editor. The integration may be unavailable if its required plugin is inactive.
  3. Add (BU)Gravity Forms 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 Gravity Forms form for static placement, or the supported dynamic mode for record-specific forms.
Dynamic sourceCustom Field or Dynamic Tag supports a field key containing the Gravity Forms form ID or the separate Dynamic Tag value. Ensure it resolves to an existing form in the preview/current context.
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 description?Choose which form-level texts are output and style them separately.
Enable Ajax? / Tab IndexConfigure the exposed embed behavior deliberately. Verify keyboard order before using a custom tab index.
Field detailsStyle labels, sublabels, descriptions, required text, inputs, textarea, placeholder, focus, checkboxes/radios, and upload button.
Steps and progressConfigure the available current/total page and percentage/progress-bar styles for multi-page forms.

Gravity Forms Embed and AJAX


The element embeds a Gravity Forms shortcode with the selected title, description, AJAX, and tabindex options. The source form still controls fields, notifications, confirmations, conditional logic, and payments. A form injected later into an AJAX popup can need its own initialization; successful embedding on a static page does not prove that popup workflow.

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 Gravity Forms 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 two-page quote form in Gravity Forms. Enable its intended AJAX behavior in the styler, style sublabels and the progress indicator, and test moving back/forward as well as an invalid final submission.

Troubleshooting


  • Form missing: activate Gravity Forms, 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