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
1
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:
1
PHP Fatal error: Uncaught InvalidArgumentException: element_id andtype donot 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:
1
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.
Problem: The client is experiencing an issue where the One Click Accessibility plugin works fine in the translated language (Greek), but does not show the original English text when viewing the site in English.
Solution: We recommend translating the remaining strings using WPML's String Translation feature. We have already translated some strings for the client, which resolved the issue for those particular strings. The client should follow these steps to translate the rest: 1. Go to WPML -> String Translation. 2. Find the strings related to the One Click Accessibility plugin. 3. Translate the strings into English.
If the solution provided here does not apply to your case, or if it seems outdated, we encourage you to check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you still encounter issues, please do not hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client is using WooCommerce Checkout Manager with WPML and is unable to translate the values of a conditional dropdown list from English to Arabic. The strings are still showing in English despite trying solutions from the WPML forum. Solution: First, we asked the client if they had tried two specific methods for finding and translating strings that do not appear on the String Translation page: 1) Finding strings that aren’t selected for translation 2) Auto-register strings for translation We then inquired if the client found the string in WPML > String Translation after trying these methods.
Next, we provided a Custom XML Configuration code to add in WPML > Settings if the fields were added in the "shipping", "Billing", or "Additional" sections:
However, we noted that this might not be necessary as we tested the method linked above and confirmed that the dropdown was correctly translated on our test site. We suggested that if the problem persists, the client should switch their theme to Storefront or TwentyTwentyone to see if the issue resolves.
If the provided solution is outdated or not applicable to the client's case, we recommend opening a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
Problem: The client reported a performance issue with their multilingual webshop when logged in as an admin. The webshop, which has over 50,000 products and 15,000 categories, was experiencing a significant number of SQL queries on every page load due to the function
1
maybe_populate_cache
in
1
class-wpml-element-translation.php
. This issue was not present when not logged in as admin. Solution: We recommended the client to modify the Sharespine WooCommerce Connector plugin. Specifically, to edit the
Additionally, we suggested that the Sharespine plugin developers join our Go-Global Program by filling out the form provided, to ensure better compatibility and support for multilingual sites.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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.
The hook you are using (wpml_get_translated_slug) is intended to get the post-type slug translation in a specific language. But you are misusing it. You are trying to get the slug of a particular page of WordPress. A regular WordPress page doesn't have this "slug prefix" type. Its permalink consists only of the page slug itself.
Let's, for example, take a custom post type with the name of 'book'. In this case, the following will consist of the permalink.
post type slug = book
post slug = my-book
permalink = /book/my-book/
The wpml_get_translated_slug hook filters the /book/ part. WordPress's pages do not have this part. Relevant Documentation:
Problem: The client was unable to configure WPML plugins after an update and received the error message 'Sorry, you are not allowed to access this page'. Additionally, the 'WPML Multilingual CMS' & 'WPML String Translation' options were missing from the dashboard menu. Solution: We recommended adding the following code to the active theme's functions.php file:
After adding the code, the client should open a page in the back and/or front-end, then remove the code to see if the issue is resolved.
If this solution does not apply or is outdated, or if the problem persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket in the WPML support forum.
Problem: The client was unable to translate the custom logo in their child theme of GeneratePress, despite adding the post ID of the media they wanted in the translation. The original logo was still displaying in both the default and translated versions. Solution: We asked the client for the file name of the translated logo and requested temporary access to their site for further investigation. Upon reviewing the WPML String Translation settings, we discovered two records for the media ID "11427" (the Swedish logo). Only one of these records was added to WPML String Translation. We added the correct record to String Translation, translated it, and confirmed that the logo now displays correctly on the translated page, as seen here: https://staging.ways.se/en/clients/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at 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
