Piotnet Forms Styler
Embed an existing Piotnet Forms form and customize its appearance directly in Bricks. The styler renders the source form; it does not replace Piotnet 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.
- Install and activate Piotnet Forms, then create and save the form in that plugin. Test its basic behavior before styling.
- Enable Piotnet Forms Styler under Bricks → BricksUltimate → General Elements and reopen the editor. The integration may be unavailable if its required plugin is inactive.
- Add (BU)Piotnet Forms 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 Piotnet Forms form for static placement, or the supported dynamic mode for record-specific forms. |
| Dynamic source | Custom Field reads a current post or supported term meta key that contains the Piotnet Forms ID. Enter a form ID through that metadata source rather than pasting the form's whole embed markup. |
| 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. |
| Labels | Use Hide labels only when another accessible labeling strategy remains. Configure label typography independently. |
| Input Fields / Textarea | Style dimensions, padding, background, border, shadow, placeholder, and focus states. |
| Buttons and feedback | Style submit hover states and available messages without changing the form's own processing actions. |
Build Logic in Piotnet Forms
Create all fields, calculations, conditional sections, and after-submit actions in Piotnet Forms. BU invokes that form and styles its output. Keep plugin-specific CSS overrides and component styles in mind when a field does not respond to a generic input rule. Test complex widgets in the exact frontend environment where the form will appear.
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 Piotnet 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 service request form in Piotnet Forms and select it in the styler. Match labels, textarea, and submit button to the site, then test a conditional section and its validation with real input.
Troubleshooting
- Form missing: activate Piotnet 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.