WAIVER ENGINE
Waiver Engine compatibility with REEID Translate
Waiver Engine compatibility with REEID Translate is being evaluated from available plugin evidence. Nonce-based CSRF protection for waiver form submissions (invalid nonce rejected with HTTP 403). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Waiver Engine.
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
Waiver Engine 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 Waiver Engine 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
- Nonce-based CSRF protection for waiver form submissions (invalid nonce rejected with HTTP 403).
- Honeypot field anti-bot check (hidden off-screen field must exist and remain empty; bots that auto-fill are rejected).
- Timing-check anti-replay/fast-bot protection using an HMAC-signed timestamp (submissions <3 seconds or >2 hours rejected with HTTP 429).
- IP-based sliding-window rate limiting using WordPress transients (default 5 submissions per 15 minutes; configurable and can be disabled).
- Optional CAPTCHA support for form submissions (Google reCAPTCHA v3 or hCaptcha; token verified server-side via wp_remote_post to provider verify endpoints).
- Admin-side management of waiver submissions with an entry list (pagination, filtering, sorting) and PDF download actions; generated PDFs stored under wp-content/uploads/pewave-pdfs/.
- Security-related maintenance tool: PDF File Cleanup deletes generated PDFs older than a configured number of days from disk while preserving database entry records.
CONTENT BOUNDARY
Waiver Engine 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
Waiver Engine and REEID Translate FAQ.
What does Waiver Engine do according to the available plugin evidence?
Waiver Engine 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 Waiver Engine?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Waiver Engine?
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 Waiver Engine in a multilingual WordPress workflow.
REEID documents Waiver Engine 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.