Problem: The client was experiencing issues with the WPML plugin on their website. The automatic translation feature was not working, leaving most of the website untranslated. They were unable to initiate the translation process manually or automatically. Additionally, there were problems with menu item translations and missing buttons in the header on translated pages.
Solution: Firstly, we resolved the issue with the automatic translation not appearing by: 1. Completing the Translation review. Guide to review automatic translations 2. Making a small change in the default page and saving it to trigger an update in the translation. 3. Completing the translation review again. If the client encounters similar issues on other pages, we recommend following the steps above and checking the guide: Why aren't my translations showing?
For untranslated menu items, we advised manually translating them and provided a guide for translating menus: Translating menus.
To fix the issue with the 'Colors' Menu on the Single Product Page, we regenerated the translation files for the theme.
For links in translated pages that were defaulting to the default language, we suggested checking the translation of the corresponding page or post and using relative URLs.
Regarding the menu synchronization issue, we increased the 'max_input_vars' setting to at least 2500 and the 'max_execution_time' to 600 to successfully complete the process. We provided a guide on how to increase 'max_input_vars': Increasing max_input_vars and a tutorial for increasing 'max_execution_time': Increasing max_execution_time.
For the missing buttons in the header, we instructed the client to add button links through custom fields in the 'Website > Header' section for each language.
If this solution doesn't look relevant, please open a new support ticket at the WPML support forum.
Problem: The client has a custom user role on their site and needs this role to be able to edit all translations. They encountered an issue where the custom role could edit some but not all translations, and assigning the role of translator and translation manager did not resolve the issue. Solution: 1. We recommended checking the workaround provided in our documentation: WPML custom role based on the editor role cannot edit translations and behave as editor. 2. We also informed the client that WPML 4.6.9 has been released, which includes a fix for this issue. We advised updating WPML to the new version to resolve the problem.
Problem: The client has a custom user role on their site and needs this role to be able to edit all translations. They encountered an issue where the custom role could edit some but not all translations, and assigning the role of translator and translation manager did not resolve the issue. Solution: 1. We recommended checking the workaround provided in our documentation: WPML custom role based on the editor role cannot edit translations and behave as editor. 2. We also informed the client that WPML 4.6.9 has been released, which includes a fix for this issue. We advised updating WPML to the new version to resolve the problem.
Problem: If you're experiencing an issue where the title of an accordion made with the 'Accordion Toggle' plugin is not being translated on your product pages, even though it appears translated in the translation editor, we can help. Solution: To resolve this, you need to register the block for translation: 1. Navigate to WPML-> Settings-> Custom XML Configuration. 2. Insert the following code:
3. Click 'Save'. 4. Edit the page in the default language. 5. Make a minor edit and then update it. 6. Update the translation. After following these steps, check your translated product page to see if the title is now correctly translated. For more detailed guidance, please refer to our documentation on making custom Gutenberg blocks translatable.
Problem: The client is experiencing an issue where the "Add to Cart" button is not appearing on product pages when the website's language is set to Chinese, despite working correctly in English. Solution: We found that the issue was caused by the "Show only products with custom prices in secondary currencies" option being enabled. To resolve this: 1. Disable the "Show only products with custom prices in secondary currencies" option. 2. Clear the site cache. After these steps, the "Add to Cart" button should appear correctly on the Chinese product pages. We ask the client to check if the button now works as expected. 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 French and Italian language options in the dropdown of the WPML language switcher widget. Solution: We recommend ensuring that the pages have been translated into the respective languages and that the status of these translated pages is set to 'Published' rather than 'Draft'. Specifically, the site's homepage needs to be translated as it currently isn't, which is likely causing the issue with the language options not displaying. For detailed guidance on translating pages using Elementor with WPML, please refer to the following documentation:
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
