Problem: The client is using Elementor and Custom Permalinks plugins and is encountering issues with translating URLs. Some pages display the original URL in the Dutch language instead of the translated version, and there are no fields to add link translation. Updating Elementor templates causes the links to revert to Dutch.
Solution: 1. We recommend changing the slug of the problematic page or registering the buttons as a workaround. 2. Use the "Yoast Duplicate Page" plugin to duplicate the page. After duplicating, change the slug of the existing page to include '-old' and let the new cloned page have the current slug. This should allow the URL to work correctly after translation. 3. If the issue is related to an image name that matches the page URL, change the slug using "Quick edit" and update the image title to ensure it has a different URL.
Problem: The client was experiencing an issue where translated taxonomy slugs for a WooCommerce taxonomy were not being updated on the frontend. For example, the slug 'a-b-c' was changed to 'a-b', but the link on a product page still showed 'a-b-c', even though the correct URL should be 'a-b'. The client had already cleared the WPML cache, saved permalinks, and cleared all other caches, but the issue persisted. Solution: We recommend checking for any third-party plugins that might affect the behavior of the translated links, as they can sometimes cause unexpected issues. Additionally, try translating the taxonomy using the native WordPress screen by navigating to Product → Categories. It is also advisable to update the WPML plugin to the latest version, currently 4.6.8, along with any add-ons, to take advantage of the latest bug fixes and improvements. You can find the latest releases under My Account -> Downloads on our site. Follow the provided instructions to update your WPML installation. Please ensure you back up your database before proceeding with the update.
If this solution does not seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: There is an issue with the String Translation table on the client's site, which could potentially become a critical issue in the future. Solution: If you're experiencing a similar issue, we recommend checking if this is the first time WPML has been installed on the website and if there are any existing translations. It's important to determine if resetting WPML is safe for your specific case. Before proceeding with any changes, ensure to create a backup of your database. If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll assist you further.
Problem: If you're experiencing issues with 'Variation Swatches for WooCommerce' by CartFlows and 'Variation Images Gallery for WooCommerce' by RadiusTheme not working in your English translations, despite following our guide and inserting the code.
Solution: Firstly, ensure you have a backup of your site. Then, for the product gallery media issue: 1. Navigate to WPML > Settings. 2. Scroll to 'Custom Fields Translation' and click on 'show System fields'. 3. Locate the required fields and set their translation settings to 'Copy'. 4. Save the changes. 5. Edit the product, select the option to copy media to translations, and resend the product for translation. 6. If this resolves the issue for one product, you can apply the same settings to all products using the option under WPML settings.
We were able to resolve the swatches issue by: 1. Changing WPML custom fields configuration to 'Copy'. 2. Switching the translation editor to the Advanced Translation Editor. 3. Retranslating the product. 4. Clearing both Object cache and WP Rocket cache.
To apply these changes to the rest of your products, resend all products for translation and clear your cache.
Problem: The client needs to enable a language selector in the Salient theme using WPML. Solution: We recommend following the steps in our documentation to add the language switcher. Here is the step-by-step guide: 1. Visit the WPML documentation on language switcher options: Language Switcher Options documentation. 2. Follow the instructions provided in the guide to add the language switcher to your site. 3. If you have already tried these steps and it did not work, please let us know for further assistance.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client's site language is set to Japanese, but when installing a new plugin, it defaults to English. Solution: We recommend checking and setting the user profile language to Japanese by navigating to Users > Profile and selecting Japanese for the Language field. Remember to save the changes. Afterwards, clear your site's caches to see if the issue persists.
Additionally, follow these steps after ensuring you have a full site backup: 1) Update WPML to the latest version, which is 4.6.8. 2) Increase the WP Memory Limit to at least 256 MB, as the minimum required memory limit for WPML is 128 MB. For more details, please refer to the following documentation:
Problem: The client needed to translate a link on a button to English, but encountered a message indicating that the string could not be translated automatically because it was not in the site's default language. Solution: We recommended the following steps: 1. Go to WPML String translations and scroll to the bottom, then click on "Translate texts in admin screens »". 2. Search for the ID of the theme option button URL, which in this case is
"btn_link_v1"
. 3. Click on "Add to String Translation" button to add it to the string translation list. 4. Return to WPML String Translation and switch the default language as previously indicated. For more detailed instructions, please refer to our documentation on Finding strings that don’t appear on the String Translation page. We have added the string for the client, and the website should now display the translation correctly.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client wants to delete the WPML plugin but keep the translated pages, as the website is not very active and seldom has new content. Solution: We recommend against deleting WPML if you want to keep your translations. Instead, you can: 1. Deactivate WPML to ensure it doesn't consume any resources from your website. 2. Create a backup of your website, delete WPML, reinstall it, and check if the translations are still there. Additionally, we provided links to resources that might be helpful:
For a complete reset of WPML, you can refer to our documentation: WPML Reset Documentation Always ensure to have a full website backup before making any changes to avoid accidental data loss.
Problem: The client manually translated English menus into traditional Chinese and is seeking guidance on how to proceed with WP Menu Sync, especially for menus that are not fully translated or have content available only in certain languages. The client also encountered issues with deleting menus and synchronizing them across different languages.
Problem: The client has a WordPress site with English as the default language and has set up both English and Spanish languages. They encounter an issue where, after changing the dashboard language to Spanish and updating an order status in WooCommerce, the email notification is still sent in English, even though it works correctly when ordering from the website frontend.
Solution: We explained that the notification email sent to the admin is always in the site's default language, as set in WPML > Languages. To receive the notification email in Spanish, the client should change the language of their profile by navigating to
Users > Profile
and adjusting the language settings there. Additionally, we provided a hook that can be used to receive emails in the language set for the client's profile:
Problem: I have some issues with "translate everything" mode because my site has over 4000 jobs to translate.
Solution: The resources on your site are important here. however all you need is time and it depends on your server resources. if you see that the number of translations is not decreasing even after 1h, please flush your server-side cache and try again. if the problem remains, then feel free to open a support ticket.
Problem: The client is unable to find the WPForm option in the Translation Management dropdown menu to translate a "contact" form Solution: We recommend ensuring that the WPML String Translation and WPForms Multilingual plugin is installed and activated on the site. For detailed instructions, please refer to our documentation at https://wpml.org/documentation/related-projects/creating-multilingual-forms-using-wpforms-and-wpml/. If the problem continues, we suggest re-saving the WPForms plugin form to refresh the settings.
Problem: If you're trying to remove connected translations by selecting "None" in the "This is a translation of" dropdown menu, but the changes are not saving and it reverts back to the original post upon saving. Solution:This issue has been solved in WPML v4.6.8 as mentioned here: https://wpml.org/errata/wpml-4-6-7-issue-with-disconnecting-translations/ so please update WPML plugins to the latest version.
Problem: The client is facing two issues after upgrading their WPML account to use the WPML String Translation plugin. First, some pages like the dashboard or login/register form are not being translated into Persian, despite being automatically generated. Second, the automatic translation function in the WPML String Translation plugin is not working for about 6000 strings on the website. Solution: We recommend increasing the WordPress memory limit to ensure that WPML operates smoothly. WPML requires a minimum memory limit of 128 MB, and we recommend setting it to 256 MB. To do this, add the following lines to your
wp-config.php
file:
define('WP_MEMORY_LIMIT', '128M');
define('WP_MAX_MEMORY_LIMIT', '256M');
For more details on how to increase the memory allocated to PHP, please visit the following documentation: Editing wp-config.php If increasing the memory limit does not resolve the issue, please provide us with screenshots and examples of the problems so that we can assist you further.
If this solution doesn't look relevant, please open a new support ticket in our 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
