Problem: The client was unable to remove a specific translation from their website. Despite deleting the string translation, it still appeared on the site. Additionally, WPML seemed to be injecting or overriding text in the FunnelKit plugin, specifically the text 'Besteed nog X voor kabel organizer tas (t.w.v. 14.99)', which did not match the configured text in FunnelKit. Solution: We suggested updating WPML to the latest version and deleting some strings that might be causing the issue, but this did not resolve the problem. We then set up a fresh WordPress installation for the client to replicate the issue. The client was instructed to install the FunnelKit plugin on this clean setup and check if the problem persisted. If the issue was reproducible, we planned to escalate it to our compatibility team. Eventually, the client discovered that the issue was within the FunnelKit plugin itself, specifically in a language tab that might only appear when WPML is active. The problem was resolved after identifying this.
Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues, we 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 the problem persists, please open a new support ticket.
Проблема: Клиент столкнулся с проблемой, что переводы раздела Features & Amenities в теме WPResidence не отображаются на русском и сербском языках, несмотря на то, что через WPML Taxonomy все переведено. Появился алерт о том, что некоторые термины таксономии не синхронизированы между языками. Решение: Мы рекомендуем убедиться, что слаги терминов таксономии Features & Amenities совпадают в оригинале и в переводе. Вот шаги, которые мы предлагаем выполнить: 1. Перейти в раздел Features & Amenities. 2. Создать термин на английском языке с определенным слагом. 3. Перевести термин на другие языки, используя тот же слаг. 4. Открыть страницу добавления свойства, переключиться на английский язык в админ-панели, выбрать созданный термин и сохранить. После выполнения этих шагов переводы должны корректно отображаться на всех языках.
Если данное решение не помогло или кажется неактуальным, рекомендуем открыть новый тикет поддержки на форуме поддержки WPML. Также рекомендуем проверить известные проблемы, версию постоянного исправления и убедиться, что у вас установлены последние версии тем и плагинов.
Problem: The client is unable to locate the Divi Flash FAQ module in WPML's String Translation. Additionally, extra identifiers are appearing on the French page after switching to Classic Translation mode, and the English translation in WPML differs from the original content. Solution: For the Divi Flash FAQ module not being recognized by WPML, we recommend updating your custom XML configuration. Please ensure to have a backup and follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Update with the following code:
3. After saving this configuration, edit the FAQ Item on the original page, save the page, and open the translation editor. You should now see the strings of the module inside the translation editor.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.
Problem: The client reported an issue where the confirmation modal for the 'Redirect visitors based on browser language only if translations exist' setting in WPML does not close or save after clicking 'Got it, activate anyway'. This problem persists across different browsers and in incognito mode, with no visible JavaScript errors. Solution: We replicated the client's site locally and discovered that the issue was related to specific plugins from Hostinger, which are only intended for use on Hostinger servers. We recommend the following steps: 1. Temporarily disable the Hostinger plugins. 2. Try enabling the WPML setting again. 3. Re-enable the Hostinger plugins. If the problem continues, consider setting up a staging site on your Hostinger server and provide us with access to further investigate.
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 at WPML support forum.
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.
Problem: You want to translate H5P activities on your WordPress site using the WPML plugin, but you cannot find how to do this because the H5P plugin is not compatible with WPML. Solution: Although the H5P plugin is not directly compatible with WPML, if your H5P activities are registered as a custom post type or custom taxonomy, you might still be able to translate them. Here’s how you can adjust the WPML settings: 1. For Custom Post Types: Go to: WPML → Settings → Post Types Translation and set the relevant post type to Translatable. 2. For Custom Taxonomies: Go to: WPML → Settings → Taxonomies Translation and set the taxonomy to Translatable. Please note that even with these settings, full compatibility is not guaranteed due to the lack of official integration from the plugin author.
If this solution does not resolve your issue or seems outdated, we 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 you still need assistance, please open a new support ticket at WPML support forum.
