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/.
Problem: The client was unable to see the 900000 credits they previously had and was confused about why the renewal price was the same as the normal price, despite expecting a discounted rate. Solution: We clarified that the client currently has 120,000 unused and unassigned credits visible in their account (https://wpml.org/account). Additionally, they have 58,016 remaining credits from an initial assignment of 60,000 credits. We provided instructions on how to assign credits, available at https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/. Regarding the payment query, the initial charge for the Multilingual CMS subscription is 99 euros, with a renewal at 75% of that amount the following year, which aligns with the 74 euros charged. If there was an overcharge, we advised contacting the Accounts department at hello[at]wpml.org for resolution.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues where changes made to an Oxygen page in one language are replicating and destroying other language versions of the same page. Solution: We recommend pressing the Translate Independently button after switching to the WP editor. This action prevents changes from the default language from being synchronized to your secondary languages. For detailed guidance, please visit our documentation on using different translation editors for different pages: Using Different Translation Editors for Different Pages.
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.
Problem: After syncing menus using WP Menu Sync, visiting pages in secondary languages leads to a critical error. This issue is temporarily resolved by deleting the menu translations, which persist on the Front End despite deletion. Solution: Set the URL field in menu items to "Don't translate" as WPML automatically handles URL translation for menu items. If you need a URL field for other purposes, create a separate one with a different name to avoid conflicts. Additionally, remove the value
a:1:{i:0;s:0:"";}
from your theme's code, as it should be a string but is incorrectly formatted as a blank array, causing errors. Ensure that you fully translate the menu and verify its behavior on the Front End. If problems persist, 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 the issue still occurs, please open a new support ticket.
Problem: If you're experiencing issues with Google search results not displaying correctly for different languages, despite using WPML. Solution: We recommend verifying that the hreflang tags are implemented correctly on your site, as these are crucial for multilingual SEO and correct language-specific page indexing by Google. If the hreflang tags are working as expected and you still face issues with Google SERPs, the problem might lie outside WPML's control. In such cases, contacting Google support is advisable.
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.
Problem: The client is experiencing issues with WPML not functioning correctly after migrating their website from a production domain to a development domain. Solution: We recommend following the steps outlined in the documentation for using the Advanced Translation Editor after moving or using a copy of your site. First, ensure you perform a full site backup. Then, when prompted, select the mark it as copy option in the alert message. Check if the issue persists after these steps. If problems continue, please provide us with access to your admin area for further investigation, ensuring you follow our privacy and security guidelines.
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.
Problem: The client is trying to use the auto-translate feature on their multisite setup but receives a message stating they don't have enough credits for automatic translation. Solution: We recommend the following steps to resolve the issue: 1. Ensure WPML is installed and registered to the network to use it on your multisite. All subsites will use the same site key. For more details, refer to our documentation on installing WPML on a multisite. 2. Perform a full site backup. 3. Navigate to your account page at WPML account sites. 4. Delete the existing site key. 5. Go to Plugins > Add New > Commercial tab, click on "Unregister WPML from this site", and refresh the page. 6. Click on "Get a key for this site" and copy the newly generated code. 7. Return to Plugins > Add New > Commercial tab and register the site with the new key.
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 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: The client is experiencing issues with the Russian checkout page on their WooCommerce site. While the checkout pages in Estonian and English are functioning correctly, the Russian page is visually off and continues to load indefinitely. Solution: We discovered that the checkout page template in Russian might not have been translated correctly. If you're experiencing this, we recommend checking if the template was built with Elementor and ensuring it's correctly translated. Additionally, the client managed to implement a temporary fix by modifying the
wc_get_terms_and_conditions_checkbox_text()
function in the WooCommerce plugin files to ensure proper link handling in terms and conditions. This change was made in the
wc-template-functions.php
file.
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 issue persists, please open a new support ticket.
Problem: You are trying to translate the 'Read More' text of the Read More block in WordPress Gutenberg using the Twenty Twenty Four theme. Despite following the provided documentation and adding translations to all the read more String Translations, the 'Read More' text is not translating on your home page in Spanish. Solution: We manually translated the strings for you via the Gutenberg block editor. To see how we did this, you can refer to this screen recording: https://go.screenpal.com/watch/cZiVQmV8t26.
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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client was facing an issue where the translated text in the payment stripe gateway setting of the motopress plugin was not displaying correctly on their website. The text continued to show in the default language despite being translated.
Solution: We resolved the issue by navigating to WPML -> String Translation. The problem was that the language of the strings was incorrectly set. Although the string was in Italian, it was mistakenly set as English in WPML, which caused the default language text to display. We corrected the language setting to Italian and added the English translation, after which the translations displayed correctly. For more details on how to change the source language of strings, please visit How to Change the Source Language of Strings.
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 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 contact us through the WPML support forum.
Problem: The client is using PHP to store URLs in data attributes for a JS-powered slider, and needs these URLs to adapt based on the active language. The client is concerned about the scenario where the WPML plugin might be deactivated and seeks a fallback method. Solution: We recommend using wpml_home_url instead of
get_site_url()
to ensure URLs reflect the current language. To safely check if WPML is active before using this function, you can wrap your code in the wpml_loaded hook. Alternatively, use WordPress's
is_plugin_active
function or check the wpml_default_language hook; if WPML is not active, it will return NULL.
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 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
