Problem: The client is experiencing an issue where a code ?v=796834e7a283 is being added to their domain URL and suspects it is related to WPML.
Solution: The parameter ?v=XXXX in the URL is added by WooCommerce when the 'Default Customer Location' is set to 'Geolocate with page caching support'. To resolve this issue, the client should navigate to WooCommerce > Settings > General tab > Default customer location and change the setting. For further guidance, we recommend checking the WooCommerce documentation on configuring settings:
Problem: The client is experiencing an issue where menus created in Traditional Chinese default to English, and when creating an English menu, they are only able to add pages in Traditional Chinese. Additionally, menu synchronization does not work, and added pages disappear after saving. Solution: We recommend the following steps: 1. Ensure you have a backup of your website. 2. Navigate to WPML -> Support -> Troubleshooting. 3. Execute the functions listed one by one. For reference, please see the documentation here. 4. After completing the troubleshooting steps, try creating a test menu to see if the issue is resolved.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is unable to see categories in the default language (English) and can only view them when switching to 'All languages'. Solution: We recommend the following steps: 1. Ensure you have a full backup of your website. 2. Navigate to WPML -> Support -> Troubleshooting. 3. Execute the functions listed there one by one. For guidance, refer to this documentation. 4. After running the troubleshooting functions, check if the categories are visible in English.
Please remember to back up your database before performing these steps.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket in our support forum.
Problem: The client wants to have separate 404 pages for different languages instead of a single redirect via the 404.php page. Solution: We recommend the following steps to create language-specific 404 pages: 1. Ensure that the strings on the 404 page are wrapped in the gettext function. You can find more information on how to enable text translation for themes not compatible with WPML in our documentation: Enabling Text Translation for Themes Not Compatible with WPML. 2. Scan your theme for strings by navigating to WPML >> Theme and plugins localization, select your theme, and click the “Scan selected themes for strings” button. 3. Translate the required strings by going to WPML >> String Translation, searching for the strings, and adding their translations. 4. Use the
wpml_current_language
hook to get the current language and display or include content accordingly. For more details, check out our documentation: wpml_current_language Hook.
Problem: The client's site is showing a 403 error after their WPML subscription ended, and the error persists even after renewal. Solution: 1. Increase the WP Memory Limit to at least 128MB, as the current limit is 40MB which is below the minimum requirements for WPML. Add the following code to the top of your
2. Re-save Permalinks by navigating to Settings >> Permalinks in your WordPress dashboard and clicking the 'Save Changes' button.
3. Clear all types of cache on your site/server.
4. If the error is still there, deactivate all plugins except for WPML and its add-ons, and switch to the parent Woodmart theme. Then, reactivate each plugin one by one to identify the problematic one.
Problem: The client's site is experiencing slow performance, taking nearly 13 seconds to render each page, potentially due to the WPML Media Plugin. Solution: We recommend creating a new staging site and performing the following steps: 1) Navigate to WPML >> Settings >> Media Translation. 2) Click on the Start button and wait for the process to complete. 3) Go to WPML >> Support page, and click on the Troubleshooting link. 4) On the Troubleshooting page, click on the following options in the Clean up section, waiting for confirmation after each:
Problem: If you're experiencing redirect errors in Google Search Console for translated URLs on your site, where the URLs include a language slug but redirect to an original page, this might be due to the content being recently translated. Solution: We recommend checking if you're using the fallback method where WPML displays the original content in secondary languages when the content is not yet translated. This could result in the slug not being translated. For more information, please refer to our documentation on Displaying Untranslated Content on Pages in Secondary Languages.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
Problem: The client was unable to filter out products from a specific category on the front page using WPML for their multilingual WooCommerce site. The provided code snippet worked in the default language (Czech) but not in the translated language (English). Solution: We pointed out that the English category had only one product translated, and for the filter to take effect in the second language, the client needed to translate the rest of the products. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client was experiencing a fatal error when trying to install WPML String Translation on their WordPress site. The error message indicated an undefined method call to
WP_Textdomain_Registry::reset()
.
Solution: We recommended that the client should upgrade the WPML String Translation plugin to version 3.2.3 or greater, as this version is required for WordPress version 6.1 or higher. Before upgrading, it is crucial to perform a full site backup. After the backup, the client should update the plugin and check if the issue persists. For more details on the upgrade process and the importance of compatibility with WordPress 6.1, the client can refer to our documentation:
Problem: You are trying to translate the messages and preview in Everest Forms on your website, but they do not appear in the items to translate. Solution: We recommend navigating to WPML => String Translation. Once there, search for the text that is missing translation, such as "Last Name". If you find the string that belongs to Everest Forms, ensure you translate it. If you are unable to locate the missing strings in String Translation, or if this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: The client is using WPML with WooCommerce, a filter products plugin (WBW), and Divi to create a catalog of dogs for adoption. After installing the WooCommerce WPML plugin, the client translated the content but then realized the WBW filter plugin was not compatible with the translated versions. The client wants to revert the shop page to English only, as the filter does not work on the translated page, and has already deleted the Spanish version of the shop page and the WooCommerce WPML plugin.
Solution: We recommended the following steps: 1. Navigate to WPML > Translation Management. 2. Check the box on the left for the "Shop" page. 3. Scroll down and select "Duplicate". 4. Duplicate the content from the default language to the other one. This process does not translate the content but copies it from the default language, which could resolve the issue with the filter plugin.
If this solution does not seem relevant or does not resolve the issue, we encourage the client to open a new support ticket for further assistance. They can do so by visiting the WPML support forum.
Problem: The client is unable to download their translation invoices for specific months directly from the WPML website due to a bug that prevents the invoices from being displayed when clicking on the invoice tab. Solution: 1. We asked the client to check their email inbox, as invoices are typically sent out each month. 2. We emailed the requested invoices directly to the client. 3. We requested the client to mark the support ticket as resolved once they have received the invoices.
If this solution doesn't look relevant to your issue, please feel free to open a new support ticket.
Problem: If you're unable to see your contact forms in the backend and cannot edit them, even though they appear on the frontend, and you notice that the language tabs under Contact Form 7 are missing, despite having the Contact Form 7 Multilingual plugin installed. Solution: We recommend you follow the steps provided in the custom search results that address similar issues with Contact Form 7 and WPML. Here is the link to the search results:
Please try these solutions and let us know if your issue is resolved.
If this solution doesn't seem relevant to your situation, we encourage you to open a new support ticket with us for further assistance. You can do so by visiting the WPML Support Forum.
Problem: The client is experiencing a fatal error caused by an undefined function wp_enqueue_block_style() in the WPML plugin's block editor loader file.
Solution: If you're experiencing a similar issue, we recommend the following steps: 1. Create a full backup of your site. 2. Update WordPress to the latest version, currently 6.4.2. 3. Update WPML to the latest version, currently 4.6.9, and check if the issue persists. 4. If the problem continues, perform a compatibility check by: a) Switching to a default WordPress theme, like Twenty Twenty-Three. b) Deactivating all plugins except WPML CMS. c) Reactivating plugins in small groups to identify any conflicts. d) Reverting to your original theme. 5. If the issue is not resolved, provide us with your Debug Information following these steps: a) Navigate to WPML > Support > Debug Information. b) Copy the Debug Information. c) In the 'Additional Data' section of our support forum, expand the 'Debug Info' item and paste the copied information.
Please perform these actions on a staging site to prevent any disruption to your live site. For detailed information on the compatibility issue, you can refer to our errata page here: WPML and WordPress 4.7 Compatibility Issue.
If this solution doesn't seem relevant to your situation, please open a new support ticket in our forum: 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
