Releases: backdrop-contrib/node_revision_limit
Releases · backdrop-contrib/node_revision_limit
1.x-1.0.1
Bug Fixes
- Admin overview now correctly shows "Revisions disabled" for content types where Backdrop
revisions are turned off, rather than showing "Unlimited" for all types regardless of
their revision setting. Was reading the wrong config key (node_optionsinstead of
revision_enabled).
1.x-1.0.0
Initial Release
- Per content type revision limit — Adds a "Maximum previous revisions to keep" field
to each content type's revision settings. Leave blank for unlimited, set to 0 for no
previous revisions, or set to N to keep the N most recent old revisions. - Automatic pruning on save — On every node save, old revisions beyond the limit for
that content type are deleted immediately. No manual intervention required. - Cron queue for bulk pruning — When a limit is set or tightened on a content type,
all existing nodes of that type are queued automatically. The queue is processed in
30-second chunks during each cron run, avoiding timeouts on large sites. A "Queue prune
for all limited types now" button is also available on the admin overview page. - Draft Workflow safe — Only revisions older than the current revision (vid < node.vid)
are ever pruned. Forward draft revisions (vid > node.vid), as used by Draft Workflow and
Revisioning, are never touched. - Admin overview — Summary page at Admin → Configuration → Content → Node Revision Limit
showing each content type, its configured limit, and total node count. - No extra database tables — Settings stored within Backdrop's existing content type
CMI config (node.type.{type}), the same pattern used by Draft Workflow. - Backdrop Native: built for Backdrop CMS, not a port of a Drupal 7 module.