NIVOLI EDGE
Nivoli Edge compatibility with REEID Translate
Nivoli Edge compatibility with REEID Translate is being evaluated from available plugin evidence. 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. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Nivoli Edge.
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
Nivoli Edge is documented in the Security 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 Nivoli Edge 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
- 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.
CONTENT BOUNDARY
Nivoli Edge 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
Nivoli Edge and REEID Translate FAQ.
What does Nivoli Edge do according to the available plugin evidence?
Nivoli Edge 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 Nivoli Edge?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Nivoli Edge?
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 Nivoli Edge in a multilingual WordPress workflow.
REEID documents Nivoli Edge 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.