Problem: The client had previously deactivated and deleted WPML and its additional plugins but found that there were still language files (French and English .json, .mo, and .po files) and a 'wpml' folder in the 'languages' directory within 'wp-content'. The client was unsure whether these files and the 'wpml' folder should be deleted and also inquired if deactivating and deleting WPML would remove related database tables. Solution: If you're not using WPML anymore, you can safely delete the related WPML files and folders. For detailed instructions on how to delete .mo and .po files for removed languages, please refer to our documentation:
Regarding the database tables, deactivating and deleting the plugin does not automatically remove them. You can use the reset option in WPML > Support > Troubleshooting to remove the tables if WPML is still installed. If you have already deactivated and deleted WPML, you will need to manually remove the tables from the database using PHPmyAdmin or a similar tool provided by your hosting platform.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We 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. If the issue persists, please open a new support ticket with us for further assistance.
Problem: The client was experiencing issues with WooCommerce products not displaying after translating them using WPML. The translated product pages were blank. Solution: We identified that the problem was due to a string that had been translated with variables, which caused a fatal error in WordPress. To resolve this, we recommended the following steps: 1. Navigate to WPML > String Translation; 2. Search for the "You must be" string; 3. Edit its translation and remove the variables, ensuring the final result matches the provided screenshot.
After following these steps, the website should function correctly.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client was unable to view the Dutch version of a page on their website. Although the Dutch flag was visible when trying to switch languages in the front-end, clicking on it still resulted in the English page being displayed. Solution: We discovered that there was a 301 redirect from the Dutch URL to the English one, which was set up using the Redirection plugin. We disabled this redirect, and after doing so, the Dutch page became accessible.
If you're experiencing a similar issue where you can't switch to a different language version of a page on your site, we recommend checking for any redirects that might have been created with redirection plugins. If you find one, try disabling it to see if that resolves the issue.
Please note that this solution might not apply to your case, or it could be outdated. If after trying this step you still encounter problems, 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 issue persists, please open a new support ticket with us for further assistance.
Problem: If you're experiencing an issue where the automatic translation is stuck, it might be due to a corrupted entry that prevents the translation status from updating correctly.
Solution: We recommend the following steps to resolve this issue: 1. Go to the pages section. 2. Switch to the secondary language using the top admin bar. 3. Delete the page translation. 4. Also, delete it from the Trash. 5. Switch back to the primary language. 6. Translate the page again manually. Since the translation memory should have the content, it won't consume additional credits. Mark it as completed in the Advanced Translation Editor (ATE).
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we 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 you still need assistance, please open a new support ticket.
Problem: The client was experiencing issues with translating Advanced Custom Fields (ACF) because the translation mode for the fields was not selected. Solution: We accessed the client's field groups and selected the appropriate translation mode for the fields. We then instructed the client to update the post in the default language and its translation. We also provided a guide for translating ACF fields: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
If you're experiencing a similar issue, we recommend checking the translation mode for your ACF fields and ensuring they are set correctly. After that, update your post in the default language and its translation. For detailed guidance, please refer to our documentation on translating ACF fields.
Please note that this solution 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 don't hesitate to open a new support ticket in our forum: https://wpml.org/forums/forum/english-support/.
Problem: The client is unable to log into the WordPress admin panel without entering recovery mode due to an error with WPML Multilingual CMS plugin.
Solution: We recommend creating a full website backup before proceeding. Then, deactivate and delete the current WPML plugin. Manually download the latest version of WPML from here by selecting "Download WPML manually". After downloading, install and activate the plugin to potentially resolve the error.
If this solution does not apply to your situation, or if it's outdated, we suggest checking the related known issues, verifying the version of the permanent fix, and ensuring that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket with us.
Problem: The client was experiencing a fatal error when trying to synchronize attributes and translate products in bulk using WPML and WooCommerce. The error was a TypeError in
wc-attribute-functions.php
indicating that an array was given where a string was expected.
Solution: We recommended the following troubleshooting steps: 1. Navigate to WPML -> Support -> Troubleshooting and perform the following actions: - Synchronize posts taxonomies (for products and then for variations) - Clear the cache in WPML - Remove ghost entries from the translation tables - Set language information - Fix terms count - Fix post type assignment for translations
If the issue persists, we suggested: 1. Installing the Adminer plugin to investigate the database entries for the problematic product IDs. 2. Checking if the mentioned product IDs are valid and not in a corrupted state. 3. Bulk editing products in WordPress to potentially fix corrupted data.
If these steps do not resolve the issue, we advised the client to open a new support ticket for further assistance. 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.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, please do not hesitate to open a new support ticket with us for personalized assistance at WPML support forum.
Problem: The client was unsure if WPML inserts Hreflang tags directly into the raw HTML or via JavaScript, as some tags seemed to only appear after rendering when using crawling software. Solution: We insert Hreflang tags directly into the HTML using the
wp_head
hook from WordPress.
If this solution does not apply to your situation because it might be outdated or not relevant to your 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 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 experiencing a permissions error when trying to access the 'OTGS Installer' option and encounters an error when updating the WPML plugin, which causes the site to stop working.
Solution: 1. We recommend deleting the OTGS Installer since it's no longer necessary if WPML is already installed. Use the Plugins > Add New > Commercial tab to add extra plugins, or manually download them from our site and upload them via Plugins > Add New > Upload.
2. Check for compatibility issues by reviewing a similar ticket and following the steps provided there. Also, ensure that you are using the latest WPML version by comparing your current version with the latest one available.
3. Create a full website backup, update all plugins and the theme to the latest versions, and then disable all plugins except WPML.
4. If updating from the backend is not possible due to an old plugin version, manually update by first creating a full website backup, then deactivating and deleting the old plugin. Download the latest version from here and install and activate it manually.
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, 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 in the WPML support forum.
Problem: The client's pages were blocked for translation after being sent to Big Translation. Even after Big Translation confirmed that all jobs had been removed, the issue persisted. The client attempted to delete and duplicate the pages, which allowed for translation, but the translations were not displayed on the site. Solution: We resolved the issue by using WPML's troubleshooting functions. We recommend the client to: 1. Translate a page. 2. Check if the translation displays correctly on the site. For further guidance, we advise checking the WPML troubleshooting documentation.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we encourage you to open 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 on the WPML support forum.
Problem: The client needs to change a specific text phrase on products across all four languages of their website, which would require editing over 200 products manually. Solution:
We recommend various Search / Replace plugins or use the WP-CLI command $wp search-replace for that requirement. This also allows running a "dry run" without modifying data yet to show you how much content is found. The Global parameter is --dry-run: https://developer.wordpress.org/cli/commands/search-replace/.
If you're experiencing a similar issue and need to update text across multiple languages on your site, we suggest trying WP-CLI for a more efficient process.
Problem: The client was experiencing an issue where HTML code within an Elementor Pro HTML widget was appearing on the translation page, and the client was being forced to translate it. Solution: We recommended moving the code from the Elementor HTML widget to the
functions.php
file of the client's Child Theme. We provided the following code to correctly add JavaScript to the theme, which prevents the Advanced Translation Editor (ATE) from confusing HTML and script code:
After applying this change, the English version should display correctly and execute the JavaScript code without it appearing in the translation editor.
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. Should you need further assistance, please do not hesitate to open a new support ticket in our support forum.
Problem: The client is unable to display product filters in a widget on the archive shop page in a secondary language. Despite setting them as translatable and ensuring product attributes are syncing, the filters do not appear, and the message 'There are no products with the selected attributes.' is displayed. Solution: We recommend going to WooCommerce Multilingual -> Attributes tab -> Select the attribute, and click 'Synchronize attributes and update product variations'. This action should allow the filter to appear correctly in the secondary language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate to open a new support ticket. We also 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. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client is using the WP Editor to translate posts and pages from English to Arabic and notices that there are 20 pages of queued translations in the WPML Translation tab, despite the fact that these have already been translated. The client is concerned about why these are showing up and if there are any negative impacts or if they can be ignored.
Solution: We explained that the "Translations" section in WPML is designed to give a comprehensive overview of the translation status for all content. It allows users to see which translations need updates, view completed translations, edit translations, and manage translation jobs. We reassured the client that the pages listed in that section do not have any negative impact on the site. However, we advised paying attention to any translations marked as "Needs Update" and to update them as necessary. Other than that, the client can ignore the rest of the list without concern.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If after 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, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
Problem: The client is using the WPML plugin and noticed that their balance of automatic translation credits is showing as "0" despite only using 54,333 credits out of the 90,000 credits initially available. Solution: We recommended the client to check their Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools > Payment and settings > Automatic Translation Usage Reports. We provided a link to the documentation where they can find more information on how to access past invoices and usage reports: Automatic Translation Invoices.
If this solution does not resolve the issue or seems irrelevant due to being 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 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 contact us in the WPML support forum: 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
