Field Forge tracks every change to every field group as a revision with author, timestamp, and full diff. Accidentally broke a field group? Rolled out a bad change? One-click rollback restores any previous version. No other WordPress custom fields plugin has this feature.
WordPress has revision history for posts (since 2.6). Every post edit is saved as a revision, and editors can revert to any previous version. This is so fundamental to WordPress that nobody thinks about it anymore — it’s just expected.
Field groups don’t have this. In ACF, SCF, Meta Box, CMB2, Carbon Fields, Pods, Toolset, and every other major custom fields plugin, editing a field group is a destructive operation. You save changes and the previous state is gone. If you accidentally delete a field, you can’t recover it. If a change broke a template, you can’t roll back.
Field Forge fixes this with a revisions table: wp_fieldforge_revisions. Every field group save creates a new revision. You can view the diff between any two revisions, and restore to any previous version with one click.
When you save a field group in Field Forge’s visual builder, the plugin:
wp_fieldforge_revisions with: – group_id (the field group being versioned)
– revision_data (the serialized JSON)
– revision_hash (MD5 of the JSON)
– user_id (who made the change)
– created_at (timestamp)
– change_summary (optional note about what changed)
This happens on every save, automatically.
In Field Forge’s visual builder, click the History icon at the top of any field group. A modal opens showing the complete revision history:
Each revision shows the author, timestamp, and (optionally) a change summary.
Click any two revisions to see the diff:
The diff view shows exactly what changed between the two revisions, so you can understand the impact before restoring.
Click Restore to this revision on any historical revision. Field Forge:
The restore is immediate and reversible. If you restored to the wrong revision, just restore again to the most recent one.
The revisions table grows over time, so Field Forge auto-prunes old revisions:
For teams that want longer history, the cap is configurable via filter:
add_filter('fieldforge/revisions/max_per_group', function($max) {
return 200; // Keep 200 revisions per group
});Field group JSON can be large. For sites with hundreds of field groups and many revisions each, the revisions table could grow rapidly. Field Forge stores revisions with gzip compression — typical compression ratio is 5–10x — so a 50 KB field group revision takes 5–10 KB in storage.
An editor or admin accidentally deletes a critical field. Without versioning, the data is gone and the theme templates that reference that field break silently. With Field Forge versioning, restore the previous revision in 10 seconds.
You edited a field group on staging and deployed to production, but the change introduces a bug. Roll back to the previous revision, investigate the bug, re-deploy with the fix.
Experimenting with different field group structures? Save as revisions, compare, pick the winner. Every iteration is preserved.
Two team members edit the same field group on different environments. Both saves create revisions. Diff the two versions to see the conflict, merge manually, save as a new revision.
For compliance-heavy environments (healthcare, finance, legal), having a full audit trail of field group changes is often a regulatory requirement. Field Forge’s revisions table provides this automatically.
Schema versioning and Local JSON Sync work together:
Git history covers the “what did we deploy” question. Schema versioning covers the “what happened since we deployed” question. Together they cover both worlds.
As of 2026, no other WordPress custom fields plugin has a native revision history with rollback for field groups:
Field Forge is the only option with built-in schema versioning.
Get Field Forge — from $35/year →
Schema versioning is included in every paid plan.