Problem: You are experiencing a Taxonomy Translation error on your site despite following the provided steps and synchronizing the Taxonomy Translation as per the instructions in a previous support ticket.
Solution: We suspect that the error might be occurring because previously active languages (English and French) on your site are now deactivated. We recommend trying to remove the content for these deactivated languages. You can do this by navigating to WPML > Languages > Site languages in your WPML dashboard and clicking "Delete content" for each deactivated language.
If this solution does not resolve your issue or seems irrelevant 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 problem persists, please open a new support ticket.
Problem: After updating WPML, you receive a persistent error message stating 'Some taxonomy terms are out of sync between languages', even after clicking 'Update Taxonomy Hierarchy'. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Take a backup of your site's database. 2. Navigate to WPML -> Support -> Troubleshooting. 3. At the bottom of the screen, click the 'Remove all messages and notifications' button. 4. Check if the problem is resolved.
If this solution does not resolve your issue or seems outdated, please 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 the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where certain taxonomies on their WooCommerce multilingual site were forced to be non-translatable, causing an error message. This issue persisted even after disabling all plugins. Solution: We advised the client to perform a minimum environment test correctly by keeping essential WPML plugins active, specifically WPML Multilingual CMS and Strings Translation. The client should deactivate all third-party plugins and monitor when the error message disappears, then report back which plugin was last deactivated. Additionally, it was found that in WPML settings under Taxonomies translation, the settings for 'product_cat' and 'product_tag' needed adjustment.
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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: You are using the Flatsome theme and are unable to translate the "MY ACCOUNT" string on the login page. Solution: The "MY ACCOUNT" string is the title of the My Account page. Since the original language of your site is Portuguese, you should change the title to "Minha Conta". This adjustment should resolve the translation issue.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: If you're using the B2B King plugin with WPML on your website and notice that the Product Information Table, which is metadata on the product page, disappears when the page is translated, this might be due to the settings in WPML. Solution: We recommend setting the B2BKing product meta values to "Copy" in WPML -> Settings -> Custom Fields translations. You can find detailed instructions on how to do this in the B2BKing guide on working with WPML here: https://woocommerce-b2b-plugin.com/docs/translate-b2bking-with-wpml/#3-toc-title. After adjusting these settings, you may need to update the translations to apply the new custom fields option. For more guidance on translating custom fields, please visit our guide here: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 problem persists, please open a new support ticket at our support forum.
Problem: The Blog Main page is not displaying translated post pages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Pages -> All Pages. 2. Edit the blog page. 3. Click on the update button. 4. Update the page's translation.
This approach should ensure that your Blog Main page displays the translated posts correctly. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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.
For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are using the WPML plugin with the Flatsome theme on your WordPress site and are facing issues where translated strings do not appear on the front page. Additionally, after attempting some fixes, the footer string disappeared and cannot be translated. Solution: To resolve the issue of translated strings not appearing on the front page and to recover the missing footer string: 1. Navigate to WPML >> String Translation page. 2. Click on the Translate texts in admin screen link at the bottom of the page. 3. Search for the string and enable its translation. 4. Assign the correct source language and add the translation of that string. 5. Clear the cache to see the updated translation. For further details, you can refer to the WPML documentation on finding strings that don't appear on the string translation page and how to change the source language of strings. For translating footer menus: 1. Go to WPML >> WP Menu Sync page. 2. Select the Spanish footer items and press the Apply changes button. 3. Complete the translation of the footer custom links from WPML >> String Translation page. 4. After completing the translation, go back to WPML >> WP Menu Sync page and press the Sync button. For more details on menu synchronization, refer to translating menus. If these steps do not resolve your issue or if you need further assistance, we 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 problem persists, please open a new support ticket.
Problem: The client wishes to remove the language selector from the admin login page that reappeared after installing WPML, despite previously using a code snippet in their theme-child functions.php to hide it. Solution: If you're experiencing the re-emergence of the language selector on the admin login page after installing WPML, we recommend navigating to WPML > Settings > Login and registration pages. Here, disable the option "Show Language Switcher on login and registration pages" to remove the language switcher.
This solution might be irrelevant if it's 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 open a new support ticket at WPML support forum for further assistance.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
