Problem: After upgrading to PHP 8.2, you might encounter deprecation warnings related to WPML, specifically with dynamic properties in Whip_RequirementsChecker. These warnings appear as 'Deprecated: Creation of dynamic property Whip_RequirementsChecker::$configuration' and 'Deprecated: Creation of dynamic property Whip_RequirementsChecker::$messageManager'. Solution: Currently, PHP 8.2.x is not fully compatible with WPML. The warnings you see are due to deprecated functions that will need updating but are still operational. To prevent these warnings from displaying to your visitors, we recommend disabling the debug mode in WordPress. You can do this by editing your wp-config.php file and ensuring it includes the following line:
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
Problem: The client was encountering a fatal error when trying to open the WPML/Languages menu item in their WordPress site. The error message indicated a call to an undefined function 'wpml_tm_load_tp_networking()'. Solution: We recommended the client to manually download and reinstall the 'WPML Multilingual CMS' plugin from the WPML account downloads section. Despite reinstallation and cache clearing, the issue persisted. We then accessed the site with the client's permission to investigate further. After troubleshooting, we added a function to recreate any missing WPML tables in the database, which resolved the issue on the live site. We advised the client to apply the same workaround on the staging site and to deactivate and reactivate all plugins to ensure the cache was flushed.
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 problems persist, please open a new support ticket.
Problem: The client is experiencing a 504 timeout error when using Custom Post Type UI (CPTUI) with Advanced Custom Fields (ACF) on a WPML staging site. The issue persists despite various tests and disabling other plugins. The error seems related to a conflict between a custom post type named 'Products' and WooCommerce Products. Solution: We recommended increasing the PHP Time Limit to 300 from 120 to see if it resolves the timeout issue. We confirmed that CPTUI is compatible with WPML and there are no known issues causing a 504 error between these plugins. We provided a sandbox environment for the client to test CPTUI and ACF without migrating the full site, which can help determine if the issue is related to the hosting environment or the plugins themselves. Access the sandbox here: Sandbox Login Link
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 at WPML support forum.
Problem: The client attempted to change the URL format on their WordPress website to differentiate between languages (e.g., https://www.example.com/fr/ for French and https://www.example.com/en/ for English), but encountered an issue where changing the URL would always redirect to the homepage of the default language. Solution: We recommended the client to check for potential conflicts with other plugins by following these steps: 1. Deactivate all plugins except for WPML CMS. 2. Temporarily switch to a default WordPress theme, such as Twenty Twenty-One. This process helps determine if another plugin or the theme is causing the issue with the URL format. We also advised the client to back up their database before performing these tests.
If the problem persists or if this solution is not applicable due to updates or different circumstances, 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to automatically translate button URLs on their website using WPML. Despite setting the links directly and using various WPML tools like re-saving permalinks, deleting WPML cache, and scanning and adjusting links, the URLs are not appearing in the WPML Advanced editor for translation. Solution: We recommend the following steps to address the issue: 1. Ensure that the target page of the button URL (Page A) is translated before translating the page with the button (Page B). 2. After translating Page A, go to WPML > Settings > Translate Link Targets to force WPML to recognize and translate the button URL. 3. Alternatively, make a minor modification to Page B and retranslate it. This should allow WPML to automatically create the translated link. If these steps do not resolve the issue, we suggest removing any custom configurations related to this problem and testing again to see if the issue is workflow-related.
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 at WPML support forum for further assistance.
Problem: If you're trying to manage translations and encounter an empty page when accessing the WPML > Translations page, it might be due to a stuck translation job. Solution: We recommend checking for any old or stuck translation jobs at WPML > Translation Management > Jobs. In this specific case, we identified and resolved an issue with a translation job from March 2024 that was causing the problem. You should now be able to access the WPML > Translations page without 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is unsure about the correct DNS settings for configuring WPML with different domains per language. They have domains like italianbracelet.de, .fr, .eu, and .be, and want each to display content in specific languages based on the domain. Solution: We recommend contacting your hosting provider to add all domains to your DNS setup using parked domains. Specifically, you should request to park domains such as italianbracelet.de, italianbracelet.fr, italianbracelet.eu, and italianbracelet.be as aliases to your main domain. Here are the steps: 1. Contact your hosting provider and request to add a parked domain (alias) to your existing domain. 2. Specify the exact domain names that need to be parked. 3. Follow the guides provided by WPML and your hosting provider for detailed instructions:
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we encourage you to open a new support ticket.
Problem: The client is developing a site and needs help selecting a cookie consent plugin that is compatible with WPML, supports cookie consent mode V2, and can be used across multiple domains. Solution: We recommend checking our list of WPML-compatible cookie consent plugins to find one that meets your requirements. You can view the list here: WPML Compatible Cookie Consent Plugins. It's important to verify the specific functionalities directly on the plugin's page or with the plugin author, as we ensure compatibility with WPML but do not confirm additional functionalities.
If you need further assistance or if this solution does not resolve your issue, 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 the issue persists, please open a new support ticket at WPML Support Forum.
Problem: You are trying to update to the current version of WPML and have installed it correctly. However, you see a message on the plugin page in WordPress stating 'Your WPML account has expired. Purchase today to protect your site from breaking changes in future WordPress releases.' Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Visit https://wpml.org/account/sites 2. Remove the current key. 3. Generate a new production key for that domain. 4. Copy the new key. 5. Go to your site's backend > Plugins > Add new > Commercial. 6. Unregister WPML first from the old key. 7. Re-register WPML with the new key. Additionally, please clear any existing local or server caching.
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 the problem persists, please open a new support ticket.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also contact our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You need help translating the menu on your site using WPML. Solution: We recommend following our guide to learn how to translate your menu. You can find the guide here: Translating Menus. If you're still experiencing an issue after following the guide, please provide more details about your problem. Uploading screenshots can also be very helpful in clarifying any issues.
Please note that the solution provided 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, feel free to open a new support ticket at WPML Support Forum.
Problem: The client has numerous categories in a bilingual GA/EN setup, where categories are randomly set with their original language instead of all being set to GA as intended. Manually adjusting each category's original language for about 150 categories is impractical. Solution: We recommend the following steps to streamline the process of setting GA as the original language for all categories: 1. Delete the translations, keeping only the categories in the default language. 2. Create a dummy product and add all the categories to it. 3. Use the translation editor to translate these categories. If using the advanced translation editor and the categories were previously translated, they should appear translated. 4. Save the product to set GA as the default language for these categories. 5. Navigate to WooCommerce Multilingual > Categories, scroll to the bottom of the page, and click the button to synchronize the categories across all products. Before proceeding, ensure you back up your site and perhaps start with just one or two categories to familiarize yourself with the process and check for any unexpected issues.
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: If you're experiencing an issue where a template is not applied to a product page translated with WPML using Elementor Pro, even though it works with other templates. Solution: We recommend the following steps to resolve this issue: 1. Edit the original product and make a minor change (e.g., add a space in the product title). 2. Click the update button to trigger an update for the translation. This change should turn the pencil icon into a circled arrow icon. 3. Edit the translation using the Advanced Translation Editor and complete it. After these steps, the template from the original product should also apply to the translated product.
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 at WPML support forum.
Problem: The client has multiple branches with the same page titles (e.g., 'Dining') under different URLs (e.g., /london/dining, /berlin/dining) within their website. In WPML's Translation Management, these pages appear with the same title without showing their full URL or hierarchy, making it difficult to identify and translate the correct page for a specific branch. Solution: 1. If the pages are not set as child pages but follow a hierarchical structure like destination pages (London, Spain, etc.), you can assign a translation priority when editing the page. This allows you to filter pages by priority in WPML's Translation Management. 2. Another method is to hover over the 'Edit' button for the page in the Translation Management dashboard. This action will display the URL in the browser's status bar or tooltip, showing the post ID. You can use this ID to identify the correct 'Dining' page to translate.
If these solutions do not apply to your case, or if they seem outdated, we recommend opening a new support ticket. We also highly 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
