Problem: You are encountering a persistent issue with an import script that fails every time it runs, throwing a Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, false given. This occurs due to the script receiving a false value from
get_post_meta
when an invalid post_id is used. Solution: We recommend trying the following steps to potentially resolve the issue: 1. Ensure you take a backup of your site's database. 2. Navigate to WPML -> Support -> Troubleshooting. 3. On the troubleshooting screen, press 'Remove ghost entries from the translation tables'. *** Please backup your database before using this.***
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: You are using Elementor with the Astra Pro theme and have a WooCommerce shortcode on your homepage to display featured products. This shortcode works correctly in the main language but fails in the translated version. Disabling the 'WooCommerce Multilingual' plugin allows the shortcode to function, but then the product shop page does not display translated products. Solution: We found that the 'icl_sitepress_settings' key in your site's wp-options table was corrupted. Here are the steps to resolve the issue: 1. Open your database manager, such as PhpMyAdmin. 2. Navigate to the wp_options table. 3. Search for 'icl_sitepress_settings'. 4. Delete this key. 5. Go to your site's dashboard. 6. Click 'Configure WPML'. 7. Complete the setup. 8. Check the translated homepage. Please ensure to backup your database before performing these steps.
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 the problem persists, please open a new support ticket.
Problem: The client manually changed the language for content in Cambodia using Elementor, but after updating the WPML plugin or over time, the translated content reverted back to the default language (English). This issue also affected banners and texts in other countries, causing them to revert to English. Solution: If you're experiencing similar issues where your manually translated content reverts to the default language after a WPML update or over time, we recommend switching to the WordPress editor for your translations. This can be done from the language sidebar in WordPress. It's important not to mix translation methods (manual and WPML editor) as this can lead to the issues you're facing. For a detailed guide on how to manage manual translations and switch editors, please visit: 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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with variation details not displaying on category pages for some variable products in a bilingual WordPress site using WPML, WooCommerce, and WPBakery, the problem might be due to incorrect synchronization of product attributes and variations. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WooCommerce > WooCommerce Multilingual > Attributes. 2. Select the attribute from which the variations were created. 3. Click the button at the bottom of the section to synchronize attributes. Repeat this for any other relevant attributes. 4. Go to WooCommerce > WooCommerce Multilingual > Status and click on the Troubleshooting link. 5. On the Troubleshooting page, follow the instructions shown in this screenshot and click the Start button. 6. Visit WPML > Support > Troubleshooting, select "Products" from the Dropdown under cleanup, click on the Synchronize Post Taxonomies Button, and repeat for "Variations".
If the issue persists, it might be due to WooCommerce's behavior of not displaying variation details for products with multiple variations on archive pages. This requires custom coding to alter. For further customization, you might consider hiring a developer from our recommended resources.
If attributes are still not showing in the translated version after completing these steps, ensure the WooCommerce Multilingual plugin is active, update the attribute and product in the default language, and then update the translation.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant 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. Please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You want to display different currency indicators depending on the language version of the website. Specifically, you want to show 'KWD' for the English version and the Arabic symbol for the Arabic version, but currently, only the Arabic version of the currency shows on all languages. Solution: This functionality is not directly available with WCML, but it can be achieved through custom work using WooCommerce hooks. We recommend reviewing the solution provided in this forum thread. NOTE: Custom code is not supported by our team. Always ensure you have a recent and working backup before implementing any changes recommended by our team or a third party.
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.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client needed clarification on whether changing the domain of a site affects WPML settings and if they should transfer the WPML key from one installation to another or obtain a new one. Solution: 1. We recommend creating a full website backup before making any changes to the domain. 2. For a new domain, it is necessary to create a new WPML key and remove the old one. Both actions can be performed here. 3. After obtaining the new key, navigate to your site > Plugins > Add new > Commercial, then unregister WPML using the old key and re-register it with the new key. 4. If you revert to the original domain later, you can reuse the previously created key for that domain.
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.
Problem: The client transferred a WPML account to another person who was later fired, and now no one in the company can access the account to renew the subscription. The client is unsure if they need to repurchase the subscription as a new customer or if there is a way to transfer it back. Solution: If the account was transferred and the new account holder is no longer available, the only option is to let that account expire and create a new WPML account. The client will need to purchase a new subscription at the normal price, as the discount benefits from the previous account are no longer accessible. They can generate a new key for their domain by creating a new account and logging in at https://wpml.org/account/sites. If the email associated with the old account is owned by the company, they might regain access by contacting the Accounts team at hello[at]wpml.org.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with the language switcher appearing in the footer of your site, Solution: We recommend navigating to WPML > Languages > Footer language switcher. From there, you can completely remove the language switcher, and it should stop showing in the footer area of your 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 issue persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You have a notification banner on top of your main menu that keeps changing to a different language, which is not your main language. The banner changes languages unexpectedly and is created using the Customizer with the ASTRA theme. All translations are managed via WPML. Solution: If you're experiencing this issue, we recommend checking the WPML->String Translation to ensure that the banner is correctly translated and registered under the domain
. Also, verify if you are using any site or server caching, as this might affect how translations are displayed. If the problem persists, consider setting the language of the selected strings from your main language to English and back, as this has resolved the issue in some cases.
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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to change the names of languages in their WPML settings. Solution: If you're experiencing this issue, we recommend navigating to WPML > Languages > Edit Languages. Here, you can change the language names to your desired ones and then save the changes.
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: The client is developing a new version of their website using the Impreza theme and needs help integrating the WPML language switcher into the header, instead of its current position at the bottom of the pages. Solution: We advised the client to use either PHP or shortcodes to add the language switcher to the header template. Detailed instructions on how to implement this can be found in our documentation on adding language switchers using PHP and shortcodes. Additionally, the client can add a language switcher to the menu by navigating to WPML > Languages > Menu Language switcher section and creating a new language switcher.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the currency switcher on their WooCommerce product pages is displaying 'USD' twice. Solution: We recommend the following steps to identify and resolve the issue: 1. Create a full backup of your website. 2. Deactivate all plugins except for WPML and its add-ons. 3. Check if the issue persists. 4. If the issue is resolved, reactivate your plugins one by one to identify the problematic plugin. 5. If the issue still occurs with only WPML plugins active, switch to a default WordPress theme like TwentySeventeen and check again. We suggest performing these steps in a staging environment if possible.
If these steps do not resolve the issue or if the solution provided here becomes 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.
Problem: The client is experiencing an Error 500 when trying to edit the Dutch homepage of their site. This issue is linked to a PHP memory limit being exhausted, as indicated by the error log showing a fatal error in
wp-includes/meta.php
. Solution: We recommend increasing the PHP memory limit. You should contact your hosting provider to request an increase of the PHP memory limit to 512MB. Concurrently, adjust the WordPress memory limit to 512MB in your
wp-config.php
file. This adjustment should help resolve the Error 500. If the issue persists, consider disabling other plugins temporarily to reduce memory usage, allowing you to edit the homepage.
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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where YouTube videos displayed using 'Presto Player' disappear in some languages after visitors click on 'Accept all Cookies'. This problem was identified to be associated with WPML after disabling other plugins. Solution: We recommend the following steps to isolate and potentially resolve the issue: 1. Ensure that the 'Video Problem Test' page is translated into all languages on your sandbox site. 2. Switch the theme on your staging site to the default WordPress theme (e.g., Twenty Twenty-Four) and deactivate all third-party plugins except for WPML, Strings Translation, 'Presto Player', and 'Real Cookie Banner'. 3. If the issue does not persist under these conditions, reactivate the original theme and then each plugin one by one. This step-by-step approach will help identify if a specific theme or plugin reintroduces the problem.
If these steps do not resolve the issue or if it appears complex, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
