META LEDGER
Meta Ledger – Track, compare, and restore post meta Changes compatibility with REEID Translate
Meta Ledger – Track, compare, and restore post meta Changes compatibility with REEID Translate is being evaluated from available plugin evidence. Automatic tracking of post meta changes for posts, custom post types, and WooCommerce products (including changes made via WordPress meta functions like `update_post_meta`, `add_post_meta`, and `delete_post_meta`). No specific visitor-facing translation surface is currently confirmed.
Visit Meta Ledger – Track, compare, and restore post meta Changes ↗
AWAITING VERIFICATION
What the available evidence establishes for Meta Ledger – Track, compare, and restore post meta Changes.
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
Meta Ledger – Track, compare, and restore post meta Changes 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 Meta Ledger – Track, compare, and restore post meta Changes 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
- Automatic tracking of post meta changes for posts, custom post types, and WooCommerce products (including changes made via WordPress meta functions like `update_post_meta`, `add_post_meta`, and `delete_post_meta`).
- Versioned history with timestamps, user information, and action types for tracked meta changes.
- Field-level diffs with side-by-side comparisons of old vs.
- new meta values.
- Restore functionality to revert a meta field to a previous version, with restore actions also recorded in history.
- Source tracking per history entry, including file path, line number, function name, and stack trace; changes made from the plugin UI are marked as “Meta Ledger UI”.
- Admin UI support including a meta box with tabs (e.g., “History”) and inline editing of meta values.
- Developer interfaces: REST API endpoints under `/wp-json/meta-ledger/v1/` for accessing history and restoring versions, plus WP-CLI commands (`wp meta-ledger show`, `wp meta-ledger restore`, `wp meta-ledger cleanup`).
Distinctive features
Automatic tracking of post meta changes for posts, custom post types, and WooCommerce products (including changes made via WordPress meta functions like `update_post_meta`, `add_post_meta`, and `delete_post_meta`). Versioned history with timestamps, user information, and action types for tracked meta changes. Field-level diffs with side-by-side comparisons of old vs. new meta values. Restore functionality to revert a meta field to a previous version, with restore actions also recorded in history. Source tracking per history entry, including file path, line number, function name, and stack trace; changes made from the plugin UI are marked as “Meta Ledger UI”. Admin UI support including a meta box with tabs (e.g., “History”) and inline editing of meta values. Developer interfaces: REST API endpoints under `/wp-json/meta-ledger/v1/` for accessing history and restoring versions, plus WP-CLI commands (`wp meta-ledger show`, `wp meta-ledger restore`, `wp meta-ledger cleanup`). Compatibility scope claims: supports WooCommerce products and High-Performance Order Storage (HPOS) orders, tracking product and order meta changes (including prices, stock, custom fields, and order meta edited via WooCommerce CRUD APIs).
CONTENT BOUNDARY
Meta Ledger – Track, compare, and restore post meta Changes 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
Meta Ledger – Track, compare, and restore post meta Changes and REEID Translate FAQ.
What does Meta Ledger – Track, compare, and restore post meta Changes do according to the available plugin evidence?
Meta Ledger – Track, compare, and restore post meta Changes 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 Meta Ledger – Track, compare, and restore post meta Changes?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Meta Ledger – Track, compare, and restore post meta Changes?
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 Meta Ledger – Track, compare, and restore post meta Changes in a multilingual WordPress workflow.
REEID documents Meta Ledger – Track, compare, and restore post meta Changes 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.