Problem: You are using WPML to translate content and encounter an issue where the translation process shows 95% completion, but it indicates something is missing when you try to save. This inconsistency occurs across various pages and templates, sometimes allowing saving at 95% completion. Solution: The issue was caused by Elementor and fixed by updating Elementor and Elementor Pro.
If these steps do not resolve the issue, or if the solution provided here becomes outdated or irrelevant to your specific case, please visit our support forum to open a new support ticket. We also 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.
Problem: You are using WPML with WooCommerce Multilingual to increase the price of multiple WooCommerce products by a percentage using the bulk actions feature. However, only the base currency (pounds) is updated, and the secondary currency (euros) remains unchanged. Solution: We have analyzed your issue and currently, we are gathering more data to determine if other clients are experiencing the same problem. As of now, we have not decided to create a feature to address this issue, and the solution has been postponed for future releases. We do not have a specific deadline for this as it depends on various factors.
If this solution becomes irrelevant due to updates or if it does not apply to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML support forum.
Problem: You are using WPML to manage translations on your site and are facing issues with pages reverting to English after manual translation. Additionally, you are having difficulty translating certain WooCommerce text strings, such as 'add to cart'. Solution: We have taken note of your issue and are currently analyzing it internally. We are also waiting to see if other clients are experiencing similar problems. As of now, we do not have sufficient data to decide on creating a feature to address this. Therefore, we have postponed the solution to future releases and do not have a set deadline for it, as it depends on various factors.
If this solution becomes irrelevant due to it being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
The client installed WordPress in German (Sie) and then WPML, which switched to German (Du). In the meta tags, 'german-formal' appears, which the client believes is not good for SEO. They need to tag the website as being in German while using formal German with WPML.
Solution:
We recommend adding a function to the theme's child functions.php file to modify the HTML language attribute for German. Here is the code you should use:
add_filter('language_attributes', 'modify_language_attributes_for_german');
function modify_language_attributes_for_german($lang) {
// Check if the current language is German
$my_current_lang = apply_filters( 'wpml_current_language', NULL );
if ($my_current_lang === 'de') {
// Replace the language code for German
return 'lang="de-DE"';
}
return $lang; // Keep default language attributes for other languages
}
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to implement automatic translation on your WordPress site using the Oxygen builder and are considering using the Deepl API with WPML.
Solution: Currently, the Oxygen page builder is not compatible with WPML, which means you cannot automatically translate your site using this setup. You will need to translate content manually. We recommend contacting the Oxygen builder's author to request a compatibility update. For developers looking to make their themes/plugins compatible with WPML, we provide detailed guidance and support. You can find more information on achieving WPML compatibility for themes and plugins at https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/. Additionally, theme and plugin authors can join WPML’s Go Global program to ensure their products are multilingual ready. More details are available at https://wpml.org/documentation/support/go-global-program/.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client added the Language Switcher to their website's header menu using WPML, supporting Hindi and English. However, the Language Switcher is not functioning correctly. Solution: We have debugged this issue during a chat session with the client. If you're experiencing a similar problem with the Language Switcher on your website's header menu, we recommend checking the configuration settings in WPML. Ensure that the Language Switcher is correctly set up to display both languages. If the issue persists, it might be due to a specific theme or plugin conflict, so testing with a default theme or deactivating other plugins could help identify the cause.
Please note that this solution might be 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 continues, please open a new support ticket at WPML support forum for further assistance.
**Problem:**
The client encounters an issue when attempting to update WPML or other plugins, receiving an error message: *"Update failed: Could not remove old translations."*
**Solution:**
If you are facing the same issue, we recommend creating a full backup of your site. Then, try updating the WPML plugin manually by following the instructions available here: https://wpml.org/faq/updating-wpml-manually/. If the problem persists, consider replacing the site key in the WP > Plugins > Add New > Commercial tab.
If these steps do not resolve the issue, it is possible that the solution may be outdated or unsuitable for your case. We encourage you to check the https://wpml.org/known-issues/, verify the fixed version, and confirm that you have installed the latest versions of themes and plugins.
Problem: After updating the URLs of pages, some pages stopped working both in the frontend and backend when using Elementor, except in Elementor safe mode. The language switcher was redirecting to non-existent pages due to these URL changes. Solution: We identified that the issue was due to the URL structure set for the categories, which conflicted with the page URLs. Specifically, both a page and a post category shared the same URL without the '/category/' part in the category URL, causing conflicts. To resolve this, we recommend checking and updating the permalink settings to ensure that pages and categories have distinct URLs. This might involve adding '/category/' to the category permalinks or adjusting the page URLs to avoid overlap.
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 here.
Problem: If you're experiencing issues where your translated URLs are displaying with page IDs instead of the expected slugs, it might be due to the pages not being published. In WordPress, unpublished or draft pages default to using page IDs in their URLs. Solution: We recommend checking the status of the pages in question. Please navigate to your pages section and ensure that these pages are indeed published. This action should resolve the issue of URLs displaying with page IDs.
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 facing an issue where, after a recent update, most of the Arabic translations in their WooCommerce store are not showing, despite being previously translated. They are concerned about the persistence of translations after updates and how to recover missing translations. Solution: 1. Navigate to WPML > String translation to ensure all strings are translated. 2. Open the theme's functions.php file and locate line 53. 3. Replace the existing code:
unload_textdomain('elessi-theme');
with:
unload_textdomain('elessi-theme', true);
This change should resolve the issue with missing translations. If some strings are still not reflected, it's recommended to check if they are translated in WPML. For ongoing issues, consider contacting us directly via chat for quicker resolution. Note: The current fix is a workaround due to a bug in the new WordPress version. You might need to reapply this fix after future theme updates until a permanent solution is implemented by the theme author. Stay updated on this issue by following the related errata: WPML Errata.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: You have translated a CSS attribute, i.e. "Placeholder" in Bricks Builder to English, and while it appears correctly in the advanced translation editor, it does not display the translated value on the frontend; instead, it shows the default language version.
Solution: We have identified an issue within the Bricks Builder code and have communicated this to the Bricks team. They are expected to resolve it in a future update, although there is no estimated time of arrival for this fix. Meanwhile, you can manually correct the translation by following these steps: 1. Open the page in the default language for editing. 2. Switch to the other language from the top admin bar. 3. If prompted, click "Edit anyway". 4. Correct the strings as needed. 5. Save. Additionally, we have published an errata which you can check and subscribe to for updates: Bricks theme translations for custom attributes are not reflected on the frontend.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML support forum.
The client attempted to install the WPML Multilingual CMS plugin using Composer with version '4.6.14' and encountered an error indicating that the file could not be unzipped, suggesting it might not be a zipfile or is part of a multi-part archive.
Solution:
We regret to inform you that installing WPML using Composer is currently not supported. This feature has been requested but has not been implemented yet due to certain limitations.
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 problem persists, please open a new support ticket for further assistance.
Problem: The client installed WPML to create English and French versions of their WP EasyCart store, but the entire site got translated instead of just the EasyCart store pages.
Solution: We recommend checking if automatic translation is active on your site, which could be translating all content automatically. You can change this by navigating to WPML -> Settings -> Translation Mode and selecting "Translate What You Choose". This setting prevents content from being sent to automatic translation without your approval.
For content you wish to translate manually, click the + icon in the Language section to add a translation, or the pencil icon to update an existing translation. If you prefer, you can also use the Advanced Translation Editor (ATE) for auto-translation while editing. For more detailed guidance, please visit the following links:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related 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 open a new support ticket.
Problem: You are experiencing an issue where the main page elements on the French page (/fr/) are shifted to the left after setting up the French language using WPML with the Woodmart Theme and following the documentation for custom fields translations. Solution: We recommend making a small modification to the original page and saving it. After this, proceed to the WPML translation editor to update the translation. This action can often resolve alignment issues caused by initial translations.
If this solution does not resolve your issue or seems irrelevant due to it 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 problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are looking for a plugin recommendation for setting up a multistore with different domains, both multilingual, that works well with WPML. Solution: We recommend using the WooCommerce Multistore plugin for WooCommerce platforms. This plugin allows you to manage multiple stores across different domains or subdomains and integrates well with WPML for handling translations and multilingual content. Ensure that each store in the multistore setup is configured correctly for WPML compatibility and test the setup thoroughly during development to ensure smooth operation across domains.
If this solution becomes irrelevant, outdated, or does not apply 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
