Problem: The client previously used XML Configuration to manage the translation of form fields in the Divi Engine Formbuilder. Now that the developer has registered these fields, the client wishes to switch to using String Translation for ease of use and needs to know how to undo the XML Configuration. Solution: If you're experiencing this issue, we recommend removing the XML Configuration that was previously set up. This involves accessing the WPML -> Translation Management page and navigating to the Multilingual Content Setup tab. Here, you can find the Custom XML Configuration section where you can delete or modify the existing XML code. After removing or adjusting the XML, you can start using the String Translation to manage your form fields translations more comfortably.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your 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.
Problem: The client created a Solaris Board with 48 letters, each set as an individual text field and animated. However, only 14 letters were visible in the ATE (Advanced Translation Editor). Solution: We found that this behavior is expected due to WPML's translation memory, which does not allow for different translations of the same text segment, such as the letter 'E'. To demonstrate, we translated all available letters to '1', and confirmed that they displayed correctly. If you're experiencing this issue and need a different approach, we recommend using a manual translation method. For guidance on using different translation editors, please visit Using Different Translation Editors for Different Pages.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: You want to translate the Contact form built with the DIVI Engine Form builder, but the placeholder in the form is not translated correctly. The translation appears in the Advanced Custom Fields (ACE) but not on the Front Page. Solution: We recommend adding the following XML configuration to your WPML settings to ensure that the placeholders and other form fields are correctly translated:
This configuration should help WPML recognize and translate the placeholders and other text fields within your DIVI Engine forms. If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: Sie möchten auf der Startseite unterschiedliche Videos für verschiedene Sprachen anzeigen, ohne jedes Mal das Video neu in der Media Translation hochzuladen. Sie möchten stattdessen ein bereits vorhandenes Video aus der Mediathek nutzen. Solution: Wenn Sie unterschiedliche Videos für verschiedene Sprachen auf Ihrer Startseite anzeigen möchten, können Sie das Media Translation Modul von WPML verwenden. Dieses Add-On ermöglicht es Ihnen, für jede Sprache ein spezifisches Video auszuwählen, das bereits in Ihrer Mediathek vorhanden ist. Sie müssen das Video nicht jedes Mal neu hochladen, sondern können einfach das gewünschte Video für jede Sprache zuweisen. Weitere Informationen finden Sie in der Dokumentation: Media Translation Modul.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
Problem: You can't translate a string from the Advanced Icon Box element from the Element Pack Pro add-on Solution: Element Pack Pro is not compatible with WPML. We recommend replacing the Advanced Icon Box element with a standard Elementor widget that is compatible with WPML. You can find more information about the Icon Box Widget from Elementor here: https://elementor.com/help/icon-box-widget/
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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 the issue persists, please open a new support ticket with us.
Problem: The client was unable to find where to translate the string "Meer weten" in the header, even with the string translation tool. Solution: We recommended the following steps: 1. Navigate to WPML > String Translation. 2. At the bottom of the page, expand the section "Not seeing the strings you are looking for" and click on "Admin Texts Translation". 3. Search for "meer weten" and click on "Add to string translation". 4. Return to WPML > String Translation, where the string should now appear. 5. You may need to change the source language of the string. For guidance on this, visit how to change the source language of strings. 6. Translate the string and verify the changes on the front end.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 further assistance is needed, please open a new support ticket.
Problem: You are experiencing 404 errors on translated pages of your website. The error temporarily resolves after saving the permalink settings twice but reoccurs after navigating other pages. Solution: We recommend the following steps to permanently resolve the 404 error on translated pages: 1. Navigate to WPML -> Settings -> Post Types Translation. 2. Expand the option 'Set different slugs in different languages for Trainingen'. 3. Translate the slug to your desired languages, for example, DE (ausbildung) and EN (training). This should resolve the issue of 404 errors on translated pages.
If this solution does not apply to your case, or if it 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 the issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
