Revisions

Each time a fieldset is saved, VX keeps a copy of its configuration: the fields, the Locations and the general settings. The Revisions tab lists those copies so you can see what changed and go back.

Revisions cover the fieldset's design, not the content. The values editors typed into posts, terms and users aren't part of them. For a post's own history, use WordPress's post revisions, which are a separate feature.

What you can do with a revision

• Compare with current: see, side by side, what differs between that revision and the fieldset as it is now.
• Restore: make that revision the current configuration. What you had before is kept as a new revision first, so a restore can itself be undone.
• Download: save the revision as a file you can import later, on this site or another one, with Import / Export. When you import it, you can bring back only some parts: the fields, the Locations, the general settings, or the active state.
• Delete: remove a revision you don't need.

Limits

• VX keeps the 15 most recent revisions for each fieldset and removes older ones automatically.
• A revision is only recorded when something actually changed. Saving without changes doesn't add one.
• If the fieldset is defined in a PHP or JSON file and the dashboard is read-only for it, you can still compare and download revisions, but Restore is unavailable, because the file is the source of truth. See Config as code.

Restoring and stored values

Restoring an older revision can bring back a field you've since removed, or remove one you've since added. The values themselves are untouched. A removed field's values stay in the database and show up in Meta Watch; a returning field picks its old values up again, as long as its key is unchanged.

Technical details for LLMs

• Stored in {prefix}vxframework_config_revisions, deduplicated by a canonical hash of the config. Default limit 15 per entity (vxframework/config_revisions/max_per_entity).
• Revisions exist for every config object (post types, taxonomies and fieldsets). The dashboard tab is fieldsets-only; vx-framework/list-revisions, vx-framework/get-revision and vx-framework/restore-revision reach every type.
• Recorded on dashboard saves, config file writes and deletes, discarded database copies, and before every ability write.
• Hooks: vxframework/config_revisions/before_persist, recorded, before_restore, after_restore; filters record, canonical_config.
• Content (post) revisions are separate: vx-framework/restore-content-revision.