Problem: The client developed a marketplace using Dokan Pro and enabled WPML integration for translating strings from English to Italian. Despite setting translations in the backend, they are not visible on the front-end. Solution: We reviewed several strings from the dashboard and attempted modifications to understand how Dokan loads them. However, these changes did not apply, even for the default language. We recommend contacting the Dokan plugin team to verify if these strings are translatable, as they also manage the WPML glue plugin. They should be able to suggest a workaround.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so here: WPML Support Forum.
Problem: The client reported that the WP Guppy chat plugin does not support automatic or dynamic translation of live chat messages with WPML. While UI strings from WP Guppy can be translated via WPML's String Translation, the actual chat messages typed by users remain untranslated on the frontend, despite showing '+' icons for each language. Solution: We confirmed that the WP Guppy plugin is not compatible with WPML for translating dynamic content such as live chat messages. We recommend contacting the authors of the WP Guppy plugin to inquire if the plugin is translatable and if they can provide a guide on how to translate it. This information will help determine if there is a missing component needed for integration with WPML.
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.
Проблема: Вы столкнулись с проблемой, когда при попытке перевести страницу на исландский язык, главная страница сохраняет контент предыдущего языка, даже если этот контент был удалён. Проблема возникает из-за настройки пользовательских полей ACF Flexible Content в режиме 'Copy Once', которые не удаляются полностью, а восстанавливаются при отсутствии в переводе. Решение: 1. Проверьте настройки группы полей ACF в вашем WordPress администраторе. Перейдите в Custom Fields → Field Groups и убедитесь, что группа полей установлена как 'Translate' или 'Not translatable', в зависимости от вашей стратегии контента. 2. В редакторе группы полей перейдите к вашему полю Flexible Content и для каждого подполя внутри проверьте настройки перевода в колонке WPML translation, установив 'Translate' для текстовых полей и 'Copy Once' для полей, которые должны копироваться один раз. 3. Обновите группу полей после внесения изменений. 4. Перейдите в раздел Pages или Posts и для страницы на вторичном языке нажмите кнопку Update, даже если вы не вносили изменений. Это поможет пересохранить страницу с примененными настройками перевода WPML. 5. Если проблема сохраняется, не удаляйте значение поля полностью в переводе, а замените его другим значением.
Если данное решение не помогло или кажется неактуальным, рекомендуем открыть новый тикет в службе поддержки WPML. Также рекомендуем проверить известные проблемы и убедиться, что у вас установлены последние версии тем и плагинов.
Problem: The client is unable to translate field labels or placeholders in a registration form built with the B2BKing Pro plugin, despite having scanned the plugin's domains and translated the strings in the WPML String Translations settings. Solution: If you're experiencing this issue, we recommend the following steps: 1. Navigate to WPML->Settings->Custom Post Type Translations. 2. Set the Custom Registration Role (b2bking_custom_role) as translatable. 3. Edit the roles and translate them to secondary languages.
This approach should resolve the translation issue on the front end.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where translations for elements like the footer and header are visible in the backoffice but not reflected in the frontoffice, despite trying several solutions. Solution: We have identified that the header feature may be incompatible with your current theme, which causes it to display the default language header instead of the translated one. We recommend reaching out to your theme's author to see if they can adjust the logic on their side. Alternatively, consider switching to a WPML compatible theme or using the default header builder provided by Elementor Pro. You can find a list of WPML compatible themes that we have tested and verified here.
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.
Problem: If you're using the Uncode theme with WPML and notice that SVG icons are not displaying correctly in translated versions of your pages, such as missing or incorrectly colored icons, this might be due to the way SVG files are handled in shortcodes. Solution: We recommend adding the following code to your theme's
This code checks if the shortcode being rendered is an icon widget that uses an image ID. If the image is an SVG file, it retrieves the SVG from the server and replaces the tag with the inline SVG markup, allowing the SVG to render correctly and be styled as expected. Additionally, if you encounter issues with tags being translated as plain text instead of HTML, you can fix this by allowing HTML tags in the shortcode title. Navigate to WPML → Settings → Custom XML Config and add the following configuration:
After saving, please re-save both the original content and its translations to apply the changes.
Please note that the solution provided 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: Your blog posts are not displaying in the languages FR, EN, and DE, despite being translated. Solution: This issue is related to an edge case with the Bricks theme. We suggest two possible workarounds: 1. Avoid assigning the blog page as the Posts Page in WP > Settings > Reading, especially since you are using a custom query in your template. 2. Use a different slug for the blog page in each language, such as "blog-fr" for French. We have implemented the second workaround on your site, and it resolved the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and ensuring you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
Problem: If you're experiencing issues with adding products to the cart on a multilingual WooCommerce site, where Bulgarian is the main language and English is secondary, this might be due to a compatibility issue with the Buy Once or Subscribe for WooCommerce Subscriptions plugin. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML > Settings > Custom Fields Translation and click on "Show system fields". 2. Search for "_bos4w_saved_variation_subs" and set it to Copy. Save your changes. 3. Search for "bos4w_use_variation_fixed_price_" and change all results to Copy. Save your changes. 4. Replace the code in
with the updated code from the provided link. 5. Do the same for
class-bos4w-cart-options.php
. 6. Make a minor edit to the original product experiencing the issue to apply the solution. 7. Update its translation. Additionally, you can translate the plugin strings in WPML > String Translation under the domain "bos4w". For the files with the updated code, please visit: https://we.tl/t-HmLg3HiCkZ
If this solution does not apply to your case, or if it becomes 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 at our support forum.
Problem: If you're experiencing issues with booking the same product multiple times on your website using PluginHive's plugin when WPML is activated, this might be due to a compatibility issue between WPML and the PluginHive plugin. Solution: We have identified the problem and are planning to fix it in a future release of WCML. Meanwhile, we recommend you try the following workaround: Add this code to your
This code adjusts the WPML settings to allow multiple bookings of the same product. 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 further assistance is needed, please open a new support ticket at WPML support forum.
