Skip Navigation

Home › Support › English Support › [Resolved] Translate Woocommerce Checkout page fields generated by Checkout Field Editor

[Resolved] Translate Woocommerce Checkout page fields generated by Checkout Field Editor

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

Problem:
The client was experiencing an issue where, despite entering Spanish translations for checkout fields using WPML, the fields were still displaying in English during the checkout process in Spanish.
Solution:
We recommended the following steps to resolve the issue:
1. Ensure a backup of the live site is available.
2. Navigate to the directory: 

wp-content/languages/plugins

3. Rename or remove the file named 

woo-checkout-field-editor-pro-es_MX.l10n.php

. We suggested renaming it by adding '.deactivate' at the end of the file name.
This action should resolve the issue upon reloading the front end.

If this solution does not apply to your case, or if it seems outdated, 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 do not hesitate to 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 4 replies, has 2 voices.

Last updated by Bobby 5 months, 1 week ago.

Assisted by: Bobby.

Author Posts
June 6, 2024 at 9:21 pm #15713367

steveV-5

Background of the issue:
Estoy tratando de traducir los campos en mi formulario de pago de Woocommerce, pero no funciona, incluso si replico la técnica especificada en el foro de WPML por varias personas, incluido su equipo de soporte. Enlace a la página donde se puede ver el problema: hidden link

Symptoms:
Siempre veo el campo en inglés en lugar de en español.

Questions:
¿Por qué no se traducen los campos en mi formulario de pago de Woocommerce?
¿Hay algún paso adicional que deba seguir para que la traducción funcione?
June 7, 2024 at 10:44 pm #15717894

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

Do you see the fields in English rather than Spanish within the WPML->String Translation area? Or do they just show in English even though you have added the translations?

June 9, 2024 at 9:17 pm #15719838

steveV-5

Hello Bobby,

I can see the fields detected by WPML and I can well enter their Spanish translations, but everything is displayed in English when I checkout in Spanish.

Thanks for your help.

June 10, 2024 at 5:45 pm #15723431

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)

**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **

I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.

NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.

Thank you,
Bobby
June 18, 2024 at 4:53 am #15747161

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

I was able to resolve the issue.

1. Ensure you have a backup of your live site.
2. Navigate to the following directory.

wp-content/languages/plugins

3. Rename or remove the file named

woo-checkout-field-editor-pro-es_MX.l10n.php

NOTE: I renamed it by adding .deactivate at the end of it.

Doing this immediately resolved the issue upon a reload of the front end.
June 20, 2024 at 4:20 pm #15765556

steveV-5

Thank you Bobby,

It's working like a charm.

Have a good day!