
BOOKING WIDGET FOR SOFTULA
Booking Widget for Softula compatibility with REEID Translate
Booking Widget for Softula compatibility with REEID Translate is being reviewed using official plugin documentation. Embeds the Softula booking widget into WordPress pages/posts via the `[softula]` shortcode or a native “Booking Widget for Softula” block. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Booking Widget for Softula does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Booking Widget for Softula is documented in the Media category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Booking Widget for Softula compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Embeds the Softula booking widget into WordPress pages/posts via the `[softula]` shortcode or a native “Booking Widget for Softula” block.
- Conditionally loads `widget.js` only on pages where the shortcode or block is used.
- Connects to a Softula widget-delivery service to load and render the booking widget; the default JavaScript source is `https://planner-api.softula.com` (with support for an API base override).
- Supports shortcode attributes including `token` (required), `widget` (required, e.g., “planner”), and optional `api_base` to override the API base URL.
- Provides a Settings page (“Settings → Booking Widget for Softula”) to configure a custom API base (staging/self-hosted), and also supports `SOFTULA_API_BASE` in `wp-config.php`.
- Widget rendering is handled by the visitor’s browser after `widget.js` is loaded; the plugin itself does not send personal visitor data, and booking form submissions are handled directly between the browser and Softula’s API.
- Allows multiple widgets on one site by using separate shortcode instances or separate block instances, each with its own token.
TRANSLATION BOUNDARY
Booking Widget for Softula capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Booking Widget for Softula and REEID Translate FAQ.
What does Booking Widget for Softula do?
Booking Widget for Softula has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Booking Widget for Softula have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Booking Widget for Softula?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Booking Widget for Softula in a multilingual WordPress workflow.
REEID documents Booking Widget for Softula functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.