Problem: If you're experiencing issues where orders placed through the German page of your WooCommerce site are not being processed automatically, even though they were previously fixed, this summary might help. Solution: 1. First, check the course product in the default language (English in this case) to ensure the associated LeanDash Course is correctly set. 2. Use the admin Language Switcher to switch and edit the product in the problematic language (German). It's crucial to edit the product using the WordPress editor, not the WPML editor. 3. Verify if the field for the LeanDash Course is empty. If it is, you need to add the correct course in the field for the German version and update the product.
This approach should resolve the issue with orders not being processed automatically on the German page. If the problem persists or the solution seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If these steps do not resolve the issue, please open a new support ticket.
Problem: The client was unable to translate certain elements of a form built with DIVI Engine, including buttons, placeholders, and required messages, despite previously adding a custom XML configuration.
Solution: We advised the client to modify the existing XML configuration by adding specific attributes to handle the translation of default texts such as 'Submit', 'Next', and 'Prev'. This involves changing these default texts to something else in the original language to make them translatable. Here is the updated XML configuration snippet:
<wpml-config>
<shortcodes>
<!-- alle Formfelder (Text, Textarea, Select, Checkbox etc.) -->
<shortcode>
<tag>de_fb_form_field</tag>
<attributes>
<!-- Beschriftung & Placeholder -->
<attribute>field_title</attribute>
<attribute>field_placeholder</attribute>
<!-- Beschreibung/Infotext unter dem Feld -->
<attribute>description_text_text</attribute>
<!-- Dropdown‑Platzhaltertext -->
<attribute>select_placeholder_text</attribute>
<!-- Inhalt von Content‑Feldern (Text oder HTML) -->
<attribute encoding="allow_html_tags">html_content_editor</attribute>
<!-- Optionslisten als JSON -->
<attribute encoding="json">select_options</attribute>
<attribute encoding="json">checkbox_options</attribute>
<!-- Optional: Radiobutton‑Optionen, falls im Einsatz -->
<attribute encoding="json">radio_options</attribute>
<!-- Optional: eigener Hinweis bei Pflichtfeldern -->
<attribute>required_message</attribute>
<attribute>forgot_password_text</attribute>
<!-- Change the default text in the original language to make it work, e.g. Please enter a valid email address -->
<attribute>email_message</attribute>
<!-- Multi‑Step: Weiter/Zurück‑Buttons -->
<!-- Change the default text in the original language to make it work, e.g. Back / Forward -->
<attribute>step_prev_text</attribute>
<attribute>step_next_text</attribute>
</attributes>
</shortcode>
<!-- gesamtes Formular: Submit‑Button, generische Placeholder etc. -->
<shortcode>
<tag>de_fb_form</tag>
<attributes>
<attribute>title</attribute>
<!-- Change the default text in the original language to make it work, e.g. Send -->
<attribute>submit_button_text</attribute>
<attribute>field_placeholder</attribute>
<attribute>redirect_url_after_submission</attribute>
<attribute>ajax_submit_button_text</attribute>
<attribute>field_placeholder</attribute>
<!-- Optional: Erfolgs‑ und Fehlermeldungen (not tested) -->
<attribute>success_message</attribute>
<attribute>error_message</attribute>
<attribute>processing_text</attribute>
</attributes>
</shortcode>
</shortcodes>
</wpml-config>
Additionally, we suggested contacting the plugin author to ensure their code adheres to standard WordPress methods for making text translatable, as detailed in our documentation: https://wpml.org/documentation/support/how-to-use-gettext/
If this solution does not resolve the issue or seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problème: Le client souhaite traduire le pied de page créé avec Elementor dans sa bibliothèque de thème OceanWP, mais rencontre des difficultés pour traduire les éléments HTML et les formulaires MailerLite intégrés. De plus, il y a des problèmes avec l'affichage des produits non traduits et la suppression de la bannière de développement. Solution: 1. Pour traduire le pied de page, utilisez la fonctionnalité de traduction de chaînes d'Elementor. Consultez la documentation pour la traduction avec OceanWP et WPML ici : https://docs.oceanwp.org/article/438-how-turning-oceanwp-multilingual-with-wpml. 2. Pour les éléments HTML et les formulaires MailerLite, modifiez directement le code HTML dans la traduction pour utiliser les ID spécifiques à chaque langue. 3. Pour afficher les produits non traduits dans la langue par défaut, allez dans WPML > Paramètres > Traduction des types de publication et sélectionnez l'option « Traduire - utiliser la traduction si disponible ou revenir à la langue par défaut ». 4. Pour supprimer la bannière de développement, supprimez toutes les clés précédentes liées à ce site dans votre compte WPML, désenregistrez WPML du site, puis enregistrez le site avec une nouvelle clé de production.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et d'ouvrir un nouveau ticket de support si nécessaire. Pour plus d'assistance, visitez notre forum de support.
