
INSTANT BACK/FORWARD
Instant Back/Forward compatibility with REEID Translate
Instant Back/Forward compatibility with REEID Translate is being evaluated from available plugin evidence. Enables instant back/forward navigation via the browser’s bfcache. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Instant Back/Forward.
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
Instant Back/Forward is documented in the Performance 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 Instant Back/Forward 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
- Enables instant back/forward navigation via the browser’s bfcache.
- Removes the `no-store` directive from WordPress `Cache-Control` responses when WordPress would otherwise send nocache headers.
- Targets logged-in WordPress sessions, and the plugin’s activation flow expects logging out and logging back in with “Remember Me” checked to observe the effect.
- Adds a session-token-based safeguard so cached authenticated pages are cleared and reloaded if the user’s login state changes.
- Preserves `private` and adds `no-cache`, `max-age=0`, and `must-revalidate` while removing `public` when adjusting cache headers.
- Includes compatibility handling for frontend login flows, including the interim login modal and two-factor/interstitial login screens.
- Can improve back/forward navigation even when full bfcache restoration is blocked, by allowing pages to be served from the browser’s HTTP cache.
CONTENT BOUNDARY
Instant Back/Forward 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
Instant Back/Forward and REEID Translate FAQ.
What does Instant Back/Forward do according to the available plugin evidence?
Instant Back/Forward 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 Instant Back/Forward?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Instant Back/Forward?
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 Instant Back/Forward in a multilingual WordPress workflow.
REEID documents Instant Back/Forward 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.