Inicio›Soporte›Soporte en español›[A la espera de la opinión de los usuarios] Strings are translated but always showing in English on the frontend (custom plugin, 4 languages)
[A la espera de la opinión de los usuarios] Strings are translated but always showing in English on the frontend (custom plugin, 4 languages)
Este es el foro de soporte técnico de WPML, el plugin multilingüe de WordPress.
Todas las personas pueden leerlo pero solo los clientes de WPML pueden ingresar comentarios. El equipo de WPML responde en los foros 6 días a la semana, 22 horas por día.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
8:00 – 12:00
8:00 – 12:00
8:00 – 12:00
8:00 – 12:00
8:00 – 12:00
-
-
13:00 – 17:00
13:00 – 17:00
13:00 – 17:00
13:00 – 17:00
13:00 – 17:00
-
Zona horaria del soporte: Europe/Vienna (GMT+02:00)
Antecedentes del problema:
I am trying to ensure that the strings in our custom booking engine plugin, adobe-renting, are displayed in the correct language on the frontend. We have provided translations in Spanish, German, and French, and all translations are marked as complete in WPML String Translation. The issue can be seen on this page: enlace oculto
Síntomas:
The booking engine always displays the strings in English on the frontend, regardless of the selected language. For example, the string 'Where is your next trip?' is not showing its translations in Spanish, German, or French.
Preguntas:
How can I ensure WPML uses the translations for this custom plugin?
Is there a WPML configuration step we might be missing?
Thank you for sharing the details. When creating a custom plugin, one of the most important actions, is to properly wrap your hard-coded strings into gettext calls. You can find more details about that in the documentation below ():
Please note that the creation of custom is unfortunately out of the scope of our support, so I can't check or write the custom created code from your plugin, but the documentation covers all your needs.
Thank you for your reply. I completely understand about the need to properly wrap hard-coded strings with __() and _e().
However, in our case the issue is broader:
For years the translations worked correctly, both for our custom plugin (adobe-renting) and for third-party plugins.
After the recent WPML update, translations stopped working globally.
Now it is not only our custom plugin strings, but also other plugin strings (e.g., WooCommerce, Elementor, Essential Addons, etc.) that no longer show the translations on the frontend.
The translations are still present in WPML → String Translation, marked as complete, but they are ignored on the frontend.
This suggests that the issue is not with the way our plugin registers strings, but with how WPML is currently loading or replacing translations after the update.
We really need guidance because the problem is not isolated to one plugin, it is affecting the entire multilingual site.
Thank you for clarifying. Indeed, in this scenario, the cause shouldn't be the string registration on code, as the issue is broader.
I would like to look at this directly on your site. For this, I would need temporary access (WP-Admin and FTP) to your site, preferably to a test/staging site where the problem has been replicated if possible.
The required fields can be found below the comments section. The information you enter is private, i.e. only you and I can see it and have access to it.
I may need to replicate your website locally. To do this, I need to temporarily install a plugin called "Duplicator" or "All in One WP Migration" on your website. This will allow me to create a copy of your website and content. Once the issue is resolved, I will delete the local website. Let me know if this works for you.
IMPORTANT
Please make a backup copy of the site files and database before giving us access.
- If you do not see the wp-admin/FTP fields, this means your post and site login details are being made PUBLIC. DO NOT post your website details if you do not see the required wp-admin/FTP fields. If you do not, ask me to enable the private box. The private box looks like this:
