Form limitations

When a form cannot be reproduced exactly, Wigoh records a limitation: one plain sentence per change. Limitations appear in the build progress, in the assistant's reply when it creates a form, and in the site's build report. Each has a severity: warn for something to check, info for something to know.

Limitation	Severity	Sentence you see
Third-party form replaced	warn	The original page used a [provider] form embed. Its fields could not be read, so it was replaced with a standard contact form (name, email, phone, message).
Multi-choice as checkboxes	warn	"[Field]" allowed several choices. CRM forms cannot, so each choice is now its own checkbox.
Multi-choice as dropdown	warn	"[Field]" allowed several choices. It is now a single-choice dropdown.
Consent as checkbox	info	"[Field]" is a plain checkbox. The CRM does not record it as a formal consent.
Unsupported field dropped	warn	"[Field]" ([type]) is not supported by CRM forms and was left out.
Multi-step flattened	warn	The original form had several steps. The CRM form shows every field on one page.
Single-column layout	warn	CRM forms stack fields in one column by default. Side-by-side fields need custom form CSS.
Hidden field dropped	info	Hidden field "[name]" was left out. The CRM adds its own campaign tracking.
Name as first name	info	"[Field]" is stored as the contact's first name.
Fields capped	warn	The form had more than 30 fields. Only the first 30 were kept.
No usable fields	warn	No usable fields were found on the original form, so a standard contact form was created instead.

Reading them

Each is a fact about what changed, not an error. Review the form on the page and, if the simplification matters, ask the assistant to adjust: split a long form across two pages, reorder fields, or add a note explaining a checkbox.

Individual pages: Third-party embeds, Multi-choice fields, Consent checkboxes, Unsupported fields, Multi-step forms, Layout.