This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to use default WooCommerce translations for your shop, but WPML can't load the default .mo file. Solution: 1) Go to Dashboard > Updates and load the latest updates for WordPress. 2) Go to WPML > Theme & Plugin Localization and scan the theme and plugins for strings. Before running these steps on the staging, ensure to fix collation issues and run WPML troubleshooting options to clean up string tables (WPML > Support > troubleshooting). If these steps do not resolve the issue, it could be due to various factors such as minimum server requirements, server limitations like missing writing permissions, corrupted data on the string tables, corrupted language files, or issues between plugins or the theme. If you encounter issues on the live site after applying these steps, we recommend opening a new support ticket. Additionally, 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 solution provided here is not relevant or outdated, please contact us for further assistance at WPML support forum.
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.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
While investigating this issue, I realized a Collation problem in your database.
- The database itself is set to "latin1_swedish_ci" and should also use "utf8mb4_unicode_520_ci".
- All tables and affected table rows should use "utf8mb4_unicode_520_ci".
I have fixed those issues partially on the local copy of your site.
After that, I rescanned the plugins for new strings and it appears to have solved the issue.
Would you like me to send you a copy of the partially fixed database?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
No, I did not change the password on the staging site.
I took a local copy of the site, fixed all the DB collation issues manually on most of the tables, cleaned up the string tables, then scanned again for new strings and created the custom language files for WPML.
I can send you a copy of this database, or you first contact your hosting support team and ask them for assistance in fixing the collation issues inside your database.
You mean having access to phpmyadmin ? This will be difficult to give you access to this, but here is a screenshot showing that all the tables and rows on the staging website now use "utf8mb4_unicode_520_ci" : hidden link
If you only need to use WordPress, I already gave you the credentials for the admin password.
Yes. I used the Operations -> Collation tools for that.
See attached picture.
If I may make one criticism, I find your support painfully slow. I've had the ticket open since the end of September, and the problem still hasn't been solved.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I am really sorry for the delay, but this is a very unexpected issue and I have spent a lot of time in investigating it.
On your staging, as a test, I removed the custom mo files from /wp-content/languages/wpml. I took a local backup of the folder and trestored it after my test.
While the folder was empty, I went to WPML > Support > Troubleshooting and force the dialog to create custom .mo language files and the dialog will not start.
The reason for this usually is missing write permission on the folders on the server.
