2.0 Beta

Smootify 2.0 is in public beta. Your 1.x store keeps working. Move when you want.

What changed

metaobject-editor

2.0: the logged-in customer edits or deletes an entry they own, one a metaobject-creator[customer-field] made (a gift list, a warranty registration). The entry is the one smootify-metaobject would show: data-handle-param (the page url's parameter), else data-id, else data-handle, with data-type. Its form is filled with the entry (a text its value, a lone checkbox true, the checkboxes of a list the values in it, a radio or a select its value, a data-quantity-for input its product's count, a file-input its saved files) and sends its fields as metaobject-creator does, as an update. Only the customer whose id is in customer-field gets is-owner and a working form; anyone else, or logged out, gets neither (hidden by skeleton.css, form inert), and the backend checks the token's customer against the entry again ("This entry belongs to another customer"); the customer field itself never changes. button[data-action="delete"] deletes the entry, after data-confirm="<question>" when set, and takes it out of the customer's smootify.<type> list; then is-deleted on the host (form inert) and data-redirect="<url>" goes there; a refusal shows in the form's .w-form-fail.

v2.0 betaServer planAdd-on: Metaobject creator
Open .md
On this page
  1. Where it can go
  2. What it requires
  3. Fields in the form
  4. Attributes on the element
  5. Attributes inside it

Where it can go

  • Anywhere on the page.
  • Must contain form.
  • Out of place, Smootify removes it from the page: also without a form, data-type, customer-field or the entry, or when the entry is not found.

What it requires

  • The server plan: on other plans Smootify removes the element from the page.
  • The Metaobject creator extension (server plan, the extension activated in the Smootify dashboard, the licensed domain). Without it, its markup is removed from the page.

Fields in the form

Each field’s Name setting in Webflow tells Smootify what the field holds. It is a setting of the field, not a custom attribute.

NameFieldWhat it does
as metaobject-creatorany fieldAs metaobject-creator, filled with the entry first; the customer-field key is ignored.

Attributes on the element

  • It reads data-type, customer-field, data-handle-param, data-id, data-handle, data-confirm.
  • It reads data-redirect on .
  • Smootify writes is-owner, is-deleted on it: do not set them yourself.

Attributes inside it

GroupAttribute nameValues
Metaobject form buttonsdata-action2

    ↑ ↓ to moveEnter to openEsc to close