USAGERAY
UsageRay compatibility with REEID Translate
UsageRay compatibility with REEID Translate is being evaluated from available plugin evidence. Read-only plugin usage and dependency auditing for administrators (site-wide audit and per-plugin scans) No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for UsageRay.
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
UsageRay 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 UsageRay 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
- Read-only plugin usage and dependency auditing for administrators (site-wide audit and per-plugin scans)
- Adds a “Find usage” action on the Installed Plugins screen and integrates “Deactivation Preflight”/bulk “Review deactivation with UsageRay” workflows without automatically deactivating plugins
- Scans and attributes multiple dependency surfaces (content, Gutenberg blocks, shortcodes, legacy widgets, custom post types, reusable blocks, Site Editor templates/parts, navigation records, cron events, and custom database tables) and links to matching edit screens when available
- Performs evidence/risk reporting with explicit uncertainty and a Scan Coverage manifest distinguishing checked vs unsupported/failed/partially inspected surfaces
- Supports audit control and persistence: cancel/resume after reload for running audits; resumes automatically if a page reload occurs; temporary audit data expires after one hour
- Exports completed audit results as CSV or JSON with scan coverage/limitations and evidence counts/locations, while omitting sensitive values (e.g., post content, metadata values, option values, filesystem paths, and cron event arguments)
- Implements safety around deactivation: opening scans/preflights never changes plugin state; deactivation requires separate explicit confirmation handled by WordPress’s normal nonce-protected workflow
CONTENT BOUNDARY
UsageRay 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
UsageRay and REEID Translate FAQ.
What does UsageRay do according to the available plugin evidence?
UsageRay 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 UsageRay?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for UsageRay?
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 UsageRay in a multilingual WordPress workflow.
REEID documents UsageRay 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.