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.
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.
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.
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?
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.
The topic ‘[Closed] Translation is not working’ is closed to new replies.
