Lite and Pro are prepared for multilingual use. Static plugin texts continue to be translated via WordPress language files. In addition, from Lite 1.0.17 onwards, shop texts stored by the user, such as frontend texts, privacy notices and default email texts, can be provided as string translations for WPML and Polylang. PRO-specific text templates are complemented accordingly from Pro 1.0.4 onwards.
Basic principle
- Static plugin texts are translated via
.poand.mofiles. - Settings manually stored in the database are not overwritten, but registered with WPML/Polylang as translatable strings.
- The string group is called
WM Widerrufsmanagerso that the texts can be found collectively in WPML or Polylang. - If no translation is available, the plugin automatically uses the previously saved original text as a fallback.
- The registration is protected against duplicate execution during a request.
Why is this important?
Many legally and communicatively relevant texts do not come from language files, but from the shop’s plugin settings. These include introductions in the withdrawal form, privacy texts, button texts, subject lines and email content. String registration allows multilingual shops to translate these custom texts directly in WPML or Polylang.
| Area | Lite | Pro |
|---|---|---|
| Text domain | wm-widerrufsmanager | wm-widerrufsmanager-pro |
| Static plugin texts | .po/.mo | .po/.mo |
| WPML/Polylang string translation | From Lite 1.0.17 | From Pro 1.0.4 |
| Registered Lite texts | Frontend title, introduction, success message, privacy note, button text and basic emails | Uses the Lite base with |
| Registered Pro texts | Not included | PRO email templates, PRO notices and other PRO-specific text fields |
| Fallback behaviour | Original stored text | Original stored text |
Translatable shop texts
- Frontend form title, introduction, success message and button text.
- Privacy and note texts from the plugin settings.
- Basic email subject lines and email texts for customers and shop operators.
- PRO-specific email templates and text building blocks once Pro 1.0.4 is active.
Existing data
- Existing settings remain unchanged.
- No texts are replaced or reinitialised automatically after the update.
- Previously saved withdrawal requests retain their existing data.
- Newly submitted withdrawal requests can store the language or locale used so that later customer emails can take the customer’s original language into account.
Typical translation workflow with WPML or Polylang
| Step | Description |
|---|---|
| 1. Save texts | Maintain and save the desired frontend, privacy and email texts in the Widerrufsmanager. |
| 2. Register strings | Open or save the Widerrufsmanager settings in the backend so that WPML/Polylang recognises the current texts. |
| 3. Open translations | In WPML or Polylang, switch to string translation and filter by the group WM Widerrufsmanager. |
| 4. Translate | Maintain the desired target languages. Keep placeholders such as {order_number}, {customer_name} or {items_table} unchanged. |
| 5. Check output | Test the withdrawal form, success message and customer emails in the respective language. |
Note on Polylang: if several interim versions were active during tests, old duplicate strings may remain visible in the Polylang table. The current registration prevents new duplicates; existing unused strings can be cleaned up in Polylang.