Passer au contenu Passer à la barre latérale

Ce sujet contient 0 réponse, a 0 voix.

Dernière mise à jour par wolfgangW-24 Il y a 1 semaine et 5 jours.

Assisté par: Christopher Amirian.

Auteur Messages
janvier 27, 2026 à 11:42 am #17766678

wolfgangW-24

Hi WPML Support Team,

I would like to report a compatibility issue involving WPML, YITH Request a Quote (RAQ), and WPForms, which appears to be language-context dependent.

Summary of the issue
When using YITH Request a Quote with separate WPForms configured per language (German / English), the product list in RAQ email notifications ({ywraq_list}) is rendered inconsistently depending on the WordPress user profile language, rather than the frontend language of the request.

Observed behavior
RAQ email notifications contain product details only when the WordPress user profile language matches the active RAQ form language
When the profile language differs, the email is sent but the product list is missing (the {ywraq_list} placeholder is not rendered)
This behavior is consistent and reproducible.

Environment behavior

Production

WordPress user profile language: German

Product details appear in RAQ emails only for German requests

English requests are missing product details

Staging (cloned from production)

WordPress user profile language: English (US)

Product details appear in RAQ emails only for English requests

German requests are missing product details

This strongly suggests that the RAQ email rendering depends on the backend user language context rather than the frontend language or WPML language switch.

Staging site for testing

Staging URL:
lien caché

Example English product page:
lien caché

English RAQ page (working on staging):
lien caché

German RAQ page (not working on staging):
lien caché

Additional notes
The RAQ email template uses {all_fields} and {ywraq_list}

When these placeholders were previously combined in a translated string separated by an HTML , WPML String Translation failed to apply them correctly

Removing the partially mitigated the issue, but did not resolve the language-dependent behavior

YITH support is currently investigating this issue in parallel and has access to the same staging environment.

Please let me know if you need admin or SFTP access to the staging site for deeper debugging.

Kind regards,
Chris