DISABLE XML-RPC
Disable XML-RPC compatibility with REEID Translate
Disable XML-RPC compatibility with REEID Translate is being evaluated using available plugin evidence. Disables the WordPress XML-RPC API on sites running WordPress 3.5 or above. No specific visitor-facing text is currently confirmed for translation.
AWAITING VERIFICATION
What the available evidence establishes for Disable XML-RPC.
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
Disable XML-RPC is documented in the Security category with 5 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 Disable XML-RPC 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
Do not treat structure, configuration, logic, integrations or runtime behaviour as translatable content unless specific human-readable text is identified.
04 · Confirm what can be translated
Publish supported content only when specific visitor-facing text has been identified and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Disables the WordPress XML-RPC API on sites running WordPress 3.5 or above.
- Uses the built-in WordPress filter "xmlrpc_enabled" to turn XML-RPC off.
- Has no admin interface; activation turns XML-RPC off and deactivation turns it on.
- Can be re-enabled simply by deactivating the plugin.
- May be affected by another plugin, theme function, or server configuration that blocks access to xmlrpc.php.
Distinctive features
Simple XML-RPC disablement for WordPress sites, with activation-based control and no settings screen.
CONTENT BOUNDARY
Disable XML-RPC capabilities and translatable content are documented separately.
The available evidence documents plugin functionality, but does not currently identify specific visitor-facing text that can be translated.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This plugin affects the WordPress XML-RPC API on sites running WordPress 3.5 or above. It has no admin interface, so there are no plugin settings to adjust from the dashboard. If another plugin, a theme function, or server configuration blocks access to xmlrpc.php, that can affect how it behaves. Deactivating the plugin re-enables XML-RPC.
COMMON QUESTIONS
Disable XML-RPC and REEID Translate FAQ.
What does Disable XML-RPC do according to the available plugin evidence?
Disable XML-RPC has 5 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Does Disable XML-RPC currently have any visitor-facing content confirmed for translation?
No specific visitor-facing text is currently confirmed for translation in this integration.
What evidence is needed to confirm translatable content for Disable XML-RPC?
The evidence must identify specific visitor-facing text, such as labels, titles, descriptions or messages, that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Disable XML-RPC in a multilingual WordPress workflow.
REEID documents Disable XML-RPC functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Supported translatable content will be published when specific visitor-facing text is confirmed by evidence.