WS Forms Styler
Embed an existing WS Form form and customize its appearance directly in Bricks. The styler renders the source form; it does not replace WS Form'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.
- Install and activate WS Form, then create and save the form in that plugin. Test its basic behavior before styling.
- Enable WS Forms Styler under Bricks → BricksUltimate → General Elements and reopen the editor. The integration may be unavailable if its required plugin is inactive.
- Add (BU)WSForms Styler. Start with Source Type set to Choose from dropdown and select the saved Form.
- Style the form wrapper, labels, input fields, submit controls, and available feedback groups.
- If the form should change per record, switch Source Type to the available dynamic/custom-field mode and provide the intended form ID source.
- Save and test the frontend at desktop and mobile widths, including invalid input and a successful submission.
Controls and Settings
| Control | Purpose and usage |
|---|---|
| Source Type / Form | Choose a saved WS Form form for static placement, or the supported dynamic mode for record-specific forms. |
| Dynamic source | Use Custom Field Name for a metadata value that resolves to the WS Form ID. This implementation also has a dynamic/scalar fallback when metadata is empty; confirm the resolved ID in the current post or term context before relying on it. |
| Wrapper / Input styles | Use width, spacing, typography, padding, backgrounds, borders, shadows, placeholders, and focus styles where offered. Avoid a fixed width that exceeds the form container. |
| Form, labels, and required text | Style wrapper rows, alternate backgrounds, labels, help text, asterisks, and required-field messages. |
| Inputs and focus | Control field dimensions, textarea, placeholder, border, shadow, disabled states, and focus presentation. |
| Specialized controls | Dedicated styles cover supported checkboxes, radios, range tracks/thumbs, progress, files/remove links, dividers, and tabs. |
| Button variants / Messages | Style default/primary, secondary, success, information, warning, and danger variants according to what the source form actually outputs. |
WS Form Tabs, Files, and States
Create form sections, tabs, upload rules, conditional actions, and validation in WS Form. Use BU to style the states those features render. Test file names, file-size text, remove links, inactive/active tabs, disabled fields, and success/error messages with real data; these states may not all be visible in the initial builder preview.
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 WS Form 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 tabbed request form in WS Form with an upload field. Select it in the styler, style tabs and primary/secondary buttons, then test required fields, upload removal, tab navigation, and final confirmation.
Troubleshooting
- Form missing: activate WS Form, 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.