DISABLE REST API
Disable REST API translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Disable REST API does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Disables access to the WordPress core REST API for general site visitors.
- Can whitelist individual REST API endpoints or entire endpoint branches.
- Supports per-user-role access rules for REST API endpoints.
- Returns an authentication error when access to an endpoint is not allowed on most WordPress versions.
- Uses the `rest_enabled` filter to disable the entire REST API on WordPress 4.4, 4.5, and 4.6.
- Does not affect REST APIs implemented by plugins or themes outside the WordPress core REST API.
Distinctive features
Security-focused REST API restriction for WordPress core, with endpoint-level and branch-level whitelisting plus per-role access rules. It also includes version-specific handling for WordPress 4.4, 4.5, and 4.6.
Dynamic content
Dynamic REST API access behavior is established for the WordPress core REST API, including endpoint whitelisting, branch whitelisting, and per-role access rules. The evidence does not establish dynamic behavior for plugin- or theme-provided REST APIs.
SEO and metadata
No SEO or metadata behavior is established in the supplied evidence.
URLs and navigation
The supplied evidence does not establish URL navigation behavior. It only indicates REST API endpoint access can be allowed or blocked.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Disable REST API does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This plugin affects the WordPress core REST API for general site visitors, but it does not affect REST APIs implemented by plugins or themes outside the WordPress core REST API. Access can be restricted at the endpoint or endpoint-branch level, and access rules can vary by user role. On WordPress 4.4, 4.5, and 4.6, the entire core REST API can be disabled through the `rest_enabled` filter. When access is not allowed on most WordPress versions, an authentication error is returned.
COMMON QUESTIONS
Disable REST API and REEID Translate FAQ.
Does the current evidence establish translation scope for Disable REST API?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.