Editor panel overview
The editor panel lets you edit the current record in context, directly on the front-end, with no switch to wp-admin.
Where it appears
Section titled “Where it appears”The panel is available in two places.
- Singular views, meaning a single post, page or custom post type.
- Term archives, meaning a category, tag or custom taxonomy archive.
It shows as a floating button. Opening it reveals the fields for the current record, covering core fields, ACF fields and SEO, depending on what’s present.
Who can see it
Section titled “Who can see it”Visibility follows WordPress capabilities. The panel only appears for users who may edit the current record. Logged-out visitors never see it, and assets are only loaded when the panel is actually shown.
Content fields
Section titled “Content fields”The content fields tab builds a form from the record’s custom fields, in the order set in the field group configuration (the same order as the wp-admin edit screen). A field added to a group later appears where you placed it, not at the bottom.
Text fields that have no value yet still show up, as empty inputs. Filling one in saves it with the rest of your changes. An input you leave empty is not sent at all, so opening the panel and saving never writes empty values into fields nobody touched.
Saving with a dry-run preview
Section titled “Saving with a dry-run preview”Before every save, the panel runs a dry-run and shows exactly what will change, including any warnings. Nothing is written until you confirm. After saving, the page reloads with your change applied and the scroll position restored.
Edit-conflict protection
Section titled “Edit-conflict protection”The panel uses optimistic locking. When you open a record, its last-modified state is captured. If someone else saves a change before you do, your save is stopped and you’re told about the conflict instead of silently overwriting their work. You can then reload the current version and re-apply your change.
Relation to the other surfaces
Section titled “Relation to the other surfaces”The panel writes through the same pipeline as the REST API and bulk import, so identity and validation rules are identical. What you can do in the panel, you can do over the API, and vice versa.