Choose fields and configure validation

Choose the right field type

Every field in this guide is included in Drecha Forms Free.

Essentials

• Single-line text for short answers.
• Paragraph text for longer messages.
• Email for a validated email address.
• Phone for telephone details.
• Number for numeric input.
• Website URL for a validated web address.

Choices

• Dropdown for one option in a compact menu.
• Radio buttons for one visible choice.
• Checkboxes for one or more choices.
• Consent checkbox for explicit acceptance.

Date and time

• Date.
• Time.
• Date and time.

Advanced

• Rating and Range slider.
• File upload and Multiple files.
• Address and Name.
• Password.
• Calculated display.

Structure

• Hidden field.
• HTML/content.
• Heading and Divider.
• Page break for a multi-step form.

HTML/content is sanitized when saved and rendered; it cannot be used to execute arbitrary JavaScript. A Password field disables defaults and URL prefilling. Drecha Forms validates the answer, then replaces it with null before storage, submission hooks, email, or integrations receive the accepted payload. It does not create a WordPress user account.

Configure the general field settings

1. Select a field on the canvas.
2. Enter a clear Label and optional Description.
3. Add a Placeholder only when it provides a useful example; it does not replace a visible label.
4. Enable Required when every visible respondent must answer.
5. Set a Default value only when preselecting an answer is appropriate.
6. Review the generated field Key before using it in calculations or email placeholders.

Field keys must be unique and cannot begin with the reserved _drecha_ prefix. Choice fields need at least one option, and each option must have a unique, non-empty stored value.

Add validation and useful errors

Validation depends on the field type:

• Text, email, phone, URL, and password fields can use minimum and maximum lengths. Supported text formats include alphanumeric and no-whitespace rules.
• Number, range, and rating fields can use minimum, maximum, and step values.
• Upload fields can limit allowed extensions and file size. Multiple uploads can also limit the number of files.
• Email, URL, date, time, and date-time values are validated again on the server.
• A required Name needs first and last name. A required Address needs address line 1, city, postal code, and country.
• A required Consent checkbox must be accepted.

Enter a Custom error message when the default message does not explain how to correct the answer. Keep it specific, such as “Enter your booking reference using letters and numbers only.”

Browser-side checks help visitors immediately, but the server repeats validation and never trusts browser data alone.

Configure layout and accessibility

Choose desktop widths of 25%, 33%, 50%, 66%, 75%, or 100%. Tablet and mobile can use Auto, 50%, or 100%. Place compatible fields next to each other, but use full width for long answers and small screens when readability matters.

You can also set sanitized CSS classes, an accessible label, and a supported browser autocomplete value. URL prefilling is available for supported input fields; do not enable it for sensitive values. Password fields never accept URL prefilling.

Use conditional logic and form-level validation

Visibility rules can show or hide a field when all or any configured conditions match. Conditional-required rules can make a visible field required only in a matching situation. Drecha Forms checks dependencies and rejects circular rule chains.

Form-level validation can require two fields to match or not match. A common example is matching an Email field with a Confirm email field. Calculated display fields use a restricted expression engine rather than eval, and circular calculations are rejected.

Review the form settings

Open the form settings panel to configure:

• Submit button label.
• A confirmation message or an HTTPS redirect URL after success.
• Entry retention from 0 through 3650 days; 0 keeps entries until an administrator deletes or erases them.
• Spam threshold from 20 through 100; lower values are stricter, and spam does not trigger email.
• Clean, High contrast, or Minimal theme and Comfortable or Compact density.
• Progress bar, step count, or no indicator for a multi-step form.
• Administrator and respondent email settings.

Free and Pro differences

All listed fields, conditional visibility, conditional required fields, form-level matching rules, safe calculations, layouts, URL prefilling, multi-step forms, validation, and basic themes are included in Free. Pro is not needed to validate or render these fields. Advanced Pro products may add integrations, but they use the same Free schema and renderer.

Troubleshoot fields and validation

The form will not save after changing field keys

Check for duplicate keys and update any calculation, conditional rule, or email placeholder that uses the old key. Keys beginning with _drecha_ are reserved.

A hidden field is still reported as required

Review its visibility and conditional-required rules. The server evaluates visibility before required validation; contradictory or circular dependencies are rejected when saving.

An upload is rejected

Check the allowed extension, verified MIME type, per-file size, multi-file count, and server upload limits. Executable uploads are never allowed even if a filename has been disguised.

A password is absent in the stored entry

That is intentional security behavior. Drecha Forms can enforce the configured length or format during validation, but it replaces the accepted value with null before storage, submission hooks, email, or integrations receive the payload. Do not use this field for authentication or account creation.