Problem: The client needs to translate a form created with Metform into Greek, but Metform is not compatible with the WPML Translation Editor. Solution: 1) Set the 'Forms (metform-form)' to 'Translatable, only show translated items' in WPML > Settings > Post Type Translation. 2) Translate the forms directly in Metform > Forms. Each translated form will have a unique shortcode. Manually place the correct shortcode on each page for each language. 3) Use the WordPress Editor as a translation method and create each form in Elementor. Follow this guide: Using different translation editors for different pages. 4) After creating a Greek form, scan MetForm for new strings at WPML > Theme & Plugin Localization and revise WPML > String Translation for strings from MetForms. 5) If these steps do not resolve the issue, consider using a compatible form plugin such as Contact Form 7 or WP Forms, listed here: WPML compatible form plugins.
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: The client has translated Term Meta to Portuguese via WPML's Translation Dashboard under Yoast SEO > Term Meta, but the Term Meta of their taxonomies still appears in English in the backend, although it is correctly translated on the frontend. Solution: 1. We have identified that Yoast SEO term metas are not stored using the standard WordPress API but as a serialized option, which can lead to issues if the data becomes too large. 2. To manage translations, we recommend using the WPML Translation Dashboard to translate Yoast SEO term meta, ensuring it displays correctly on the frontend. 3. If editing is necessary, it should be done via the Advanced Translation Editor (ATE), and the term meta should be re-sent for manual translation if it was initially auto-translated. This will not incur additional credits as the translations are saved in ATE's translation memory. 4. We are considering implementing a feature where the Yoast SEO term meta field in the backend will be locked with a recommendation to use ATE for translations, to prevent issues with direct edits.
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: Using Shoplentor and Fox currency switcher with fixed prices in Euro and GBP. When the country is set to France, prices are correct in Euros. However, switching to the French version of the shop results in prices being marked up again, treating Euro prices as if they were GBP and converting them to Euro again, resulting in prices that are 15% too high. WPML multicurrency is set to off. Solution: If you're experiencing this issue, we recommend you try the following steps: 1) Go to WPML->Settings->Custom Fields Translations 2) Click on Show system fields 3) Set the following fields as copy: -
_woocs_price_geo_countries
-
_woocs_regular_price_geo
-
_woocs_sale_price_geo
-
_woocs_regular_price_EUR
-
_woocs_sale_price_EUR
- Update the product in the original language.
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 at WPML support forum.
Problem: If you're experiencing issues with translating custom fields using the Advanced Translation Editor (ATE) or String Translation in WPML, it's important to note that these fields might not be supported for automatic translation. Solution: We recommend translating these products manually. You should also manually set the custom fields as they are not automatically translatable through ATE or String Translation. For more detailed guidance, please refer to our documentation on using different translation editors for different pages and Advanced Product Fields for WooCommerce.
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 at our support forum.
Problem: The client is experiencing an issue where the heading is translated through automatic translation in the backend, but on the frontend, it only displays in French using the Divi Builder, while other contents are showing properly. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Make a small change to the original content. 2. Update the page. 3. Open the translation and complete it. If the issue still persists, please provide more details and attach screenshots showing the problem so we can better assist you.
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 you still need assistance, please open a new support ticket at WPML support forum.
Проблема: Divi Builder отображается на английском языке, хотя должен быть на русском. При деактивации WPML, Divi отображается на русском. Решение: Если вы столкнулись с аналогичной проблемой, мы рекомендуем перейти в папку
wp-content/languages/wpml
и удалить весь контент в ней. Необходимые файлы будут автоматически пересозданы, что должно решить проблему. Также, если у вас возникли проблемы с миграцией на Divi 5 при включенном WPML, рекомендуем ознакомиться с известной проблемой и возможным решением здесь: Divi 5: Migrating from Divi 4 May Fail.
Обратите внимание, что данное решение может быть неактуальным или не подходить для вашего случая. Мы настоятельно рекомендуем проверить список известных проблем, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.
Problem: The client reported that the list of documents on the French page of their website was not displaying, while it worked correctly on the English page. The issue was suspected to be related to WPML interfering with the display of titles on the French page. Solution: We resolved the issue by adjusting the slug translations in WPML. Here are the steps we recommend you follow if you're experiencing a similar problem: - Go to WPML->String Translations - Select
admin_texts_document-library-pro_settings
from domains - For slug strings, either delete the string or ensure the translations are exactly the same as the original.
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 issues persist, please open a new support ticket.
