RPWS TAXONOMY FILTER LITE
RPWS Taxonomy Filter Lite compatibility with REEID Translate
RPWS Taxonomy Filter Lite compatibility with REEID Translate is being evaluated from available plugin evidence. Provides an Elementor Pro widget (“Taxonomy Filter Lite”) intended to filter an Elementor Loop Grid using a dropdown UI. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for RPWS Taxonomy Filter Lite.
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
RPWS Taxonomy Filter Lite is documented in the Navigation 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 RPWS Taxonomy Filter Lite 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
- Provides an Elementor Pro widget (“Taxonomy Filter Lite”) intended to filter an Elementor Loop Grid using a dropdown UI.
- Filters one taxonomy per widget instance; multiple taxonomies require adding multiple filter widgets to the same page.
- Automatically detects registered post types and their taxonomies for use in filtering.
- Renders filtered states as bookmarkable/shareable by storing filter selections in URL parameters.
- Supports dropdown placeholder support and customizable hierarchy display depth for the taxonomy terms shown in the dropdown.
- Includes “Smart Loop Grid integration” to connect the dropdown filter selections to the Loop Grid filtering behavior.
- Offers empty-terms control options (i.e., configurable behavior when no terms are available).
- Provides full styling controls and supports a custom dropdown icon.
CONTENT BOUNDARY
RPWS Taxonomy Filter Lite 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
RPWS Taxonomy Filter Lite and REEID Translate FAQ.
What does RPWS Taxonomy Filter Lite do according to the available plugin evidence?
RPWS Taxonomy Filter Lite 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 RPWS Taxonomy Filter Lite?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for RPWS Taxonomy Filter Lite?
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 RPWS Taxonomy Filter Lite in a multilingual WordPress workflow.
REEID documents RPWS Taxonomy Filter Lite 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.