BETTER REVISION HISTORY
Better Revision History compatibility with REEID Translate
Better Revision History compatibility with REEID Translate is being evaluated from available plugin evidence. Replaces the default revision comparison screen with a timeline-style “Revision History” meta box inside the post editor (for enabled post types). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Better Revision History.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Better Revision History is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Better Revision History compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Replaces the default revision comparison screen with a timeline-style “Revision History” meta box inside the post editor (for enabled post types).
- Records field-by-field changes on each save and displays before → after comparisons with old values highlighted and new values highlighted.
- Supports standard Posts and Pages out of the box, and can be enabled for custom post types via a settings page listing detected post types.
- Integrates with Advanced Custom Fields (ACF) by auto-detecting applicable ACF field groups/flat fields/repeater sub-fields per post type (using ACF’s field group registry) and performs repeater row-level diffing (Added/Updated/Removed).
- Provides a fallback mode when ACF is not active by comparing all non-internal (non “_”-prefixed) post meta keys.
- Includes a settings page at “Settings → MDI Revision History” to enable/disable tracking per post type.
- Groups multiple saves within the same timestamp into a single timeline entry and shows author & timestamp for each revision entry.
- Claims lightweight operation: no JavaScript, no external dependencies, and no database tables; it reads existing revision data and runs on post-edit screens for enabled post types.
CONTENT BOUNDARY
Better Revision History capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Better Revision History and REEID Translate FAQ.
What does Better Revision History do according to the available plugin evidence?
Better Revision History has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Better Revision History?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Better Revision History?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Better Revision History in a multilingual WordPress workflow.
REEID documents Better Revision History functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.