Problem: The client was experiencing an issue where the icon behind the page title in the WordPress back-end page list would keep spinning after attempting to translate a page, indicating that the translation was not completing. This problem occurred on both the production and staging sites, even after restoring backups and updating the WPML plugin.
Solution: We suggested that the issue might be related to the Avada theme layouts. It was possible that the layouts were created in a language that was later changed or deactivated. The client discovered that by creating a new layout and translating it, there was no issue. Further testing revealed that the problem was specific to the page representing the front page. By cloning the front page, creating a new one, and deleting the old front page, the translation issues were resolved, and everything started to work perfectly again.
If you're experiencing a similar issue, we recommend trying the following steps: 1. Create a new layout and translate it to see if the problem persists. 2. If the issue is specific to a particular page, try cloning that page, creating a new one, and then deleting the old page.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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 site moved notice appeared after pushing changes from staging to live and the client was unsure which option to select.
Solution:
To be able to use your original dev site and the new location, log in to the dev site and you’ll find a notification about your site moving to a new location that lets you mark the dev site as a copy.
After that, please follow the below steps to register the live site with a new key:
1. log in to the live site
2- Go to Plugins-> Add new-> Commercial tab
3- Click on "Unregister WPML from this site"
4- Click on "Register WPML"
5- Click on "Get a key for this site"
6- Create a new production key
7- Use it to register again in Plugins-> Add new-> Commercial tab
Problem:
After pushing the site to production, the admin dashboard showed the following error message: "We have detected a problem with some tables in the database. Please contact WPML support to get this fixed."
Solution:
The site moved notice appeared after pushing changes from staging to live and the client didn't select any option. After selecting one of the options, the error message was removed.
Problem: The client was unable to see the translated versions of their menus in French and Spanish on the desktop view of their website, although the mobile view and footer menus were displaying correctly. Solution: We recommended the following steps to resolve the issue: 1. Navigate to Appearance -> Menus, select the menu, and copy its ID. 2. Go to WPML -> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the menu ID. 5. Select the strings you want to translate. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the menu ID. For more detailed instructions, please refer to our guide on translating texts in the admin texts screen.
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 switched from Gutenberg to Classic Editor in WordPress and encountered an issue where the translations appeared correctly in the Advanced Editor but not on the live site after translating a post. Solution: We checked the issue and discovered an old package in WPML-> Packages with the same post ID as the post in question. We deleted this old package, updated the post and its translation, and asked the client to verify if the problem was resolved.
If you're experiencing a similar issue, we recommend checking for any old packages in WPML-> Packages that might be conflicting with your current translations. If you find any, delete them and update your posts and translations. If the solution provided here is not relevant to your case, possibly because it's outdated or not applicable, 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 you need further assistance, please don't hesitate to contact us on the WPML support forum.
Problem: The client was experiencing 404 errors on the shop pages of their WooCommerce store in five out of twenty stores, each in a different language.
Solution: 1. We identified that the issue was resolved when disabling the String Translation and testing in a minimal setup. 2. We found an error related to the WordPress Options table and the "rewrite_rules" option name. 3. We discovered that the problem might be due to incorrect translations of specific strings in the String Translation, particularly those that did not respect the original placeholder or special formatting. 4. We deleted all strings from the text domain "WP Endpoints", which resolved the errors, and the shop pages displayed correctly. 5. We then instructed the client to go to WooCommerce > Settings > Advanced and click the "Save changes" option to re-register the "WP Endpoints" strings for translation in WPML. 6. We advised the client to avoid translating endpoints unless necessary, and provided examples of endpoints that should not be translated, such as
wc/file/transient
and
wc-api
.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If you're still experiencing issues, we 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 with us.
Problem: The client was unable to see the WPML Translation Editor when editing a custom post and had issues translating an ACF field, as well as translating content using a shortcode with Divi Theme Builder.
Solution: Firstly, we recommended increasing the WP Memory Limit to at least 256M by adding the following code to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
We also suggested checking with the hosting provider if the memory limit could be increased even further.
For the ACF field translation issue, we advised checking the ACF Field Groups Settings and selecting the 'Expert' mode for translation preferences. This allows individual fields to be set as translatable. We provided a guide for reference: Choosing how to translate field groups Expert translation option
For translating the shortcode content, we suggested that if the shortcode or it's attributes are not available in the WPML Translation Editor, the client could try to locate it manually by placing the shortcode directly in the translated content using Divi.
If these solutions do not resolve the issues, or if they seem outdated or not applicable, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the problem persists, please open a new support ticket.
Problem: The client's website's shop page in Chinese is not displaying any products. Solution: 1. We asked the client to check if the products were already translated to Chinese at WooCommerce > WooCommerce Multilingual & Multi-Currency > Products. 2. We inquired if the client had translated the product base slug at WooCommerce > WooCommerce Multilingual & Multi-Currency > Store URLs to Chinese. 3. We recommended the client to review any further issues at WooCommerce > WooCommerce Multilingual & Multi-Currency > Status.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we suggest you open a new support ticket. 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 need further assistance, please visit our support forum.
Problem: The client needed to display prices in EUR on their website but required customers to checkout in AED, as their payment gateway only accepts AED. They were looking for a way to enable multiple currencies while restricting the checkout currency to AED, regardless of the payment gateway used. Solution: We informed the client that by default, all payment gateways set up on their site will be available for all site currencies. However, restricting a specific payment gateway to a specific currency is currently only possible with WooCommerce PayPal Payments, Stripe, and direct bank transfers. We provided a link to the relevant documentation: Multi-currency support for WooCommerce. We also suggested considering PayPal as it is available in over 200 countries, including the UAE, and accepts Visa or Mastercard payments.
Please note that this solution might not be applicable to your case, as it could be outdated or not relevant to your specific situation. If this is the case, 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 open a new support ticket in the WPML support forum.
Problem: The client is trying to translate an Avada form from English to French. The issue is that the "Checkbox fields (with conditional logic)" for the "SERVICE" field are not being displayed on the frontend of the French translation, even though the form appears as 100% translated in the Advanced Translation Editor (ATE). Solution: We recommend checking the specific errata page for a workaround regarding Avada forms where checkbox fields with conditional logic are not displaying in translated forms. You can find the workaround here: https://wpml.org/errata/avada-forms-checkbox-fields-with-conditional-logic-not-displaying-in-translated-forms/.
Please note that the solution provided might be outdated or not applicable to your case. If after following the steps 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 open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client needed help translating a product page and its content. Solution: We recommended the client to refer to the WooCommerce Multilingual documentation: https://wpml.org/documentation/related-projects/woocommerce-multilingual/. After receiving the debug information, we advised the client to ensure their server meets the minimum requirements: - PHP version 7.4 or greater. - MySQL version 8.0 or greater OR MariaDB version 10.4 or greater. More information on server requirements can be found here: https://wordpress.org/about/requirements/. We then instructed the client to update WordPress and WooCommerce to the latest versions, along with any add-ons. The client was also advised to install the WooCommerce Multilingual & Multicurrency plugin and follow the guide provided in the documentation. Updates and instructions for updating can be found under "My Account -> Downloads" on the WPML site, and the update guide is available here: http://wpml.org/faq/install-wpml/. We emphasized the importance of backing up the database before proceeding with the updates.
If the solution provided is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking the 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 with us.
Problem: The client accidentally triggered a translation request for their Services page in all available languages, which they did not intend to do, and they are concerned about using their translation credits prematurely.
Solution: Firstly, we confirmed that only a few pages had been translated to Spanish, and the Services page in French and German had not been translated yet, which means the translation credits were not used. This situation occurred because the client had the 'Translatable - use translation if available or fallback to default language' option selected in WPML>>Settings>>Post Types Translation, which lists pages/posts in secondary languages without translation or content duplication. For more details, we provided a link to the documentation: Displaying Untranslated Content on Pages in Secondary Languages.
Since the client has chosen the 'Translate What You Choose' option in WPML>>Settings>>Translation Mode, they need to manually send posts and pages for automatic translation. We provided documentation links for further guidance on automatic translation and managing multiple translation jobs in bulk:
We also directed the client to check the existing translation jobs and their status at: Translation Jobs Status Page.
If the solution provided here is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us at the WPML support forum.
Problem: The client is using a staging site and has encountered two notifications after setting it up. The first notification is about mapping the default language for automatic translation, and the second is about WPML detecting a new address for the site.
Solution: For the first notification regarding the default language, the client should ensure that the default language (English) is correctly mapped to a supported language in WPML -> Languages settings.
For the second notification about the site address change, on the staging site, the client should select "Yes, this is a copy" to indicate that the original site is still running. In the subsequent step, the client can decide whether to share credits for automatic translation with the staging site.
If these steps do not resolve the issue, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the problem persists, the client should open a new support ticket for further assistance at our support forum.
Problem: If you're trying to enable automatic translations but want to exclude certain posts in specific categories, you might be facing some difficulties.
Solution: We recommend using the "Translate what you choose" mode, which allows you to manually create translation jobs from WPML > Translation Management > Dashboard. This mode gives you the flexibility to send content for automatic translation or assign it to local translators as needed.
However, if you prefer to use the "Translate everything automatically" mode and still want to exclude specific posts from automatic translation, you'll need to edit each original post in the WordPress Editor. In the right sidebar, change the translation method from "WPML Translation Editor" to "WordPress Editor". This action will exclude those posts from automatic translation.
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, don't hesitate to open a new support ticket with us.
Problem: The client needed to update the date format for French to match the format 'le 20 février 2024' but changes made in the admin strings were not taking effect. Solution: We recommended manually translating the date format using the Advanced Translation Editor and provided the correct format to use. The client should enter the following format in the translation editor:
\l\e d F Y
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 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive