LIUER BOX
Liuer Box compatibility with REEID Translate
Liuer Box compatibility with REEID Translate is being evaluated from available plugin evidence. Visual field-group builder to create field groups, add fields, drag to reorder, and choose display locations (e.g., options pages, post types/meta boxes, taxonomy terms, user profiles, page templates). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Liuer Box.
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
Liuer Box is documented in the Other category with 7 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 Liuer Box 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
- Visual field-group builder to create field groups, add fields, drag to reorder, and choose display locations (e.g., options pages, post types/meta boxes, taxonomy terms, user profiles, page templates).
- Clean native storage model: single field values stored in one native post/term/user meta row; complex fields (e.g., repeater/gallery/link) stored as a single JSON row; global options consolidated into a single `liuer_box_options` row.
- Repeater support with drag-sort rows, collapse, min/max, dynamic row labels, and nested repeaters (repeaters inside repeaters).
- Conditional logic to show/hide fields based on another field’s value, evaluated both client-side and server-side.
- Developer API for reading/writing values using functions such as `liuer_option()`, `liuer_field()`, `liuer_term()`, `liuer_user()` and setters like `liuer_update_field()`, `liuer_update_term()`, `liuer_update_user()`, `liuer_update_option()`, plus group registration via `liuer_box_register()`.
- Optional safe output helpers that echo escaped output (e.g., `liuer_e()`, `liuer_attr_e()`, `liuer_url_e()`, `liuer_img()`, `liuer_wysiwyg()`, `liuer_embed()` and corresponding `liuer_option_*` variants).
- No plugin dependencies: states it has zero plugin dependencies and uses WordPress core APIs plus bundled jQuery, `wp.media`, and the WP color picker.
CONTENT BOUNDARY
Liuer Box 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
Liuer Box and REEID Translate FAQ.
What does Liuer Box do according to the available plugin evidence?
Liuer Box has 7 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 Liuer Box?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Liuer Box?
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 Liuer Box in a multilingual WordPress workflow.
REEID documents Liuer Box 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.