QUERY FORGE
Query Forge compatibility with REEID Translate
Query Forge compatibility with REEID Translate is being evaluated from available plugin evidence. Visual node-based interface for building queries without code No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Query Forge.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Query Forge is documented in the Page Builder 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 Query Forge 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 node-based interface for building queries without code
- Supports querying Posts, Pages, and all Custom Post Types
- Works with both Gutenberg block editor and Elementor
- Advanced filtering by taxonomy, meta fields, and custom conditions
- Flexible sorting options including Date, Title, ID, and Meta Value
- Fully styled card grid display with customizable design controls
- Query result caching to improve performance
- Pro version supports multiple data sources including SQL tables and REST APIs
CONTENT BOUNDARY
Query Forge 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Query Forge and REEID Translate FAQ.
What does Query Forge do according to the available plugin evidence?
Query Forge 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 Query Forge?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Query Forge?
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 Query Forge in a multilingual WordPress workflow.
REEID documents Query Forge 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.