Problem: When switching the site language to English and clicking on the logo, instead of redirecting to the homepage, it leads to a different page or shows a 404 error. Solution: This issue occurs because the homepage has not been translated into the secondary language (English). When the site is translated, the homepage URL changes to include language parameters, such as
https://your-site.al/?lang=en
or
https://your-site.al/en/
. To resolve this, you need to translate the homepage into English. Once translated, clicking the logo in the English version will correctly redirect to the English homepage instead of showing a 404 error.
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 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 experiencing style issues with the language switcher on mobile devices. Solution: We have determined that the problem might not be directly related to WPML or the language switcher itself, but rather to how your current theme handles dropdown items in mobile view. We recommend trying one of the following solutions: 1. Change the language switcher style to a horizontal list and disable the display of the current language to save space. 2. If your theme supports it, consider creating a separate header for mobile devices that allows for better customization of elements specifically for mobile users.
Please note that this solution might be outdated or not directly 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: The client reported style issues on the RU and UZ pages of their website, specifically with the 'Certifications' and 'Contact Us' blocks. Solution: We identified that the theme styles were not copied over to the translations, causing the display issues. Here's how we fixed it: 1. Navigate to WPML → Settings → Custom Fields Translation and activate the option labeled "Show 'Multilingual Content Setup' meta box on post edit screen." 2. Go to the home page of the original content. 3. Scroll to the bottom of the page and click on "Show system fields." 4. Identify the custom fields associated with your theme that may contain the layout settings and set them to "Copy." 5. Make a slight modification to the original page and save your changes. 6. Access the WPML translation editor and complete the translation. For more details on translating custom fields, visit https://wpml.org/documentation/getting-started-guide/translating-custom-fields/.
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: The client was experiencing issues with their multilingual WordPress site using WPML and Elementor. Specifically, links on buttons were not redirecting to the correct language-specific product pages, and images were not displaying on the German version of the site. Solution: 1. We advised the client to manually translate custom links as described in our documentation on how to translate links. 2. To address the translation issues, we edited the primary language page and retranslated the page using the Advanced Translation Editor. 3. For the images not displaying, we re-saved and retranslated the product, ensuring that images were correctly linked and displayed in the translated version.
If this solution does not resolve your issue or seems outdated, we 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 reported that after updating the
post_name
of a translated product, the permalink (URL) does not update to reflect the English version, even after trying to flush rewrite rules. Solution: We suggested using a custom function to ensure that when a post is duplicated in WPML, its permalink (slug) updates to match the original post's slug. Here is the function to add to your theme's functions.php file or a custom plugin:
We also recommended testing this solution in a sandbox environment and recording the process using a tool like https://www.loom.com/ to better understand the issue.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 for further assistance.
Problem: The client is experiencing an issue where French is still appearing in the menu despite having enabled the setting to hide languages from untranslated pages. Solution: We recommend clearing your browser cache as a first step to resolve this issue. It's possible that cached data is causing the French language to still appear even though the settings have been adjusted to hide it. If after clearing the cache the problem persists, please check your WPML settings again to ensure they are configured correctly to hide untranslated languages.
If this solution does not resolve the 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. Additionally, you can open a new support ticket with us for further assistance at WPML Support Forum.
Problem: After installing the WPML plugin, the client does not see a menu on their site. Solution: If you're experiencing this issue, we recommend you try manually updating the WPML plugins by following these steps: 1. Download fresh copies of the WPML plugins from wpml.org. 2. Log in to your WPML.org account and go to the Downloads page. Download the plugins. 3. On your website, navigate to Plugins → All Plugins and delete WPML and all its components. 4. After that, go to Plugins and upload the plugins. 5. Activate them.
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 at WPML support forum.
Problem: You are experiencing an issue where all product categories are displayed in the original version of your store, but in the Russian version, half of the categories are missing. These categories are translated and function correctly but do not appear on the store page. Solution: We recommend trying the following workaround: 1. Add the following code to your
functions.php
file inside your theme folder:
testfix();<br />function testfix(){<br /> global $wpdb;<br /> $elements = $wpdb->get_results("SELECT `element_id`<br />FROM {$wpdb->prefix}icl_translations<br />WHERE `element_type` = 'tax_product_cat' ORDER BY `trid`");<br />foreach ($elements as $element){<br /> $testelement = get_term_meta($element->element_id, 'order', true);<br /> if ($testelement == ""){<br /> add_term_meta($element->element_id, 'order', 0);<br /> }<br />}<br />}
2. Set the sort to category order in the widgets. 3. Visit the front end once. 4. Delete the code from the
functions.php
file after checking.
Please ensure to backup your site before implementing this test to avoid any potential issues.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Symptoms:
When translating the 'header' template part, there are no strings found. Additionally, my block theme has only 1 header template part, but there are 3 listed under the 'Template Part' section in 'Translation Management'.
Questions:
What am I missing when translating the 'header' template part since no strings are found?
Why are there 3 header template parts listed under 'Template Part' in 'Translation Management' when my block theme has only 1?
Solution:
Under "Translation Management" is a section "Navigation Menus". For some reason I thought this was for classic themes and ignored it. Turns out that this is very Navigation Block menus live. The name "Main Menu" is set per default in the Block Editor Inspector Sidebar under "Advanced" (when editing the Navigation Block), which was the reason why I got confused.
Problem: If you're experiencing issues with your WordPress site not displaying credits in the WPML translation management tools, it might be due to a plugin conflict. Solution: We recommend deactivating the 'HelloPack Client' plugin to resolve this issue. After deactivating, you should be able to register WPML plugins and see the site prepaid credits correctly. 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are working on a site under development and trying to translate an image link using WPML. You translated an image link that didn't need translation, and now you can't remove it without affecting the translation completion status. Additionally, you receive an error message stating: "The original text contains nested formation tags (one tag inside another). Please nest the formatting markers in your translation in the same order," which prevents the post from being 100% translated. Solution: We recommend making a minor edit to the page and then attempting the translation again. 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.
Problem: You are experiencing an issue where the logo link on your multilingual WordPress website redirects correctly in the primary language but redirects to the blog page instead of the translated homepage in the secondary language. Solution: We found that the problem was due to a translated string (
admin_texts_show_on_front
) that should not have been translated. To resolve this, you should delete the translation of this string. After doing so, the homepage should open correctly in the secondary language.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
Problem: The client updated the slugs for custom post types (CPTs) in different languages using WPML settings but encountered issues where the CPT pages sometimes display a 404 error or redirect to the homepage after the first page refresh. This issue persists even after clearing various caches. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Ensure that the slug translations are correctly set for each CPT in WPML -> Settings -> Post types translation. 2. Clear the WPML cache by navigating to WPML -> Support -> Troubleshooting -> Clear the cache in WPML. 3. Also, clear the full site cache on your hosting provider's dashboard. 4. If the issue persists, it might be related to how caching is handled on your server. Since the client's server is with Kinsta and caching cannot be disabled, consider testing changes in a staging environment where caching is not enabled.
If these steps do not resolve the issue or if it reoccurs, it might be due to a configuration that is specific to your environment or possibly an outdated solution. 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 with us for further assistance at WPML support forum.
Problem: You are experiencing issues with the currency converter on your WooCommerce site, where the currency symbol changes but the amount does not convert correctly for some products. This issue arises because the prices are stored in the wp_postmeta table using comma separators instead of decimal points, which prevents them from being recognized as numbers suitable for calculations. Solution: To resolve this, you need to correct the format in which prices are stored: 1. For simple products, simply re-save each product. This action will update the price format in the wp_postmeta table to the correct decimal point format. 2. For variable products, re-saving the parent product alone will not suffice if the prices are not altered. You must change the price of each variation slightly to trigger the update in storage format. We have created a video to guide you through these steps, which you can view here: Video Guide.
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 with us for further assistance.
Problem: You are experiencing issues with importing XLIFF files for translation on a site that has recently switched from Polylang Pro to WPML. The import fails for two of the pages, and you suspect it might be related to a plugin conflict. Solution: We recommend temporarily deactivating the YoastSEO plugin and its Pro version, then attempting the XLIFF import again. Ensure you perform a full website backup before making these changes. If the problem persists or occurs with other XLIFF imports, please contact us for further assistance.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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 continues, do not hesitate to open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
