Extend Revisions for Custom Fields and Taxonomies

WordPress revisions do not normally include custom fields or taxonomies. This plugin extends revisions to include taxonomies and custom fields from PODS etc, allowing previous states to be captured, compared & restored as expected.

Usage
There is no user interface, once installed and activated it will start
capturing custom field and taxonomy information. The rest is stock WordPress revision functionality, except that this plugin formats the extra data into an easy to read format for display in the comparison screens.

The look for the compare screens can be changed in “settings.ini” (including turn off or changing the CSS used).

Features

• Taxonomies are saved as metadata with a key such as “$TAXONOMY:light_conditions” for the “light_conditions” custom category. The values are a list of “ID=Name” pairs. These would generally sort to the top (or close to it).

• WordPress limits how the data is presented in the “Compare Revisions” screen, so the data is displayed as an alphabetically sorted list of fields and their values.

• You can filter out metadata keys with one or more regular expressions if you don’t care about their values. Filtered out metadata is not saved, displayed or restored.

• Some CSS is applied to the WordPress “Compare Revisions” screen which I believe makes it easier to understand, however you can disable this by renaming or deleting the CSS file (or adjusting “settings.ini”).

• The unicode characters also make the output easier to read and you can change their values or remove them via “settings.ini”. For example, you can tell the difference between a repeating field and a single field with many lines.

• Note that the “Restore This Revision” button restores what is on the right hand column and explains why it is greyed out for the last revision slot.

Try it out
Try it for free at TasteWP

Reporting Issues
Please turn on both “debug” and “info” in settings, perform the failing
operation, and include the php log (part or all, if later specify the problem’s time as per the log)…
Please provide screenshots if possible.

1. 

   Example of "settings.ini" configuration.

2. 

   This shows what comparing revisions looks like with the DEFAULT CSS and options.