Framework for storing revisions of Post Meta
|Reported by:||alexkingorg||Owned by:|
|Severity:||normal||Keywords:||needs-testing needs-codex needs-refresh|
|Cc:||nacin, markjaquith, scribu, info@…, rspindel, joachim.kudish@…, ipstenu@…, kovshenin@…, h@…, ryan@…, maorhaz@…, lol@…, dennen@…, lightningspirit@…, hello@…, bronson@…, jared@…, admin@…, jbrown510@…, adamsilverstein@…, dromsey@…, kwight@…, Ken@…, doughamlin@…, steph@…, peterherrel@…|
There are a couple of tickets that would seem to benefit from storing revisions of post meta (#11049, #20299). We had a need for this feature in our Carrington Build and RAMP products and built it a few years back.
It handles the storing of post meta along with revisions, as well as restoring those revisions when someone restores an older version of a post(/page/etc.). There is an API for registering the post meta keys you want to track revisions of, it does not track all post meta keys by default.
There are two versions of the code. The bare-bones revisions framework code is here:
while I started adding features to a version that would be more user-friendly plugin, allowing the users to select which post meta keys they want to track revisions for:
If this would be a valuable addition to core, I'd be happy to help polish this up in whatever manner is most helpful. I'd recommend breaking out the code I started on for the admin form and having that be the extent of the "revision manager" plugin - basically it becomes a nicer UI for selecting additional post meta keys to track revisions for.
Change History (94)
comment:41 DrewAPicture — 8 months ago
- Keywords needs-codex added
comment:53 in reply to: ↑ 49 ; follow-up: ↓ 55 azaozz — 8 months ago
- Keywords needs-refresh added
- Resolution fixed deleted
- Status changed from closed to reopened