Active installations10Adoption metric — not a quality score
WordPress.org rating5.0 / 5 from 1 ratings
Official packageDirect from WordPress.org
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records Simple Editor Control – File History, Diff & Restore version 6.0.0 as active, updated 2mo ago and tested up to WordPress 7.1.
Overview
About this plugin
php in Appearance → Theme File Editor, saved, and the site went down. Or a plugin file was quietly modified and you want to know who, when, and what exactly changed.
Simple Editor Control records every save made through the WordPress theme and plugin file editors — automatically, with zero setup. For each save it stores the complete file, compressed and sealed with a SHA-256 integrity hash, along with the user and the timestamp.
History you can trust
Every revision stores the full file content — revisions are independent, so your history can never drift or corrupt.
The very first tracked save also captures the file as it was before the change, so the original state is always recoverable.
A save is only recorded after WordPress actually wrote it. Saves that core refused or rolled back (fatal PHP error) never pollute the history.
SHA-256 integrity check on every read: a corrupted revision is detected and refused, never silently written to disk.
Diffs worthy of git
Real Myers diff algorithm (jsdiff) rendered by diff2html — side-by-side or unified, with syntax awareness.
Instant context switching (0 to 25 lines) with no server round-trip.
Added/removed line counts on every revision in the timeline.
Compare any two revisions of a file, not just consecutive ones.
Restore without fear
One-click restore of any revision (arm, then confirm — no accidental clicks).
Before overwriting, the current on-disk content is snapshotted as a new revision: a restore can never lose data, even changes made outside WordPress.
When restoring a PHP file of an active plugin or theme, the site is probed afterwards; if a fatal error is detected, the previous content is put back automatically. No white screen.
Restore requires the same capabilities as the core editors, and is disabled entirely when DISALLOW_FILE_EDIT is set — the audit trail never becomes a policy bypass.
Respectful of your site
Old revisions are pruned automatically (configurable, default: last 100 per file).
Deactivation keeps your history; deletion removes everything, including database tables.
All third-party libraries are bundled with human-readable sources: jsdiff (BSD-3-Clause) and diff2html (MIT).
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
file editor
audit
diff
restore
revisions
Compatibility & maintenance
Compatibility & maintenance
Tested with WP 7.1
Marked as tested with the current WordPress 7.1 release.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 5.5 · PHP 7.4
Update activity25 Aug 20262mo ago
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
Changes recorded by WP PlugIndex
Recent tracked changes
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
Tracking & source
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
