NIVOLI EDGE
Nivoli Edge translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Nivoli Edge 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
- Edge-enforced request blocking before PHP execution, including XML-RPC blocking, login/comment/search flood limits, AI-crawler blocking, and a “stray-PHP” rule that returns 404 for .php requests except real WordPress entry points.
- WordPress surface hardening at the edge to refuse user enumeration attempts (e.g., REST users list, rest_route usage, author parameter) and to block leftover/installer-related files (e.g., readme.html, license.txt, installer, debug.log).
- Admin access controls at the edge, including an IP lock for wp-admin visits and a login country lock.
- Security-headers enforcement at the edge via a “security-headers pack.”
- Install/change protection (“install lock” and “change lock”) that refuses plugin/theme install/upload/update/delete and file-editor actions at the edge until a confirmation link is mailed to the email on the Nivoli license; automatic updates and WP-CLI are stated as unaffected.
- Origin/lock enforcement mechanism (“origin lock”) where the edge stamps a secret on forwarded requests and the plugin refuses code changes that arrive without it; includes a self-test that reports whether the server enforces the origin lock.
- Managed-edge security shields (on managed plans) that add additional edge shields (e.g., AI-crawler block and wp-admin IP lock from the Growth plan) and describe monitor/off modes for certain shields (PHP and surface shields) plus an attack-surface strip over a recent window.
Distinctive features
Edge-enforced request blocking before PHP execution, including XML-RPC blocking, login/comment/search flood limits, AI-crawler blocking, and a “stray-PHP” rule that returns 404 for .php requests except real WordPress entry points. WordPress surface hardening at the edge to refuse user enumeration attempts (e.g., REST users list, rest_route usage, author parameter) and to block leftover/installer-related files (e.g., readme.html, license.txt, installer, debug.log). Admin access controls at the edge, including an IP lock for wp-admin visits and a login country lock. Security-headers enforcement at the edge via a “security-headers pack.” Install/change protection (“install lock” and “change lock”) that refuses plugin/theme install/upload/update/delete and file-editor actions at the edge until a confirmation link is mailed to the email on the Nivoli license; automatic updates and WP-CLI are stated as unaffected. Origin/lock enforcement mechanism (“origin lock”) where the edge stamps a secret on forwarded requests and the plugin refuses code changes that arrive without it; includes a self-test that reports whether the server enforces the origin lock. Managed-edge security shields (on managed plans) that add additional edge shields (e.g., AI-crawler block and wp-admin IP lock from the Growth plan) and describe monitor/off modes for certain shields (PHP and surface shields) plus an attack-surface strip over a recent window.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Nivoli Edge 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 integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Nivoli Edge and REEID Translate FAQ.
Does the current evidence establish translation scope for Nivoli Edge?
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.