Problem: The client has a multilingual WooCommerce shop and is facing an issue where the shop page slug is not correctly translated. The default language shop page slug is "/all-products/", but in English, it incorrectly shows as "/en/alle-producten/" instead of "/en/all-products/". The client has tried to translate the page and set a different slug, but the translated page remains empty, while the incorrect slug still works. The client also noticed that setting a different shop page per language is not possible.
Solution: We recommend ensuring that the Shop page is translated and published in all languages. To handle the slug translations, the client should edit the pages directly. Additionally, there are options to translate slugs related to WooCommerce under the 'Store URLs' tab in WooCommerce -> WooCommerce Multilingual & Multicurrency. We also advise following the steps in our guide to install and set up the WooCommerce Multilingual & Multicurrency plugin:
Problem: The client is experiencing an issue where the menu disappears when switching languages, showing only the home button after installing WPML and translating some pages. Solution: 1. We recommend translating the menu items following the steps in our guide on Translating Menus. After completing the menu translations, the issue should be resolved. 2. We also advise increasing the WordPress memory limit to at least 128MB. This can be done by adding the following code to the
Place this code above the line that says /* That's all, stop editing! Happy blogging. */. You can verify the updated memory limit in the WPML -> Support section.
Problem: The client wants to duplicate content and manually translate it without being redirected to the Advanced Translation Editor (ATE) page. Solution: If you're experiencing issues with duplicating content and want to manually translate it, we recommend you follow these steps: 1. Duplicate the content by following the instructions in our documentation on Displaying Untranslated Content on Pages in Secondary Languages. 2. After duplicating the content, you can edit it using the WordPress native editor by: - Editing the post/page in the default language. - Going to the Languages tab. - Activating the 'WordPress Editor' option. - A popup window will appear where you must select the scope of the change. - Saving the changes. - You can now edit the duplicated post/page using the WordPress Editor.
When that did not resolve the issue, we suggested the following steps: 1. Create a full backup of the site. 2. Update all outdated plugins. 3. Update the WPML plugins. 4. Flush the cache memory. 5. Edit the post in the original language and make a small change to the content. 6. Save the changes and update the translation. 7. Double-check if the issue disappeared.
After these steps did not fully resolve the problem, we advised running a scan for internal links again. We then converted the chat into a forum ticket for further assistance and potential escalation to our second-tier support.
Additionally, we updated the XML configuration for the custom fields to ensure the correct field names were targeted:
We instructed the client to edit the content in the original language again, make a small change, update the translation, and then check if the links in that field were updated.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an Internal Server Error on their multilingual WordPress site when clicking any menu items, with logs indicating excessive internal redirects.
AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer:...
Solution: We recommend checking the .htaccess file to ensure it follows the default WordPress configuration. If necessary, delete the .htaccess file, save the permalinks to generate a new .htaccess file, and then add the workaround provided in our documentation to the theme's functions.php file.
Here are the steps to follow: 1. Verify the .htaccess file against the default WordPress configuration found here: WordPress .htaccess documentation. 2. If the .htaccess file is incorrect, delete it and save the permalinks in WordPress to create a new one. 3. Add the workaround from our errata page to your theme's functions.php file: WPML .htaccess workaround.
Additionally, increase the WP Memory Limit by adding the following code to your wp-config.php file:
Problem: The client was experiencing issues with a translated menu disappearing after a minor change and encountering problems with non-translated items after using the "Sync menus" function. Despite deleting the menu and clearing caches, the deleted menu continued to appear on the site.
Solution: 1. We confirmed that only one English menu was present and suggested creating a new specific menu for the English language. 2. We recommended assigning the new English menu as a translation of the original Swedish menu, ensuring that all menu items are correctly translated and ordered. 3. If the client continues to experience issues with the menu disappearing or non-translated items appearing after these steps, we advised opening a new support ticket for further assistance.
If this solution doesn't look relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client was unable to see translated products because they were saved as drafts and encountered a critical error when trying to access Appearance > Themes with WPML active, due to WPML attempting to read MO files from an invalidly named theme. Solution: We recommend the following steps to resolve the issue: 1. Rename the theme folder with the invalid name (e.g., 'bluehost-mila-tak%c4%b1') to a valid one, such as 'bluehost-mila-tak'. 2. Update the 'text-domain' in the style.css file. To do this, navigate to Appearance > Theme File Editor and edit the 'Text Domain:' field to match the new folder name, 'bluehost-mila-tak'.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client was unable to access the English translation of a blog page, which was previously available. The menu item linking to the page was missing, and the page was not listed in the page overview. Solution: We found that the translation was created as a draft and had been moved to the trash. We restored the page and then published it. If you encounter a similar issue, please make sure that the translation is not created as a draft or added to trash. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client was alerted by Wordfence about potential vulnerabilities for two WPML add-ons: WPML Sticky Links and WPML CMS Navigation. The concern was due to the plugins being flagged as outdated or abandoned. Solution: We confirmed that the client is using the latest versions of both plugins, which are secure and regularly reviewed for security and compatibility. We reassured the client that these plugins are part of our active suite and receive updates as needed. We advised the client to: 1. Mark the issues as fixed in WordFence to remove the warnings. 2. Check the changelogs for the latest updates: - WPML Sticky Links Changelog - WPML CMS Navigation Changelog 3. Visit our downloads page for more information: WPML Downloads We also informed the client that if they encounter any further issues or if this solution is not relevant, they should feel free to open a new support ticket in our forum: WPML Support Forum
Problem: The client is experiencing an issue where the URL argument (ID=) disappears when switching languages using the WPML language switcher on their development site. Solution: We recommend using the option to preserve URL arguments when switching languages. This can be done by following the instructions provided in our documentation. Here is the link to the relevant guide:
Problem: The client was experiencing an issue with the WPML registration on their website. After deleting a development site, the original site still displayed a WPML bar in the footer indicating that it was registered as a development site. Solution:
- Deleted the sitekey and register a new one.
- Purged all caches
If this solution doesn't look relevant or if the problem persists, please open a new support ticket with us.
Problem: If you're experiencing issues with translating text within Gutenberg blocks from Rehub theme like titlebox, review box you need to add custom XML configuration for them. Solution: We recommend adding specific XML configuration to your WPML settings. Here's a step-by-step guide: 1. Navigate to WPML > Settings > XML Configuration. 2. Add the following XML code:
3. After adding the code, make a small change to the default language and re-translate the content. Additionally, you may want to inform the theme author about this issue so they can include a fix in their theme updates.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: After migrating the client's website from a temporary URL back to the original URL, a persistent message from WPML is displayed indicating that the site address has changed. Solution: If you're experiencing a persistent message from WPML after migrating your site, here's what we recommend you try: 1. If you plan to use the same translation memory and credits on both your production and development sites, select "No, I changed the address of the site...". 2. If the temporary URL was only for a development copy, choose "Yes, this is only a copy...". For more detailed information, please refer to our documentation on Using Advanced Translation Editor when you move or use a copy of your site.
Problem: My links, translated in the advanced translation editors are reverting to the original ones and losing its translations.
Solution: This problem has been solved already, you don't have to do anything more than re-send your page to translate via WPML > Translation Management
Problem: WordFence is reporting some WPML plugins as abandoned.
Solution: If you're experiencing false notices from WordFence about WPML plugins being abandoned, we recommend you to ignore these notices and continue using the plugins.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
