PERSISTENT FILTERS
Persistent Filters compatibility with REEID Translate
Persistent Filters compatibility with REEID Translate is being evaluated from available plugin evidence. Preserves and reapplies WordPress admin list filters for Posts, Pages, and WooCommerce listings (including Products, Orders, and Coupons). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Persistent Filters.
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
Persistent Filters is documented in the Other category with 6 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 Persistent Filters 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
- Preserves and reapplies WordPress admin list filters for Posts, Pages, and WooCommerce listings (including Products, Orders, and Coupons).
- Remembers admin list filter selections such as search terms, ordering, and statuses, and reapplies them when returning to the corresponding admin list screen.
- Stores filter selections per user and per listing (each post type/listing maintains its own stored filters).
- Adds a “Reset Filters” button next to admin list filter options when filters have been used for the current post type/listing.
- Provides an option to remove all filters via an admin “Reset all filters” link, with a choice to remove filters for only the current user or for all users.
- Does not affect front-end queries; it only saves and reapplies admin list screen query parameters.
CONTENT BOUNDARY
Persistent Filters 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
Persistent Filters and REEID Translate FAQ.
What does Persistent Filters do according to the available plugin evidence?
Persistent Filters has 6 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 Persistent Filters?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Persistent Filters?
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 Persistent Filters in a multilingual WordPress workflow.
REEID documents Persistent Filters 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.