Problem: The client is creating a new website using WordPress and wants to use WPML to manage different versions for the US and UK. They are concerned about the URL structure because the language code 'uk' is typically used for Ukrainian, and they want to use it for the UK version of their site. Solution: We recommend not altering the WPML languages table to change the Ukrainian language code to something else and then creating a custom language for 'uk'. This is because 'uk' as a language code for Ukraine is an international standard. You can use "en" or "en-gb" for Great Britain. For the US version, you should use the custom language code "en-us". Using incorrect language codes can negatively impact SEO by causing incorrect targeting, poor user experience, duplicate content issues, and hreflang tag errors. To avoid these issues, ensure you use the correct language codes and implement hreflang tags properly. This will help search engines understand which version of your content to show based on language and location. For more details on setting up custom languages, visit: WPML Custom Languages Setup Guide For information on country codes, refer to: Country Codes Reference
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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: You are experiencing numbers being added to your URLs on your site, and you want to know why these numbers are there and how to remove them. Solution: The numbers added to your URLs are likely caused by the Geolocate feature in WooCommerce, not by WPML. To resolve this issue, we recommend checking if you have the Geolocate feature enabled in WooCommerce and consider disabling it if it's not necessary for your site's functionality. For more details on how to address this issue, please review this article.
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.
Problem: You are experiencing issues with WPML not activating and triggering a fatal error when using the Enfold child theme. Despite various troubleshooting steps like changing PHP versions, resetting WPML, and adjusting theme settings, the problem persists. Solution: We have identified that your Enfold child theme lacks necessary code and does not include the enqueue scripts in the
functions.php
file. Since the child theme does not contain any critical information, we recommend deleting this child theme and recreating it using a reliable plugin. This approach should resolve the activation issue 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 the problem persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to apply different page templates to translated pages using the Full Site Editing (FSE) system, but you cannot see the option to select a 'template' under the page options in the block editor for these translated pages. Solution: We recommend following the steps outlined in this article on how to use different translation editors for different pages, which might help you manage templates for translated content more effectively: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, please check the 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 you continue to experience issues. You can do so here: WPML Support Forum.
Problem: The client is unable to translate the footer designed with Divi Theme Builder using WPML. The footer appears untranslated in the English version even after attempting direct translation in the Divi Theme Builder and using WPML's translation tools. Solution: 1. Open the Footer template for editing by navigating to the specific post in the WordPress admin area. 2. Make a minor change in the template to refresh the translation settings. 3. Update the template. 4. Update the translation using the WPML Advanced Translation Editor. 5. Visit the English homepage to see the changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML support forum.
Problem: The client is experiencing an issue where a URL in the footer does not translate correctly on the Danish and German versions of their site, despite being saved in WPML's string translations. The issue is that the URL appears with an extra 'www' which leads to missing links. Solution: We recommend checking and adjusting the URL directly in the menus for each language. Here are the steps to follow: - Go to Appearance > Menu - Click the Pencil icon beside the Language name. - Open the menu item and adjust the link by removing the 'www' part.
This solution might not be relevant if the details of the issue have changed, or if it's outdated. If this doesn't resolve the issue, or if the problem described doesn't exactly match your situation, please visit our support forum to open a new 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 trying to translate the currency sign (лв.) to BGN on the English version of your site. Solution: First, ensure you have a backup of your site. Then, insert the following code into your theme's functions.php file:
add_filter("woocommerce_currency_symbol", "change_existing_currency_symbol", 10, 2);
function change_existing_currency_symbol($currency_symbol, $currency) {
switch ($currency) {
case "BGN": // Assuming BGN is the currency code for Bulgarian Lev
if (ICL_LANGUAGE_CODE == "en") {
$currency_symbol = __("лв.", "your-domain-name-here");
} else {
$currency_symbol = __("лв.", "your-domain-name-here"); // You can provide a different symbol for other languages if needed
}
break;
}
return $currency_symbol;
}
Please check if this resolves your issue. If this solution does not work or seems outdated, 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 https://wpml.org/forums/.
Problem: The client was experiencing issues with the alignment of the translation switching buttons in the global top bar of their website. The buttons were misaligned, with the English option being too far to the right and too high, past the divider. Solution: We identified that the issue was related to the theme's handling of these elements. After testing, we applied custom CSS to correct the alignment:
This CSS effectively hid the divider and adjusted the padding for the current language menu item, aligning the buttons properly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing issues where the WPML plugin cannot connect to wpml.org for updates, and there are problems with translated product category links and untranslated menu items. Solution: For the connection issue, it might be a false-positive caused by server caching. We recommend going to Plugins > Add New > Commercial, then clicking the "check for updates" button. If WPML still shows as registered after the page refreshes, the issue is likely just a false positive. For the issues regarding translated links and menu translations, due to our support policy of handling one issue per ticket, please open a new support ticket for each separate issue.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with redirections set up in Rankmath being overridden by WPML, causing URLs to redirect to incorrect language versions. This problem arises because you are using identical slugs for pages in different languages. Solution: We recommend ensuring that all your page slugs are unique across different languages on your website. For instance, instead of using 'wms' and 'wcs' for both English and French pages, use 'wms-fr' and 'wcs-fr' for French. This change should resolve the redirection issues. Here is a general guideline from WordPress on the importance of unique slugs: https://wordpress.stackexchange.com/questions/35315/must-slugs-be-unique
If this solution does not apply to your case, or if it seems outdated, please check the 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was unable to update the English translation of a static block, and products on translated pages were leading to broken links after translating some categories. Solution: We recommended translating categories in bulk using automatic translation. The client should create a product, assign all available categories to it, and send it for automatic translation via WPML > Translation Management > Dashboard. This should translate all assigned categories. Additionally, for the issue with the widget not being translated, the client should translate the widget at WPML > String Translation by selecting the text-domain "widgets". If this does not resolve the issue, creating one widget per language might be necessary. For further guidance, we suggest reading the quick guide on sending content for automatic translation at https://wpml.org/documentation/translating-your-contents/#sending-content-for-automatic-translation.
If the provided solution does not apply or is outdated, we recommend opening a new support ticket. It is also advisable to 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: The client needed the correct CSS code to apply a specific font for the Persian language on their website, after previously receiving incorrect information. Solution: We advised the client to use the CSS language selector
html[lang="fa-IR"]
for the Persian language. To apply the font across various elements like body, h1, h2, etc., the client should use the following code:
html[lang="fa-IR"] body { font-family: 'kalameh-fa' !important; }
If this solution does not resolve the issue or seems outdated, or if it does not apply to your case, we recommend opening a new support ticket. We also highly suggest 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 https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues where Polish language filter titles appear on the English version of your site, as seen here: https://romanskanieruchomosci.com/en/properties/, this might be due to untranslated placeholders in Elementor. Solution: We recommend that you edit the English archive template using Elementor and manually translate the placeholders. This should resolve the issue of language discrepancies on your multilingual site.
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 problem persists, please open a new support ticket.
Problem: The client experienced unexpected high usage of 60,000 credits for translating nine pages using WPML. The issue arose because the plugin translated pages that were already in English, leading to unnecessary credit expenditure. Solution: We explained that WPML needs to be set up with a single default language before adding translations. If the site already contains multiple languages, WPML might not recognize the existing language correctly and could translate content unnecessarily. We recommended checking the WPML > Translation Management > Tools section to view a usage report, which shows detailed information about translated pages, the translation engine used, and the credits spent. Additionally, we provided links to change the automatic translation engine (how to change automatic translation engines) and a cost calculator (calculate your cost). We also credited 30,000 credits back to the client's account to compensate for the misused credits.
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 (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 was unable to use the WPML system to translate new or edited content. They had activated the 'Pay-as-you-go' option but still had 588 credits left from a prepaid plan. The system required 1004 credits for a new article, and the client was unsure if it could use the remaining prepaid credits to cover the difference. Solution: We resolved the issue by first fixing a stuck translation from Polish to English. We then restarted the 'Translate Everything' option in WPML -> Translation Management by pausing it and pressing the 'Start automatic translation' button again. We chose to translate both new and existing content. This process first used the existing credits and then switched to the 'Pay-as-you-go' system. Now, the client can continue translating their site.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 https://wpml.org/forums/forum/english-support/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
