Skip to content

Missing or moved forms

Forms are identified by their Basin ID, the last part of https://usebasin.com/f/demo0contact. The ID stays the same when a form is renamed, so renaming is always safe. Two other changes in Basin can break things quietly:

The form still accepts submissions, but they no longer appear in this site’s Control Panel, because the site only shows forms in its linked project. Nobody sees an error.

Visitors who submit it see Basin’s error page, and their message is lost.

When a template, a Basin Form field or a GraphQL query asks for a form that isn’t in the linked project, the plugin:

  • returns null, so a template wrapped in {% if form %} leaves the form out, instead of showing visitors a form that can’t work (craft.basin.render() does this for you);
  • records it in the error log, with the form’s ID, the page it was used on, and when.

It does the same for Basin forms in hard-coded markup it finds on your pages, as long as Add spam protection automatically is on. Those it can only log: the form stays on the page.

  • The form was moved by mistake: move it back to the linked project in Basin. The entry clears itself.
  • The form was replaced: update the template, or choose the new form in the field.
  • You’ve dealt with it: click Dismiss in the error log. If the form is used again, the entry comes back.

To turn tracking off, turn off Track missing forms in the settings.

The plugin keeps a copy of your forms list, so forms keep working on your site during a Basin outage, and nothing is reported as missing. Front-end pages never wait more than a few seconds for Basin.