CRYPTX
CryptX compatibility with REEID Translate
CryptX compatibility with REEID Translate is being evaluated from available plugin evidence. Automatically detects email addresses in content and protects them using JavaScript, Unicode, image replacement, or custom text. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for CryptX.
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
CryptX is documented in the Security 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 CryptX 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
- Automatically detects email addresses in content and protects them using JavaScript, Unicode, image replacement, or custom text.
- Works across posts, pages, comments, widgets, and text widgets.
- Can leave selected addresses or whole domains unchanged via an exceptions list.
- Can disable protection for specific posts or pages.
- Supports RSS feed control, including leaving feeds unprotected.
- Provides a Gutenberg editor block for protected email addresses with link text, subject, cc, and bcc fields.
- Includes WP-CLI commands for settings management and scanning published posts for readable addresses.
- Supports multisite with per-site settings and network defaults for new sites.
Distinctive features
Email-address protection with multiple display methods, exceptions for addresses or domains, a Gutenberg block for protected email links, WP-CLI support, and multisite settings controls.
CONTENT BOUNDARY
CryptX 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
- Protection behavior is described for posts, pages, comments, widgets, and text widgets. RSS feed handling is configurable, including an option to leave feeds unprotected. The available evidence does not establish broader content coverage beyond these surfaces.
COMMON QUESTIONS
CryptX and REEID Translate FAQ.
What does CryptX do according to the available plugin evidence?
CryptX 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 CryptX?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for CryptX?
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 CryptX in a multilingual WordPress workflow.
REEID documents CryptX 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.