Skip Navigation

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

Problem:
The client reported an issue where translations were visible in the WPML String Translation system but did not appear on the site unless 'Auto register strings for translation' was enabled. When this option was disabled, the translations reverted to English.
Solution:
We provided a step-by-step solution to address the issue:
1) Navigate to WPML>>String Translation.
2) Search for and delete the problematic string from the 'pinegrow' text domain.
3) Go to WPML>>Themes and Plugins localization.
4) Scan the theme strings for translation.
5) Translate the newly added string again in WPML>>String Translation.
Additionally, we suggested that the issue might be related to .mo files not matching the .po files used on the live site. We recommended:
- Regenerate the .mo files from WPML>>Support>>Troubleshooting by using the 'Show Custom MO Files Pre-generation' dialog box and clicking 'Generate .Mo files'.
- Clear all types of caches and check if the issue persists.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our support forum to open a new ticket. We also 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.

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.

No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Tagged: 

This topic contains 17 replies, has 2 voices.

Last updated by Bigul 1 month, 1 week ago.

Assisted by: Bigul.

Author Posts
September 24, 2024 at 1:49 pm #16215245

edA

I am responding to this ticket so that the status changes from "Waiting for user feedback" while I await followup. This should help in keeping it from automatically being closed as the original ticket was.

September 25, 2024 at 2:04 pm #16221061

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

We are still working on the bugs you reported and have an update now. Please check this post :- hidden link

The *Attorneys for this Practice Group* string's translation (*Avocats dans ce domaine d’expertise*) work as expected after the following steps.

1) Visit WPML>>String Translation
2) Search for the *Attorneys for this Practice Group* string
3) Delete the string *Attorneys for this Practice Group* from *pinegrow* text domain
4) Visit WPML>>Themes and Plugins localization
5) Scan the theme strings (*pinegrow*) for translation from WPML>>Theme and plugins localization>>Strings in the themes
6) Visit WPML>>String Translation and translated the newly added *Attorneys for this Practice Group* string

Please wait. We will get back to you soon with more details.

--
Thanks!

Bigul

October 4, 2024 at 3:00 pm #16254920

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

We are unable to reproduce the issue exactly on our testing servers, but we do have an update.

The .mo files do not depend on the .po files at runtime, which means the issue only occurs if some of the original strings in the migrated .mo files differ from those used on the live site.

Since the .mo file is usually an identical copy of the .po file, please consider migrating only the .po files and then recreating the .mo files directly on the live site.

To do this, regenerate the Mo files by clicking Show Custom MO Files Pre-generation dialog box >> Generate .Mo files from WPML>>Support>>Troubleshooting

Afterward, clear all types of caches and check if the issue still exists.

--
Thanks!

Bigul