Problem: You created an English review request page with a Strong Testimonial form and used String Translation to translate the form text to Dutch. However, not all translations are shown on the Dutch page. Solution: If you're experiencing this issue where the registered string appears in the wrong language, we recommend checking how to change the source language of strings here: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-change-the-source-language-of-strings/ Additionally, ensure that you have followed the guidelines for translating testimonial fields in multiple languages with WPML, which can be found here: https://strongtestimonials.com/docs/how-to-translate-testimonial-fields-in-multiple-languages-with-wpml/ If this solution does not apply because it is outdated or not relevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing difficulty with users switching languages via the language switcher in the navigation menu. They want to display both Dutch and English flags next to each other in the main menu. Solution: We recommend customizing the Language Switcher to display both language flags next to each other in the main menu. You can find this option under WPML > Languages > Menu Language Switcher. For detailed guidance, please refer to our documentation: Language Switcher Options.
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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: You are trying to translate a toggle made with Divi using WPML, but the translation process stops at 94% despite all translations appearing to be completed. Additionally, you are experiencing issues with the WPML String Translation plugin not showing available updates on your dashboard. Solution: 1. To address the translation issue: - Open the Translation Editor. - Go to the top right corner of the Translation Editor. - Click the gear icon and enable the option "Use the previous version of the Advanced Translation Editor." - Check for any segments that are in progress, complete the translation, and save them.
2. Regarding the WPML String Translation plugin update: - Visit the "Plugins > Add New > Commercial" tab to check if you can download or update the String Translation plugin directly from there. - Alternatively, log in to your WPML.org account, download the latest version of String Translation, and try reinstalling it on the site.
If these steps do not resolve your issues or if the solution 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: The client was experiencing an issue where the navigation links in the Divi Builder blog layout were not translating correctly. Despite translating the Dutch words for 'next' and 'previous' into English using String Translation and translating the module, the English blogs still displayed the Dutch words 'Vorige' and 'Volgende'. Solution: The navigation link texts were coming from a custom body template created for posts in Divi > Theme Builder. The template can be translated by going to WPML > Translation Management and using the search filter to find the 'Body Template' post type then translating the correct template. After translating the template, the issue was resolved.
Problem: The client was experiencing an issue where the footer translated via String Translation was showing up in English but remained in Dutch on the German and Spanish pages of their Divi-built website.
Solution: We recommended that the client should have initially tried translating the footer template through Translation Management. Upon further investigation, we discovered that the issue was due to an untranslated template. We translated the necessary template. If you're experiencing a similar issue, ensure that all templates are fully translated and consider using Translation Management for such tasks.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client was unable to access the English translation of a blog page, which was previously available. The menu item linking to the page was missing, and the page was not listed in the page overview. Solution: We found that the translation was created as a draft and had been moved to the trash. We restored the page and then published it. If you encounter a similar issue, please make sure that the translation is not created as a draft or added to trash. If this solution doesn't look relevant, please open a new support ticket.
Problem:
I am looking for a free affiliate plugin which is compatible with WPML. After struggling for weeks with WP Affiliate Manager they finally realised the plugin did cause problems because I have a multilingual website.
I have tried to look for another free affiliate plugin but sofar none of the ones I found will work with WPML.
Do you know of any free affiliate plugins that will work with WPML? I am asking for a free plugin because my product only costs € 47,50 and I will not send many.
Solution:
In our compatible list of affiliate plugins, we have only three options - but they are all paid, I'm afraid:
Comparing their pricing, Gutencon seems to be the cheapest alternative.
You still can use the free options, and check if they will produce issues when using them together with WPML. Not being in our compatible list (wpml.org/plugin/) does not mean that the plugin is incompatible, just that it wasn't fully tested by our compatibility team, and therefore, we might encounter issues (might, not necessary will find).
