Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] WooCommerce checkout strings not using WPML translations

[Resolved] WooCommerce checkout strings not using WPML translations

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

Problem:
If you're experiencing issues where some WooCommerce checkout strings, such as 'Населённый пункт' and 'Saadetis', are not using the translations set in WPML → String Translation in both Estonian and Russian languages, despite having disabled automatic updates and cleared caches.
Solution:
We recommend exporting the .pot file with the updated strings from a test site where the issue is already resolved. You can do this via WPML → String Translation → Import/Export → Export strings. Then, import this .pot file into your live site using the same WPML → String Translation → Import/Export path. This process is safe to perform on a production site and should not affect your existing content or database structure. Additionally, this fix should remain effective after future WPML or WooCommerce updates, although you may need to re-scan for new strings or re-export/re-import the .pot file if updates introduce changes.

Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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 issue persists, please open a new support ticket 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.

Tagged: 

This topic contains 22 replies, has 0 voices.

Last updated by Dražen 1 month, 1 week ago.

Assisted by: Dražen.

Author Posts
October 24, 2025 at 8:02 am #17515133

innarL

I’m not sure what exactly is blocking the SFTP access — I can log in without any issues from my side, using the same credentials.

Maybe the hosting environment has some restrictions for external connections.

Please let me know if you’d like me to check or send something manually from the file structure.
October 24, 2025 at 8:28 am #17515257

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

yes, please if you can check, since it worked fine few days ago. I would like for our 2nd tier to check the structure and advise further, but we can not without login.

I have also deployed your website in local environment in default WP structure and there translation works fine.

Regards,
Drazen
October 24, 2025 at 1:11 pm #17516762

innarL

Hi,

I checked this with Pressable, and they confirmed that SFTP access is not restricted by IP -external developers can connect using the same credentials.

I'd reset the password, but again here is no field for sensitive data.

Thanks
October 27, 2025 at 6:45 am #17520089

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks.

Yes, I need to enable the private fields for you.

I have done it so now.

Regards,
Drazen
October 27, 2025 at 1:02 pm #17521987

innarL

I’ve added the SFTP details.
October 28, 2025 at 6:30 am #17524299

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks, I can login now.

Sharing it with our 2nd tier so they can advise further.

Regards,
Drazen
October 30, 2025 at 9:07 am #17531613

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

We downloaded the .pot file with translations from WPML > String Translation > Import / Export from local installation and imported it t your site.

It’s now fixed there, and I can see multiple instances of the “Shipping” string at this link and translated fine:

- hidden link

- hidden link

Regards,
Drazen
November 2, 2025 at 9:50 am #17537989

innarL

Hi Dražen,

Thank you for fixing the translation issue on the test site, everything looks perfect there now.

Could you please confirm the correct steps to safely apply the same fix on my main (live) site?

From what I understand, I should:

1 - Export the .pot file with the updated strings from the test site (where it’s already fixed).

2 - Import this .pot file into the live site using WPML → String Translation → Import/Export.

Is this the right way to replicate the fix, and is it safe to do it directly on the production site?

Also, could you please confirm that this fix will remain in place after future plugin or WooCommerce updates?

Thank you for your help and all your time on this case!
November 3, 2025 at 6:44 am #17539478

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hi Inna,

I’m glad to hear everything looks good on the test site!

Yes, your steps are correct — you can safely replicate the fix on your live site as follows:

Export the updated .pot file from the test site (WPML → String Translation → Import/Export → Export strings).

On the live site, go to WPML → String Translation → Import/Export, and import that same file.

This process is safe to do on the production site — it won’t affect your existing content or database structure.

The fix should remain in place after future WPML or WooCommerce updates. However, if a new update introduces additional strings or changes existing ones, you might need to re-scan for new strings or re-export/re-import the .pot file to keep everything synchronized.

Best regards,
Dražen