Problem: The client is unsure if their website is properly connected to WPML, where to find a counter for the words used or available, and whether WPML creates a sitemap for the second language. Solution: We recommend checking if there are any notifications about WPML not being able to connect to wpml.org on your website. If there are no such notifications, your site is properly connected. The WPML site page on your wpml.org account is not updated in real time, so it is normal not to see immediate changes there.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.
Problem: You are experiencing issues with translated portfolio pages on your website, where photos disappear, and the arrangement shows incorrect language text. This problem started after recent edits to the portfolios. Solution: We recommend adding a custom XML configuration to your WPML settings to ensure that all necessary attributes are correctly translated. Here is the XML code you should add:
This configuration should help in translating the subtitle and other text elements correctly. If this solution does not resolve your issue or 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client reported that certain information was not appearing in the translation section even after duplicating the content. Solution: We enabled the translation for the page options. We recommend you check if these strings now appear for translation in your WPML interface. If you're experiencing this issue, we suggest verifying that the translation options for page elements are correctly enabled.
Please note that this solution might be outdated or not applicable to your specific 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 plugins, all pages except the home page on the client's site are showing 404 errors. Solution: If you're experiencing 404 errors on your site after updating WPML plugins, we recommend checking and updating your permalink settings. This can often resolve issues where pages fail to load correctly after updates. To update your permalinks, navigate to the WordPress dashboard, go to Settings > Permalinks, and simply click 'Save Changes' without altering anything. This action can help refresh the permalink structure and potentially fix the 404 errors.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your specific 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. Additionally, if the problem persists, please open a new support ticket with us for further assistance at WPML support forum.
Problem: If you're experiencing issues with the translation page not loading after adding custom languages, and encountering errors related to languages mapped to English, this might be due to a known issue in our code. Solution: We recommend implementing a temporary workaround until the permanent fix is available in WPML 4.8. You can find the workaround details here: Custom Database Prefix and Having 30+ Languages Can Cause a Database Error When Visiting Translation Dashboard.
This issue may arise particularly if you are using a custom prefix for your database tables, similar to our local environment setup.
Please try this solution and let us know how it goes. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific 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.
Problem: The client was experiencing issues with translated parent/hub pages in Thai, which after some time, would automatically redirect back to the default English version. This redirection was inconsistent, with some pages functioning correctly while others reverted to English. Solution: 1. We recommended disabling all other plugins and switching to the default WordPress theme to check if the issue still occurred. 2. If the problem persisted, we suggested editing the slug of the second language page by adding '-1' to ensure uniqueness, although the client preferred to maintain identical slugs across languages. 3. We advised checking the WPML > Settings > Post Translation Settings and ensuring it was set to 'Translated only', which was already done by the client. 4. The client was also instructed to delete the problematic translated page, remove it from Trash, and then save the Permalink Settings again. 5. After these steps, the issue was resolved, although the exact cause was not clearly identified.
If this solution does not apply to your case, or if it seems outdated, 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 the problem persists, please open a new support ticket.
Problem:
Elementor product module showing products only in default language.
Solution:
I checked the WPML settings and found out that "Adjust IDs for multilingual functionality" option was disabled from WPML >> Languages page, I just enable it and now the products are showing correctly on English language page.
Problem: The client is experiencing issues with transferring the WPML site key to a new domain name, phagetherapygeorgia.eu, from the old site, caucasushealing.com. The client is unable to connect the key on the new site, encountering an error message 'wpml: Unable to register: Site key not matching'. Additionally, the site is running slow after the domain change. Solution: 1. To resolve the 'Site key not matching' error and transfer the WPML site key to the new domain, you need to re-register the key. Re-registering the key will not affect your translations; it is only necessary to keep WPML updated and to access support and translation features. 2. If you are unsure where to find the option to re-register, navigate to the 'Plugins' section in your WordPress dashboard, then go to 'Add New', and you will find the 'Commercial' tab where you can manage your WPML registration.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: The client is new to WPML automatic translation and Pay-as-You-Go services and encountered unexpected results in translation costs. The client noticed a significant difference between the word count shown in the Translation Dashboard and the actual credits used, making it difficult to estimate costs. The client asked for clarification on why the credits used are significantly higher than the expected word count, whether repeated content is charged again, and how to better estimate translation costs.
Solution: 1. Translation memory only takes effect for future translations and does not apply to translations sent in the same batch. Therefore, if the homepage and the paragliding page were sent in the same batch, the translation memory would not reduce the word count for repeated content. 2. For Divi global sections, it is recommended to first translate the global sections and then the pages using them to ensure translations are reused without extra charges. 3. The Translation Dashboard may not reliably apply translation memory for estimating word counts. A better approach would be to send the jobs directly to the Advanced Translation Editor (ATE) to see the actual word count that will be translated before applying automatic translation.
If these steps do not resolve your issue or the information provided here is outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where clicking the refresh icon in the WooCommerce product grid leads you to the WooCommerce product editor instead of the WPML Translation Editor, this might be due to the settings not being correctly configured to use the WPML Editor for translations. Solution: To resolve this, please follow these steps: 1. Inside the product editor, click on "WPML Editor für Übersetzungen". 2. In the pop-up that appears, select the option to change the editor for that product only. 3. Click the Update button to save the changes. Now, when you attempt to update the product's translation, it should redirect you to the WPML Translation Editor. 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 the issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're encountering an error message 'Change the field group translation setting', seeing a lock icon when trying to update content, or having issues updating the WPML plugin, here are the steps to resolve these issues. Solution: 1) For the error message 'Change the field group translation setting', it's actually a warning indicating a needed adjustment. Set the ACF Field Group to 'Do not translate'. More details can be found here: https://wpml.org/errata/advanced-custom-fields-field-group-should-be-set-as-not-translatable/ 2) If the WPML plugin won't update, it might be due to the site still being registered under an old domain. To fix this, go to WPML → Plugins → All Plugins, open the Commercial tab, click 'Unregister' at the top right, and then add the new site key from your WPML account: https://wpml.org/account/sites/ 3) If you encounter a lock icon when updating content, this is expected unless translation preferences are configured. Set your preferred translation option as explained here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/#translating-options-page-custom-fields If these solutions do not resolve your issues or seem outdated, 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing an issue where the WPML dropdown click switcher works in desktop view but fails in mobile view. The switcher does not function with the popup effect in mobile view. Solution: We recommended the client to first ensure that all WPML plugins are updated to the latest versions. Here are the steps we suggested: 1) Navigate to Plugins > Add New > Commercial and click "Check for updates" to update WPML plugins to the latest versions. 2) Create a backup of the site before proceeding with further steps. 3) Disable all other plugins, leaving only WPML plugins active, to check if the issue persists. 4) Switch to a WordPress default theme to see if the issue still occurs. If these steps do not resolve the issue, it might be due to outdated information or a specific case not covered here. 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 WPML support forum for further assistance.
Problem: The client was experiencing issues with the 'Widget language switcher' not being visible when accessing WPML – Languages again. Additionally, there were concerns about the widget area being too wide and how to display the flag for the selected language in a narrow header view on tablet/mobile.
Solution: 1. To ensure the 'Widget language switcher' remains visible, we recommended deactivating and then reactivating WPML, which resolved the visibility issue.
2. To address potential issues with settings not being saved, we suggested increasing the PHP memory limit to at least 512M. This can be done by adding the following code to the 'wp-config.php' file:
3. We also advised checking for Object Cache conflicts by temporarily deactivating and purging the cache.
4. For diagnosing theme or plugin conflicts: - Create a backup of the website. - Use a default theme like 'TwentyTwenty' and deactivate all plugins except WPML-related ones. - Reactivate plugins one by one to identify any conflicts.
If these steps do not resolve the issue or if the solution 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.
Problem: The client needs to know if they can edit translations locally on their site without accessing external servers due to security concerns. Solution: If you're experiencing the need to edit translations locally, we recommend two options: 1) Use the Classic Translation Editor, which operates directly within WordPress. 2) Switch to Manual Mode, allowing you to edit translations directly in your Page Builder. Note that the external connection is only necessary for the Advanced Translation Editor, which provides additional features like automatic translation, glossary, and translation memory. More information on these features can be found here.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client was unable to register their site with a new WPML key after the account was transferred and the previous key was unregistered. The system did not accept the new key and displayed errors indicating a mismatch and an expired account. Solution: 1. We recommended increasing the WordPress memory limit to at least 128MB by adding the following code to the wp-config.php file:
This code should be placed above the line /* That's all, stop editing! Happy blogging. */. 2. After adjusting the memory limit, the client was instructed to: - Visit https://wpml.org/account/sites/ and delete the site. - Navigate to the site's dashboard under Plugins -> Add new -> Commercial tab, unregister the site if it was still registered, and then register the site with a new key generated from the same page.
If these steps do not resolve the issue or if the solution 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 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
