Problem: The client is experiencing issues with missing 'edit translation' options on some pages, which prevents linking translations between languages and forces manual content translation, losing the connection with the original translation. Solution: 1. We recommend editing the page in the default language. 2. In the sidebar, look for the option to change to "WPML Translation Editor" and click on it. 3. In the popup that appears, select "All pages" to revert all pages to the Advanced Translation Editor (ATE). 4. Remember that once a page is translated via ATE, it's better not to edit the translation directly. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
Problem:
The Enfold theme language switcher was moving to the new line on mobile devices.
Solution:
I have followed the below steps in order to fix this issue:
1. Added WPML Language Switcher from WPML >> Languages > Menu Language Switcher.
2. Disabled the existing Enfold theme language switcher by following the below steps:
- Went to Enfold >> Theme Options page.
- Clicked on Header >> Extra elements tab.
- Set the Enfold WPML Language Flags option to Hide the default language flags by pressing the save button.
Problem: The client's orders page was showing a 'not found' error after translating the site. The issue persisted until the 'WPML String Translation' plugin was deactivated, indicating that the problem was related to a translation.
Solution:We found that some Dokan options were unnecessarily translated using the String Translation feature, leading to the error. To resolve this: 1. Navigate to the String Translation section. 2. Locate the Dokan admin texts that have been translated. 3. Select these strings and delete them. This solution worked on our copy of the client's site; if you face a similar issue, try checking for Dokan option texts that have translations which are not necessary.
Problem: The client is unable to install and activate the WPML plugin due to a directory creation error and a file copy issue.
Solution: We recommend manually installing the WPML plugin by following these steps: 1. Download the WPML plugin from our downloads page. 2. Navigate to your website's backend > Plugins > Add New > Upload Plugin, then upload the zip file, install, and activate WPML.
If the above does not work, use cPanel's "File Manager" to: 1. Navigate to the /public_html directory > wp-content > plugins. 2. Upload the zip file downloaded from our site. 3. Extract the zip file in the /plugins directory, which will create a new folder called "sitepress-multilingual-cms". 4. Go to your site's backend > Plugins, where you should see the WPML plugin and be able to activate it. 5. After confirming the plugin is present, delete the .zip file from your hosting via cPanel.
If these steps do not resolve the issue, please open a new support ticket so we can investigate further.
Problem: If you're experiencing an issue where clicking on translated products redirects you to the homepage instead of opening the products, and this only occurs with products in the translated language, not the original language. Solution: We recommend trying one of the following solutions: 1. Change the translated "Product base" slug from "online-shop" to "online-store" in WooCommerce. You can do this by navigating to WooCommerce > WooCommerce Multilingual & Multicurrency > Store URLs. 2. Disable the "Remove base" option in Rank Math SEO. Go to Rank Math SEO > General Settings > Woocommerce. We have already changed the product base slug to "online-store" for you, and it should now be working correctly. Please be aware that there are known issues with the Rank Math SEO plugin, which our developers are actively working to resolve. You can find more information on these issues here:
Problem: The client needs to rename taxonomies to French on a website where the default language is French, but the taxonomies were created in English.
Solution: We recommend navigating to the WordPress taxonomy screen and renaming the taxonomies directly from there. This action should be performed in the default language of the site, which in this case is French.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: If you're entering your key on the site and receiving the message "Unable to parse data from service response," we can assist you. Solution: We recommend whitelisting the following domains with the assistance of your hosting provider:
Problem:
The client was trying to activate the OTGS installer plugin to upgrade the WPML plugins.
Solution:
The OTGS installer plugin is only necessary when installing the WPML Multilingual CMS plugin. Once you've activated WPML Multilingual CMS, there's no need to activate the OTGS installer plugin since it provides the same functionality.
If you've registered WPML on your site, you can update it by going to the Plugins >> Add New page, clicking the Commercial tab, and then hitting the “Check for updates” button.
Problem: The client is experiencing an issue where a required table in the database, specifically 'wp6f_icl_strings', is missing, which is causing an error. Solution: If you're encountering a similar problem with missing database tables, we recommend following the steps outlined in our documentation on how to deal with error messages about a broken table that needs fixing. You can find the instructions here: https://wpml.org/faq/how-to-deal-with-error-messages-about-a-broken-table-that-needs-fixing/#problem-with-some-tables-in-the-database. This guide should help you resolve the issue. If this solution doesn't seem relevant or if you need further assistance, please don't hesitate to open a new support ticket in our support forum.
Problem: The client is trying to get the product attribute filter to appear on category pages for translated languages in WooCommerce, but the attribute fields are not showing up. Solution: 1. We have spotted the client had set the Product Brand (pa_brand) as 'Translatable - use translation if available or fallback to default language' in WPML -> Settings -> Post Types Translation. 2. We noticed that the Brand terms in Chinese had no products assigned, which is a common issue when products and categories are set as 'Appear as translated' and only part of the content is translated. 3. We recommended using the 'duplicate' feature instead of the 'fallback' option. Detailed steps can be found here: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/#duplicating-content. 4. We duplicated one product of the Brand 'Lee Kum Kee' to Chinese and turned off the option "Use the product attributes lookup table for catalog filtering" in WooCommerce -> Settings -> Products -> Advanced. 5. Finally, we suggested translating the widget texts through WPML -> String Translation module, which may require deleting and recreating the previous strings and widgets.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
Problem: The client needs to display all posts in all languages on a listing or social media website with frontend submission, without translating them. The issue is that the Translation Management (TM) only allows duplicating content from the site's default language, and not in bulk for content created in other languages. Solution: We regret to inform you that we do not plan to implement a feature for duplicating original content not created in the site's default language in bulk. However, we offer a hook that can be used on the Frontend to create duplicates in WPML when a post is published, regardless of the post's default language. You can find more information about this hook here:
Problem: The client is experiencing an issue with missing information in the product view, which seems to be related to a translation problem. The error message indicates an 'Invalid taxonomy' when trying to retrieve terms using custom code.
Solution: We have identified that the issue is with custom code attempting to access a taxonomy with an incorrect slug. The correct code should use the taxonomy slug 'gebinde_de' instead of 'gebinde'. Here are the steps to correct the issue:
on lines 322-323 with the correct taxonomy slug. If the client's developer is unable to resolve the issue, we suggest contacting one of our certified partners for further assistance.
Problem: The client needed assistance with connecting and changing an old WPML license to a new one, as they could not access the old account and had to purchase a new license. Solution: 1. Log in to the "new" WPML account. 2. Navigate to Account -> Sites (https://wpml.org/account/sites/). 3. Register the site and copy the site key. 4. Access the site's dashboard, go to Plugins -> Add New -> Commercial tab. 5. Unregister WPML from the site and then register it again using the new site key.
If this solution does not seem relevant, 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
