[Resolved] WPML can't load Woocommerce .mo

I was able to access the DB today, which did not work earlier, and the tables are looking correct now.

I can not tell you more about the folder permissions, as FTP access is denied.

Please consult your hosting company and ask them to verify if the permissions are set correclty.

Also, ask if they are blocking any of our domains, as mentioned earlier.

Further, it looks like WPML > Support > Troubleshooting displays that the REST API is disabled, but I can access it on front end. Please also ask the hosting support of the REST API is somehow limited on this hosting platform.

Please tell them, that this issue did not occur on a local copy of the site on a virtual server.

More details:
https://wpml.org/documentation/support/rest-api-dependencies/

On your staging I went to Dashboard > Updates and made sure to download the latest language files from WordPress.

---

Also, I realized, that the issue about default strings appears not to be the the .mo files dialog for WPML not opening.

After reviewing this further, this dialog will only appear, once you create your own translations. The default translations will be loaded on my test site even without having .mo files.

---

- I did not change anything regarding REST API on the staging site.

I do not see this REST disabled notification on my local site copy, which is an identical copy of your staging site. Anyhow, this seems to be a false postitive, as you can see here that the REST API is functioning:

hidden link

---

- I did receive the FTP credencials, but once I enter them I get the message:
"Access denied".

---

Could you please provide me an example on the Frontend where strings are not loading as expected?

I can see for example here, that the translations are actually loading:
hidden link

Also, take note that in your specific case the Woodmart Theme overwrites many of the default WooCommerce strings.

Hi,

I am glad to hear that the issue seems to be solved.

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.

What was solved before running those steps on the staging:

- fixed collation issues
- ran WPML troubleshooting options to cleanup string tables (WPML > Support > troubleshooting)

If, this will not direclty solve the issue there could be various points that cause the issue, like:

- Minimum requierments for the server
- Server limitations, like missing writing permissions
- Courrupted data on the string tables
- Corrupted language files
- Issue between plugins or the theme

If you run into issues on the live site applying step 1) and 2), please let me know and i can offer to take a look at the site.

Best regards
Andreas

The custom language files, which WPML generates at /wp-content/languages/wpml are using the translations of WPML > String-Translation and convert them into .mo files.

The goal of this approach is a performance enhancement.

Those files are not requiered to display translation that are based on files coming from theme's and plugins.

I am sorry to hear that you are unhappy with my support. Take note, that you can open a new ticket anytime and one of my colleagues will be glad to assist you and maybe have a different approach towards investigating this problem.

I am honeslty not sure at this point what was cuasing the issue, as there are too many factors that need to be considered. It simply worked at some point after running step 1) and 2).

When I last visited the site, all the translatiosn showed up on Frontend but not on WPML > String Translation. This is an unexpected and rare behavior and I was not able to figure out what is causing it.

On the local copy I had the same issue. Somehow everything was registered inside WPML to the text-domain "default". I cleaned up the whole string table, then scanned theme and plugins again and then it worked.

You find an option on WPML > String Translation to delete strings by domain. This was another step I took, but take note, that you might remove strings that you translated aleady.

You reported that the issue got solved and I did not take a further look at the staging site. I currently I can not longer log in.

If you would like me to check this on the live site, let me know. The private reply form is enabled again.