Problem: You are using WPML with Divi and the Diviflash plugin, specifically the FAQ Module (difl_faq / difl_faqitem), and you want the FAQ titles to be recognized by the WPML Translation Editor. Although the FAQ answers are detected, the FAQ titles are not showing up for translation. Solution: First, ensure that the DiviFlash plugin author is aware that for compatibility with WPML, they should follow the documentation on registering page builder content for translation, which can be found here: https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/. Next, update your custom XML configuration in WPML > Settings > Custom XML Configuration with the following code:
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, it may be due to the plugin author's responsibility to ensure compatibility with WPML. In such cases, 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 the problem persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing an issue where the phone number in the DIVI Global Header was displaying in German across all languages, despite previous correct settings. The section to edit this header was also not visible. Solution: We advised the client to check under DIVI Layouts where multiple Global Sections (Menü 1, Menü 2, and Menü 3) might be overwriting the header settings. By opening these sections and searching for the phone number, the client was able to locate and correct the numbers. Additionally, to allow translating numerical values such as phone numbers, we provided a code snippet to be added to the theme's functions.php file:
After adding this code, the client should resave the primary language page so the Advanced Translation Editor can rescan and show the numbers for translation.
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 issues persist, please open a new support ticket.
Problem: The client is unable to display a linked post in other languages on their website using Divi layouts and the DiviFlash plugin. The expected translated posts are not showing. Solution: 1. Ensure that the Divi layout used to create the page is translated: - Navigate to WPML > Translation Management. - Locate the Divi layout in question. - Select it and send it for translation at the bottom of the page. - Proceed to WPML > Translations and complete the translation. 2. If the translated post still does not display, check the compatibility of the DiviFlash plugin with WPML. The Posts List widget used by DiviFlash is currently not compatible with WPML. We recommend contacting the DiviFlash developers to encourage them to make their plugin compatible with WPML. They can apply for assistance through our Go Global program.
If these steps do not resolve your issue, or if the information provided here is 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate user notifications for Gravity Forms using WPML, but despite following the guide and translating all forms and strings, the notifications are still sent in German when the enquiry is made from the English version of the site. Solution: We conducted a test by setting up a local copy of the client's site with only essential plugins activated (WPML CMS, String Translation, Gravity Forms, and Gravity Forms Multilingual) and using the default WordPress theme. We created a test page and did not encounter the issue in this minimal setup. We suggest the client to: 1) Deactivate all non-essential plugins. 2) Switch to the default WordPress theme temporarily. 3) Clear the browser's cache or try accessing the site using a private browsing window to see if the issue persists.
If these steps do not resolve the issue, 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 the problem continues, please open a new support ticket.
Problem: The client is planning to switch their multilingual website from using different languages in directories to using different domains per language and is concerned about potential issues during this transition. Solution: If you're planning to switch to different domains for each language, here are the steps we recommend: 1. Ensure that all domains for each language are properly configured to point to the same WordPress installation by setting up the DNS records accordingly. 2. Make sure your server is configured to handle requests from these domains. This might involve setting up virtual hosts or adjusting server settings. 3. Update the WPML settings to reflect the new domain structure. You can do this by specifying that you're using different domains for each language in the WPML settings. For detailed guidance, visit How to use WPML with different domains per language. 4. If your site uses HTTPS, ensure you have valid SSL certificates for each domain. This may require obtaining separate certificates or a multi-domain (SAN) certificate.
While switching the option should be straightforward, adjustments might be needed. If this solution seems 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Der Kunde möchte eine Sprache auf seiner mehrsprachigen Website nicht indexieren lassen. Solution: Wir empfehlen, die robots.txt-Datei zu verwenden, um die Indexierung einer bestimmten Sprache zu verhindern. Ein Beispiel, wie dies umgesetzt werden kann, finden Sie in unserem Forum: https://wpml.org/forums/topic/noindexing-of-english-sites/#post-12567063.
Bitte beachten Sie, dass diese Lösung möglicherweise nicht mehr aktuell oder auf Ihren Fall nicht anwendbar ist. Wir empfehlen Ihnen, 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 von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen: WPML-Support-Forum.
