RECRAS

Recras compatibility with REEID Translate

Recras compatibility with REEID Translate is being evaluated from available plugin evidence. Remote data retrieval for widgets (book processes, packages, products, voucher info, and deprecated contact forms) from a configured Recras domain over HTTPS, with the plugin stating that no data is sent to Recras servers other than request parameters. No specific visitor-facing translation surface is currently confirmed.

Visit Recras ↗

AWAITING VERIFICATION

What the available evidence establishes for Recras.

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
Recras is documented in the Analytics category with 6 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 Recras 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

  • Remote data retrieval for widgets (book processes, packages, products, voucher info, and deprecated contact forms) from a configured Recras domain over HTTPS, with the plugin stating that no data is sent to Recras servers other than request parameters.
  • Frontend widget rendering via Gutenberg blocks (recommended), classic editor buttons (limited functionality), or manually entered shortcodes (discouraged).
  • Client-side caching of retrieved Recras data for up to 24 hours, with an option to clear the cache to reflect changes immediately.
  • Optional “basic Google Analytics integration” for booking of packages and voucher sales, enabled via a setting on the Recras → Settings page, and described as working only when a global `ga` JavaScript object exists.
  • Widget styling behavior: no custom styling is applied by default; available CSS classes are referenced in `css/style.css`, and the plugin does not automatically load that stylesheet.
  • Date picker behavior for (standalone) contact forms: by default uses the browser date picker, with an optional plugin-provided date picker that can be enabled in Recras → Settings; the setting is stated to not apply to contact forms used in older online booking of packages integration or in book processes.

CONTENT BOUNDARY

Recras 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

Recras and REEID Translate FAQ.

What does Recras do according to the available plugin evidence?

Recras has 6 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 Recras?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for Recras?

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 Recras in a multilingual WordPress workflow.

REEID documents Recras 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.

Shopping Cart
Scroll to Top