Problem: The client is experiencing inconsistent search results in a secondary language using WPML and Elementor. The issue does not occur in a staging environment with only WPML, Elementor, and a default WordPress theme active, suggesting the problem might be related to the custom theme or another plugin. Solution: We recommend creating a staging site and testing with only WPML plugins and Elementor active, then temporarily switching to a default WordPress theme. This will help determine if the issue is caused by a third-party plugin, custom theme, or custom code. If the problem persists in this minimal setup, further investigation into the custom theme or plugins is necessary. Gradually enable plugins to see if the issue reappears, and if it doesn’t, the custom theme is likely the cause. Trace the code being executed on the specific page/action to identify potential interference.
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where your sitemaps are not working correctly on different language domains, such as receiving a 404 error when accessing the sitemap for a translated version of your site, this might be due to the taxonomy settings. Solution: We recommend checking if the taxonomy for your models is set to be displayed as translated. It's important to ensure that these taxonomies are not only set to be displayed as translated but are actually translated. You can do this by selecting one of the models and translating it to see if this resolves the issue.
If this solution does not apply to your case, or if it seems outdated, please do not hesitate 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. For further assistance, you can always contact us through the WPML support forum.
Problem: You are experiencing discrepancies in product display and WooCommerce behavior across different language versions of your website. Specifically, issues include inconsistent product visibility in different language versions and the 'Hide out of stock items from the catalog' setting not working consistently. Solution: To ensure product visibility is consistent across all translations, check that the taxonomy product_visibility is set to Not translatable under WPML → Settings → Taxonomies Translation. This setting should sync product visibility automatically across all translations. If discrepancies persist, navigate to
and use the 'Fix incorrect or missing translation links for product variations' option to re-link everything properly.
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 problems continue, please open a new support ticket.
Problem: You are trying to translate a timetable created with the Timetable Responsive Schedule For WordPress plugin using WPML. While you have successfully translated Events, you are facing issues with translating Timetable columns and event hours. The translations for Timetable columns disappear after saving, and event hours do not appear as strings in String Translation, preventing you from having separate event hours with texts in different languages. Solution: 1. The Timetable Responsive Schedule For WordPress plugin is not listed as compatible with WPML. We recommend contacting the plugin authors to confirm if their plugin supports WPML and to request steps for proper translation. 2. Ensure all WPML plugins are up-to-date by creating a full site backup and then updating your plugins. You can update WPML plugins via Plugins -> Add new -> Commercial tab -> Click on the button to get the most recent updates.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are encountering a PHP warning related to the WPML plugin, specifically an 'Undefined array key "REQUEST_METHOD"' error. This issue occurs in non-browser contexts such as WP-CLI commands, scheduled cron jobs, or when custom code triggers certain WPML functions outside of a normal page load. Solution: To address this issue temporarily, you can modify your custom code to set the 'REQUEST_METHOD' in the $_SERVER superglobal before WPML functions are called. Here is how you can do it:
<?php<br />$_SERVER['REQUEST_METHOD'] = 'GET';<br /><br />// ... rest of the script.
We have already reported this issue to our developers, and a fix will be included in future versions of the plugin.
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 was experiencing an infinite loading issue in the WPML Translation Management dashboard, accompanied by console errors indicating a 'Request failed with status code 500'. Despite disabling all non-WPML plugins and changing themes, the issue persisted. Solution: We initially suspected a conflict with a third-party plugin and recommended disabling all plugins except those related to WPML and switching to a default WordPress theme. However, the actual resolution involved addressing a missing secondary language on the website. We added English back as a secondary language, which resolved the infinite loading issue. If you're experiencing similar issues, we recommend checking for any missing languages in your WPML settings and ensuring all intended languages are properly configured.
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 trying to configure different domains for each language on your site using WPML, but encounter a 'not valid' error when saving the settings. The domains include thermex.ee for Estonian, thermexlt.lt for Lithuanian, and ru.thermex.lv for Russian, all pointing to the same IP as the main site. Solution: 1. Check if the error is a false positive by unchecking the validate checkbox and saving the settings. If your site functions correctly afterwards, the error may not be significant. 2. Ensure there are no static constants for WP_SITEURL or WP_HOME in your wp-config.php file, as these could interfere with validation when using different domains for each language. 3. Verify that there are no separate websites running on the additional domains. All domains should display the main website when WPML is disabled. If this is not the case, it might be a misconfiguration in your DNS settings. 4. Once your domain configuration is correct and all domains display the default language version of your site without WPML, you can re-enable WPML. If issues persist, contact us for further assistance.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
