Problem: The client wants to export all translations to an Excel file and import them once translated. Additionally, the client is experiencing an error 524 due to a timeout when trying to load over 921 translations added to the translation basket, even after increasing the WP memory limit to 400M. Solution: To export translations to an Excel file, we recommend following the instructions provided by our colleague in a related support ticket, which can be found here: https://wpml.org/forums/topic/how-to-generate-a-clean-excel-file-for-external-translator/. Regarding the error 524 and the translation basket issue, we have created a separate ticket to address this problem. You can follow the progress and find the solution here: https://wpml.org/forums/topic/split-how-can-i-reset-translation-basket/. Please mark the current ticket as resolved.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client is working on a custom theme using Advanced Custom Fields (ACF) and has encountered an issue where after entering a password on a password-protected page, it redirects to a 404 page instead of displaying the content. Solution: We recommend navigating to WPML->Settings->Login and registration pages and unchecking the option Allow translating the login and registration pages. This should resolve the issue and allow the password-protected content to display correctly after the password is entered.
If the client wishes to use the option to translate the login and registration pages, we advise reviewing the following documentation, especially since the client is on an NGINX server:
If the provided solution is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. We also highly recommend checking related 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 contact us in the WPML support forum.
Problem: The client is trying to change the slug for products in the French version on their WooCommerce site but the changes are not taking effect. The products in the French version appear to be duplicates of the English version, and there are concerns about SEO optimization and duplicate content.
Solution: 1. Ensure the slug is updated in WooCommerce > WooCommerce Multilingual > Store URLs. After updating, resave the permalinks. 2. If the issue persists, go to WPML > String Translation, search for the original slug, and remove it. Then, try updating the slugs again from WPML > Settings > Post Type Translation > Products. 3. To display only translated products and avoid duplicates, go to WPML > Settings > Post Type Translation, find Products, and set the translation preference to "Translatable - only show translated items". 4. The slug 'acheter' was already in use for product category base translation, causing a conflict. We resolved this by renaming the category base slug to
acheter-1
, which allowed the French product URLs to work correctly. A different slug should be used for the French category base translation.
Problem: The client is having issues with the WPML plugin not automatically loading existing .po/.mo files for plugins such as Events Manager. Additionally, the client is unable to see the country flag options on the Events pages, even after loading strings into the WPML system.
Solution: 1. WPML should automatically load .po/.mo files if they exist for a plugin and are in the correct language. If the translations are not working, the client can regenerate the .mo files through WPML by navigating to WPML -> Support -> Troubleshooting and using the relevant option.
2. Importing .po/.mo files alone will not display flags for Events in other languages. The client needs to translate the Events themselves or use a fallback option for displaying untranslated content in secondary languages, which can be found here: Displaying Untranslated Content on Pages in Secondary Languages.
If the provided solution does not apply or is outdated, or if the issue persists, we recommend opening a new support ticket. We also 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.
Problem: The client needed to translate the "I've read and agree to the terms & conditions" acceptance text on the WooCommerce checkout page but was unable to find the correct string to translate. Solution: We recommended several steps to locate and translate the string: 1. Search for the string in WPML > String Translation. Helpful documentation on using the String Translation plugin can be found here: String Translation documentation. 2. If the string is not found, scan the theme or plugin generating the string for translations, as explained here: Theme Localization documentation. 3. Check if the string is an admin text and follow the process for finding and translating admin text strings: Finding and translating admin text strings. 4. Enable the "Look for strings while pages are rendered" option at the bottom of the WPML > String Translation page, visit the front end where the string appears, and then search for it again in String Translation. 5. If the string is hard-coded in the theme files, refer to this guide for translating: Translating hard-coded theme strings.
If these steps do not resolve the issue or if the solution is outdated or not applicable to your case, we encourage you to open a new support ticket. We also 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. For further assistance, please contact us on the WPML support forum.
Problem: If you're experiencing issues where changes made in Elementor are not appearing in the WPML advanced translator, it might be because the updated content needs to be re-sent for translation. Solution: To resolve this, we recommend the following steps: 1. Update the content in the default language. 2. Go to WPML > Translation Management. 3. Find the page or post in the default language and check the box next to it. 4. At the bottom of the page, select "Translate" for the language you want to re-send it for translation. For other languages, select "do nothing". For more detailed instructions, please refer to our documentation on translating pages, posts, and custom post types.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problem:
Elementor elements (buttons and certain text sections) keep changing back to the original language (english) whenever I update the translations using the WPML editor.
Solution:
1. I edited the page using the elementor page editor and unlink the global widget.
2. Then, I create a new "Global Widget" from the widget that I just unlinked.
3. Translated the new "Global Widget" to different languages.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue with incorrect links on their multilingual WooCommerce site, where the expected product URL was redirecting to a different category URL.
Solution: We recommended the client to: 1. Navigate to WPML-> Support-> Troubleshooting. 2. Run the troubleshooting functions one by one. 3. Go to WooCommerce Multilingual-> Attribute tab. 4. Select the size attribute and click on the Synchronize button. 5. If the issue persists, go to WooCommerce Multilingual-> Status tab and select Troubleshooting. 6. Select all options except the last one and click on the Start button. 7. Clear the site's cache.
Additionally, we noticed that the WordPress memory limit was lower than the minimum requirements for WPML. We advised the client to increase the memory limit by adding the following code to the top of their wp-config.php file:
If the solution provided is not relevant 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 issue persists, please do not hesitate to open a new support ticket at our support forum.
Also, take a look at the WPML Hooks Reference for additional hooks and examples that might be helpful, especially the
wpml_get_element_translations
hook.
If these suggestions do not resolve your issue, and you're not comfortable with custom coding, you might want to consider hiring a developer. You can find qualified contractors at https://wpml.org/contractors/.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please don't hesitate to open a new support ticket with us.
Problem: The Client is translating your site from Dutch to English, but some pages and posts are not automatically translated and display an eye icon indicating the English language assessment. Solution: If you're experiencing this issue, we recommend you follow these troubleshooting steps after ensuring you have a full site backup: 1) Navigate to WPML>>Support page, and click on the Troubleshooting link. 2) On the Troubleshooting page, click on the following options in the *Clean up* section and wait for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables 3) Go to WPML>>Translation Management Dashboard. 4) Select the Post/Page you have issues with. 5) Send it to the Translation Basket. 6) Visit WPML>>Translations queue and click the *Translate* button to translate the page.
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 following error appears after activating WPML:
PHP Fatal error: Uncaught InvalidArgumentException: element_id and type do not match in \wp-content\plugins\sitepress-multilingual-cms\classes\core-abstract-classes\class-wpml-set-language.php on line xx
Solution:
This kind of error probably happens because of corrupt entry or misconfiguration in the Database. Please try the following steps after creating a full database and website backup:
1- Open your database using phpMyAdmin(or another database manager)
2- Go to the wp_icl_translations table
3- Find the entry with element_id: XXX (The ID number you see in the error)
4- Delete that row
Problem:
When a member tries to login, they see the following fatal error:
Fatal error: Uncaught TypeError: Argument 2 passed to WPML_User_Language::update_user_lang_from_login() must be an instance of WP_User, string given, called in ********/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php on line 15
Solution:
It looks like a compatibility issue with the member login plugin, the member login widget is most probably calling the wp_login hook: https://developer.wordpress.org/reference/hooks/wp_login/
But it's not passing a WP_User instance as a second parameter.
Please note that the "Membee Login" plugin is not listed on the WPML compatibility list for the plugins - https://wpml.org/plugin/. This means that our compatibility team has not tested it.
So we suggest contacting the plugin author and sharing the issue with them, probably they can provide a quick fix.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
