Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are trying to translate a string for a WooCommerce Product Taxonomy to other languages, but the translation does not appear on the frontend unless 'Look for strings while pages are rendered' is active. For example, instead of 'Color', 'Farbe' (the original string) is displayed.
Solution:
We found that the

wordpress-en_US.l10n.php

file in your site's directory might be outdated. We recommend renaming or deleting this file located at

wp-content/languages/wpml/wordpress-en_US.l10n.php

. This action should allow the

wordpress-en_US.mo

file to be loaded instead, potentially resolving the issue.

If this solution does not work or seems irrelevant due to it being outdated or not applicable to your case, 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 problem persists, please 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.

Tagged: 

This topic contains 0 reply, has 2 voices.

Last updated by enrikB 5 months ago.

Assisted by: Lauren.

Author Posts
December 6, 2024 at 1:58 pm #16486343

enrikB

I didn't make any updates or changes but I assumed that it was the workaround with changing the language to english(unless you re-imported the db) but maybe it wasn't.

Just updating the plugin on the live site didn't change anything.

Then I made a new backup and imported it into the testing site, including Plugins. There it seemed to work correctly. On my local site it works as well after doing a new import but I don't know why. Is there any data that is persistent but gets changed/updated when importing the database or doing a search-replace?

I will do a clean installation with all files on monday again probably and see if it's the same result.

December 11, 2024 at 12:27 pm #16503382

enrikB

I synced a 1:1 copy from live again, including database, and now its wrong again, even with the updated plugin.

hidden link

hidden link

Those two are still german. Any other ideas?

December 11, 2024 at 7:17 pm #16505202

Lauren
WPML Supporter since 10/2015

Languages: English (English )

Timezone: America/New_York (GMT-04:00)

Thank you so much for running these tests and the update. I've informed our 2nd tier team and they will continue troubleshooting. I'll update here as soon as I have more information.

January 10, 2025 at 4:16 pm #16582679

Lauren
WPML Supporter since 10/2015

Languages: English (English )

Timezone: America/New_York (GMT-04:00)

Our 2nd tier team noticed that the wordpress-en_US.l10n.php file is not updated on your site, causing the problem. It seems outdated. Try to rename or delete it in wp-content/languages/wpml/wordpress-en_US.l10n.php, so the wordpress-en_US.mo file will be loaded.

Let me know if the issue is resolved after that.

January 13, 2025 at 9:41 am #16587334

enrikB

Thank you so much, this really seems to have been the issue. I will give an update once the project lead accepted it and then we can close this ticket for good.

January 13, 2025 at 10:06 am #16587537

enrikB

The issue has now been fully fixed and can be closed.