This thread is resolved. Here is a description of the problem and solution.
Problem: The client's website is multilingual (EST, RUS, ENG) and faces an issue where string translations in the WooCommerce checkout form revert to English when the 'Auto register strings for translation' is disabled. Solution: We recommend trying the following steps: 1. Ensure you have a backup of your live site. 2. Navigate to the
wp-content/languages/plugins
directory. 3. Rename or remove the file named
woo-checkout-field-editor-pro-ru_RU.l10n.php
. This action should resolve the issue with the string translations reverting to English.
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 the problem persist, please do not hesitate to open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
The site has 3 languages: EST (main language), RUS, and ENG (second languages). String translations do not work in the WooCommerce checkout form, specifically for billing and shipping fields with customer information. Translations are only displayed when the function 'Auto register strings for translation' is enabled. Once it is disabled, the translation reverts to English (default).
Symptoms:
String translations in the WooCommerce checkout form revert to English when 'Auto register strings for translation' is disabled.
Questions:
How can I ensure that string translations in the WooCommerce checkout form work without enabling 'Auto register strings for translation'?
To troubleshoot this issue without affecting your live site, I have set up a fresh WP site on cloudways. Can you please migrate your site to the cloudways server so that we can see if it’s a theme/plugin conflict or a server-specific issue? I have shared the migration details in a previous private reply.
Thanks for migrating the site and sharing the login details of the test site. I’m working on debugging this issue on the test site and will get back to you with an update soon.
- I’ve checked the issue in the minimal environment by deactivating all plugins except WPML, WooCommerce, Checkout Field Editor for WooCommerce plugins, and with the parent Divi theme but the issue still persists.
- The issue is gone when I deactivated the Checkout Field Editor for WooCommerce plugin. I suspect this might be a compatiblity issue between Divi, WPML, and Checkout Field Editor for WooCommerce plugin.
- When we spot a compatibility conflict, we need to replicate this issue at fresh WP site in order to escalate it to our 2nd tier support.
- To replicate this issue at fresh WP site, Could you please follow the below steps:
1. Please login to the fresh WP site by clicking on the auto login URL: hidden link
2. Please install the Divi theme and Checkout Field Editor for WooCommerce plugin.
3. Configure them as you did on your site and let me know how it goes.
Thanks for installing the necessary theme and plugins, I’ve tried to replicate this issue at fresh WP site but it seems to be working correctly there.
It seems to be the site specific issue, so I thoroughly debugged this issue on test site and by renaming/removing the “woo-checkout-field-editor-pro-ru_RU.l10n.php” file from wp-content/languages/plugins directory the issue is solved.
Can you please give it a try on your live site after taking backup and see if this resolves the issue.
Thank you for your cooperation and amazing patience
Thanks for amazing support! It solves the problem!
Manage Cookie Consent
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.