WPForms ability reference

What WPForms needs before these load

2 of the 29 also ship in GoBuildWP Free 1.18.6 under the same names, marked “Also in GoBuildWP Free” below. They need no GoBuildWP Pro licence, but each retains its own dependency, feature and permission checks. Where Free's copy does less, its own description follows Pro's. When Pro's richer copy passes its gates, it registers first and answers.

WPForms 1.8.0 or newer must be active, Lite or Pro. The gate checks the WPFORMS_VERSION constant and the wpforms() function; 1.8 is the release that settled the form and entry accessors this module calls. Pro is recognised by the WPFORMS_PLUGIN_SLUG constant or the pro/wpforms-pro.php file. Permissions go through wpforms_current_user_can() for the form or entry in question, with checks such as wpforms_view_forms, wpforms_edit_forms, wpforms_view_entries, wpforms_edit_entries and wpforms_delete_entries; a refusal is wpforms_capability_missing (403). Below the floor the wpforms category is not registered at all. The free plugin's wpforms-list-entries answers wpforms_pro_required on Lite just as Pro's does, and withholds email and phone answers with no way to reveal them.

Minimum (base)

1.8.0 WPPILOT_PRO_WPFORMS_MIN_VERSION

WPForms editions

free, pro

Agent skills shipped

wpforms-integration, form-model-schema, form-model-migration

A WPForms form is one post, so edits can be undone

Each form is a post of type wpforms whose post_content holds the whole definition as JSON: fields, settings, notifications, confirmations and payments. Edits check that the stored JSON is unchanged since it was read and fail with wpforms_concurrent_modification (409) if another editor got there in between. A post_content that no longer decodes stops every write with wpforms_form_corrupt instead of being replaced by an empty form.

Because the form is a post, the change ledger takes a before-image of it, and additions, edits, reorders and deletions of fields, notifications, confirmations and settings can be put back with wppilot/rollback-change. Deleting a form trashes it unless force=true is passed, which the ledger records as permanent. The module also refuses to remove a form's last notification or confirmation (wpforms_last_notification, wpforms_last_confirmation); edit it instead.

Why entry calls fail on WPForms Lite

WPForms Lite does not expose locally stored entries through the supported entry API. That is a statement about local storage only: any copy WPForms itself keeps for Lite users elsewhere is outside what this module can read. On Lite the entry calls return wpforms_pro_required, and the export answers wpforms_lite_no_entries, noting that submissions from before Pro was switched on are not available through this local entry API. On Pro, entries live in wpforms_entries, with one row per answer in wpforms_entry_fields and extra data in wpforms_entry_meta.

Entries have no trash. wppilot/wpforms-delete-entry removes the entry and its child rows at once, and the ledger records entry edits, deletions and read or starred flags as irreversible because they land in those tables. Edit-entry is held for confirm=true, refuses payment, signature, captcha and layout fields with wpforms_field_not_editable, and mirrors each change into wpforms_entry_fields so searches find the new value. Searches skip the fields get-entry redacts and never look at the IP, which sits on wpforms_entries; with include_meta, get-entry also redacts card, IP, token, password and signature keys inside the meta blob.

Pro field types such as file upload, payment and signature carry pro_only in the field catalog; on Lite, add-field treats them as unavailable and returns wpforms_unknown_type.

Representative call sequence

This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.

Add a phone field to the contact form, then take it out again after the client changes their mind.

1. 01 wppilot/wpforms-check-setup Reports whether Pro is present and lists available_field_types, confirming the phone type can be used on this install.
2. 02 wppilot/wpforms-add-field Appends the field with the form's next sequential field id; the ledger stores the form post as it was before the write.
3. 03 wppilot/list-changes Shows the add-field write against the form post with rollback available.
4. 04 wppilot/rollback-change Restores the form post to its before-image and verifies the result, removing the phone field.

Questions about WPForms