Skip Navigation

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.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 7:00 – 12:00 -
- 13:00 – 16:00 13:00 – 16:00 13:00 – 16:00 13:00 – 16:00 13:00 – 16:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

Tagged: 

This topic contains 0 replies, has 2 voices.

Last updated by Lucas Vidal de Andrade 1 week, 1 day ago.

Assisted by: Lucas Vidal de Andrade.

Author Posts
November 19, 2024 at 12:05 pm

pawelB-25

Background of the issue:
I'm trying to translate items on the left sidebar on my website using WPML. The specific URLs I'm working on are hidden link and hidden link. I am following the documentation at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/?utm_source=plugin&utm_medium=gui&utm_campaign=acfml#using-different-fields-across-languages.

Symptoms:
Translation is not working for the items on the left sidebar.

Questions:
How can I get the translations to work for the sidebar items on the specified URLs?

November 19, 2024 at 12:40 pm
November 19, 2024 at 2:18 pm #16420220

pawelB-25

I still need assistance.
I have a problem that these things still don't translate:
Brand
Number of chambers
Number of gaskets

Even though I have their translations set in string translations, even though I cleared the cache.

I have a problem that the large ACF group field called site modules is untranslatable in the German version even though I have the "Diffrent accros language" option set

An example is:
hidden link

There is:
Button two

And there is a "padlock" there all the time even though theoretically it should be translatable without any problems because it is an ACF field set to translate or copy once.

I would be grateful for your help.

If there is such a possibility, I would be grateful for an email notification at:
dawid.gawalkiewicz@pageart.pl

How will you respond to this ticket, considering that I am the one responsible for the technical support of this site.

Best regards,
Dawid Gawałkiewicz

November 19, 2024 at 6:59 pm #16421125

Lucas Vidal de Andrade
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thank you for waiting. I was able to fix the issue in a copy of your website. Please make sure to have a full website backup and follow these steps:

1. Go to WPML > String Translation and select "Look for string while pages are rendered";
2. Wait a couple of seconds;
3. Visit hidden link and hit CTRL + SHIFT + R (or CMD, if you're using a Mac);
4. Go back to WPML > String Translation and refresh the page
5. Look for the strings "Brand", "number of gaskets" and "number of chambers" and add the translation to all occurrences;

That should fix it. The labels weren't properly registered, so doing that will register them, so that they can be translated. In step #5, you should find new untranslated occurrences. Let me know how it goes.

Kunststofffenster - Kosten _ Lieferung - Fenbro.jpeg
String Translation _ Fenbro _ WordPress.jpeg
November 20, 2024 at 6:58 am #16422283
pawelB-25

ok, will try to do that.
My another problem:
I have a problem that the large ACF group field called site modules is untranslatable in the German version even though I have the "Diffrent accros language" option set

An example is:
hidden link

There is:
Button two

And there is a "padlock" there all the time even though theoretically it should be translatable without any problems because it is an ACF field set to translate or copy once.

I would be grateful for your help.

If there is such a possibility, I would be grateful for an email notification at:
dawid.gawalkiewicz@pageart.pl

How will you respond to this ticket, considering that I am the one responsible for the technical support of this site.

Best regards,
Dawid Gawałkiewicz

New threads created by Lucas Vidal de Andrade and linked to this one are listed below:

https://wpml.org/forums/topic/split-untranslated-acfs/

November 20, 2024 at 1:06 pm #16424783

Lucas Vidal de Andrade
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Please let me know your results, when performing the steps I advised previously.

To keep thing organized, I created a new ticket to discuss the other issue you're having with your custom fields:
https://wpml.org/forums/topic/split-untranslated-acfs/

I'll answer you there.

November 25, 2024 at 12:40 pm #16439768

pawelB-25

Ok, still this seems not working most of the times.
I still have in WPML things like that:
Wind resistance
Water resistance
Acoustic insulation
Air permeability
Profile thickness
Price from

And probably more things not translated which I cannot find right now, why we have these errors and do i have to use Look for string while pages are rendered since i have few hundrets of users walking on page?

November 25, 2024 at 5:54 pm #16441616

Lucas Vidal de Andrade
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there Dawid.

Can you please be more specific?

1. What exactly is not working most of the time? Please share concrete examples;
2. Where do these string appear (Wind resistance, Water resistance, etc), in the front end? Please show me an example for each of those strings;

And probably more things not translated which I cannot find right now, why we have these errors and do i have to use Look for string while pages are rendered since i have few hundrets of users walking on page?

It's necessary that the user reviews the website and check what strings and texts need to be translated.

So far, we had no errors. WPML depends on themes and plugins to properly register texts, so that they can be translatable. When that's not done properly, we need to actively search for the strings. This is what we did.

Yes, when you use "Look for strings while pages are rendered", you need to visit the page that contains them yourself. That's because of the way the rendering works internally.

Please note that not all the strings present in WPML > String Translation need to be translated. You can only translate the ones that show in the website and actually need translation.