Kindly EditDocumentationTry the editor

Forms, fields, and actions

Build a native form, configure its behavior, and distinguish preview validation from real submissions.

Watch the video

Chapters and transcript Captions are included.

There are two kinds of form in Kindly Edit. This page covers the Simple form element: the quick built-in form you add to a page, whose fields and settings live in that page. For anything more, use Kindly Forms, the full forms system in Kindly Edit > Forms, with a builder, entries, emails, conditions, connections, payments, PDF documents and reports. A page form can be moved to Kindly Forms at any time, and the page Form element keeps working as described here.

Build the form#

Insert a Form, then edit its fields and labels. Give each input a meaningful visible label and stable name. Choose the appropriate input type, required status, placeholder, choice list, and validation limits. Keep the submit button's wording specific to the result.

The form's saved identity is data-cb-form on form.cb-form. Its public submission endpoint is associated with both the page ID and this identity. The server derives the allowed field schema from the published page, not a visitor-supplied schema.

Validation#

The server checks required fields, lengths, email and URL formats, phone fields, number and date/time ranges, allowed choices, and files. Browser validation improves feedback, but server validation is authoritative. Test empty required fields, malformed values, and a successful case.

An Email field without Required stays optional for visitors, so a form can ask for a second or optional address (Kindly Edit 0.9.18 and later; earlier releases made every email field required in the browser). The one exception is a sign-up whose only field to fill in is an email address, apart from tick boxes: Kindly Edit always requires that address, so the form can't be sent empty.

A form on a draft page is not a public submission form. The submission route requires a published page without password protection. When a visitor submits a stale field layout, the published schema still governs acceptance.

Actions#

Form settings can store a submission, send a notification email, send a second email, redirect, call a webhook, open a popup, and manage file delivery. Configure only the actions the form needs. Empty recipient settings do not establish a working notification route. Verify real email delivery with an authorized test recipient after publishing; an editor preview does not send it.

Private action settings are stored separately from public form markup in _cantata_edit_forms, with draft settings promoted alongside page publication. This prevents recipients and webhook settings from becoming page HTML.

Preview and publish#

  1. Save the form draft.
  2. Use Preview to inspect layout and validation without delivering a submission.
  3. Publish when the fields and actions are ready.
  4. Test the public page using safe test data.
  5. Verify each enabled destination: the submissions list, notification receipt, redirect target, webhook result, or popup.

This documentation's recorded demos use a local site with email disabled. They demonstrate configuration and validation, not production delivery.

Abuse handling and troubleshooting#

Native forms include a honeypot and rate checks. Repeated failures can be validation or rate-limit responses; inspect the actual error before retrying. Check that the form ID remains unique, the page is published, the field names match the saved schema, and the expected action settings were published.

See Submissions and uploads for private records and file handling.

About this page

Documents Kindly Edit 0.9.16. Source: includes/forms.php, assets/form-settings.js, assets/elements.js. Theme choices and account permissions can change which controls appear.

Type a word or phrase to search the full documentation.