Problem: The client reported that the banner image on their blog category page was not translated, despite being processed through the Media Translation plugin. This issue was specific to the blog category page, as translations worked correctly on other pages. Solution: We discovered that the issue occurred only on the category page and suggested a workaround. We recommended rearranging the blocks on the page: moving the column containing the image block above the column that has the WordPress Archive Output block. This change should allow the translated image to display correctly on the frontend.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking for 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.
Problem: The client was unable to translate ACF fields despite having set them to 'translatable'. The fields remained greyed out. Solution: We recommended checking if the issue was specific to the ACF text fields by making changes in the Text Area or the Editor field values and saving these changes to see if there was any difference. If the problem persisted, we suggested providing admin access after ensuring a full site backup for further investigation. Upon receiving access, we identified that the translation preference for the 'Accordion' fields needed to be changed from 'Copy' to 'Copy once'. After applying this change, the fields were no longer greyed out, and the expected results were achieved on the staging site.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to import taxonomies and products for a WooCommerce site using WPML but encounters an issue where the content is imported in one language only, without creating translations. Solution: We recommend creating separate files for the taxonomies in each language. Import the taxonomies as translations of each other, then import the products in the original language, linking to the categories in the same language. This approach is detailed in our documentation here: Exporting Multilingual Content. Alternatively, you can use a single file containing the taxonomies in all languages if you configure it correctly. Both methods are valid and depend on your preference and setup. For further guidance, refer to the section in our documentation here: Preparing Import Files for WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 personalized assistance. You can contact our support team directly through our support forum here: WPML Support Forum.
Problem: The client created a post category template that appears correctly in the default Spanish language but has layout issues in other languages. The translated version is missing several divs, causing the layout to be inconsistent with the default template. Solution: We resolved the layout issue by adjusting the block arrangement in the WPML Advanced Editor. Specifically, on the staging site, we moved the "WordPress Archive Output" block under the "Column" block and above the "WordPress Archive Loop" block. The client should replicate these changes in the English and French translations of the layout. On the live site, we ungrouped the block items under the "WordPress Archive Loop" block, updated the translation layout, and cleared the SG cache. This adjustment made the layout in the English version consistent with the Spanish version.
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 the problem persists, please open a new support ticket.
Problem: The client is using JetSmartFilters on their learning hub, but the filters are not visible in the translated version. Solution: We recommend updating the JetSmartFilters plugin to the latest version, which is 3.5.0. You can download the update from https://crocoblock.com/changelog/. After updating, please verify if the filters appear in the translation. Additionally, ensure that all content is fully translated, as untranslated content might not display correctly in filters. For further guidance on making JetSmartFilters multilingual, please refer to the following documentation:
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.
Problem: The client reported that a small paragraph of text, specifically bullet points, was not being translated on multiple pages. Despite the translations being available, the English version was still displayed on the French version of the site. Solution: We recommended the client to edit the page in English, make a small change to the content of the bullet points, save the changes, and then update the translation. This action should ensure that the bullet point translations display correctly on the frontend.
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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to change the hreflang of a custom Japanese language from 'jp' to 'ja' while maintaining the language code 'jp'. They encountered an error stating 'The hreflang already exists' because the default Japanese language was using 'ja', even though it was not enabled. Solution: 1. Navigate to WPML->Languages and add the default language for Japanese. Pause automatic translation if it's active to prevent content creation in that language. 2. Click on "edit languages". 3. Change the hreflang for the default Japanese language from 'ja' to another value, such as 'ja-ja', and save the changes. 4. Refresh the page, then adjust the custom language setting from 'jp' to 'ja'. This should now allow the assignment of 'ja' as the hreflang. 5. Remove the default Japanese language since it is no longer in use.
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 unable to find and translate the 'Leggi Tutto' text in the footer using the 'Translate texts in admin screens' feature of WPML. Solution: We advised the client to check the WPML String Translation page directly by navigating to WPML String Translation where they could find and translate the strings containing 'Leggi Tutto'. Additionally, we suggested clearing the cache and trying from a different browser or device to see the changes. We also checked the widget settings to ensure the correct text was displayed and made adjustments as necessary.
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 WPML Support Forum.
Problem: You need to set different prices for product variations in different languages using WPML with WooCommerce, but the price field for product variations is locked. Solution: In WPML, when you translate products using WooCommerce Multilingual, all product translations share the same details as the original. It's not possible to set different product details for translations directly. If you aim to set custom prices in different currencies, this can only be done on the original product. The price will then be copied to the translated product and, if using the Multi-currency feature, converted on-the-fly. To set completely different prices for translations, you should create individual products for each language independently, without translating the original products. These products will not be linked and will not share any product details. For more information on setting up multi-currency, please visit Multi-currency support in WooCommerce.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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.
Problem: The client is unable to register their site to their WPML account, despite having previous experience with another site. Solution: If you're experiencing issues registering your site to your WPML account, we recommend checking that you are entering the license key in the correct section. It's important to enter the WPML license key in the WPML section, not the Toolset section, even though both are part of the same company and appear on the same screen. Additionally, ensure that when adding the site to generate the license at https://wpml.org/account/sites, you use the exact URL format as shown in your WordPress admin under Settings > General. This includes the correct use of http or https and www or non-www.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking the related known issues at https://wpml.org/known-issues/. Please also verify that you have installed the latest versions of themes and plugins. If the problem persists, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing issues where changes made in the base language using Elementor Pro, such as layout and CSS styles, are not syncing correctly with the second and third languages. This problem is particularly evident in the mobile version, where changes like URL updates in Smart Slider are not reflected. Solution: First, ensure that any changes made in the default language are followed by updating the translations. This update is necessary for the changes to sync across all languages. If you are using automatic translation, this update should occur automatically. However, if the issue persists, it might be related to caching. We recommend deactivating any caching plugins temporarily to see if this resolves the issue. Specifically, with plugins like LiteSpeed Cache, consider adjusting settings to exclude certain pages or sections from being cached to prevent them from interfering with Elementor's functionality.
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 continue, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're using the MasterStudy LMS plugin recommended by WPML and notice that your website becomes inaccessible due to htaccess modifications, this might be relevant to you. The issue arises when third-party plugins frequently call the
flush_rewrite_rules(true)
function, leading to unwanted changes in the htaccess file. Solution: We recommend following these steps to address the issue: 1. Ensure you back up your site for safety. 2. Insert the following code into the functions.php file of your theme:
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 https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing an issue where you can only add one product to the cart instead of two when WPML is active. This problem occurs specifically when the PixelYourSite plugin is also enabled. Solution: We have identified that the issue does not occur when the PixelYourSite plugin is disabled. Since we have not tested this plugin for compatibility with WPML, we recommend contacting the plugin's author and suggesting they apply for our Go Global program to ensure full compatibility with WPML.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing a '400 bad request, request header or cookie too large, nginx' error after opening 4-6 pages in the WordPress admin. This issue started after installing WPML and persists until cookies are cleared, but reappears upon further navigation. Solution: We recommend checking if this issue occurs across different browsers such as Chrome, Firefox, and Safari. Although we couldn't find a similar case in our records, we suggest following the steps in these articles to troubleshoot and potentially resolve the issue:
If these steps do not resolve the issue, it might be due to an outdated solution or a different underlying problem. 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. If the problem persists, please open a new support ticket.
Problem: The client is experiencing a PHP Fatal error due to memory allocation issues. The error messages indicate that the server's memory limits are being reached, and there's an issue with output buffering in the WPML plugin's ComposerAutoloadClassLoader. Solution: We recommend contacting your hosting provider to discuss these errors and the server's resource limits. It's also advisable to investigate other plugins and recent changes on your website that might be causing resource usage spikes. Ensure all plugins and themes are updated to their latest versions. If these steps do not resolve the issue, it may be beneficial to consult the related known issues on WPML at https://wpml.org/known-issues/.
If this solution does not apply to your case, or if it becomes outdated, please open a new support ticket. We highly recommend checking the related known issues and confirming that you have installed the latest versions of themes and plugins. For further assistance, visit our support forum at https://wpml.org/forums/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
