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.

This topic contains 2 replies, has 0 voices.

Last updated by glebE 1 week, 4 days ago.

Assisted by: Alejandro.

Author Posts
December 16, 2024 at 10:19 am #16516619

glebE

Hello again Alejandro,

I translated the website, everything is very good, i am satisfied with the result.

But have 2 problems,

1. On all the product pages there is 1 block which didnt translate, only the header, and WPML doesnt see it, what can i do to resolve this? hidden link

2. there are strong tags in text, which is not good) hidden link can you help to resolve this please?

3. I am also curious about the above questions, and for example if i change some content, what is the best practice for implememnting it on the Finnish and/or other languages

December 16, 2024 at 2:49 pm #16517874

glebE

Did you make any responce to here? I got notification but i dont see anything

December 16, 2024 at 4:05 pm #16518199

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hello

1) Where can I see the problem here: hidden link ? because to be honest, I can't really see anything untranslated.

Instead I do see a place that is not translated in the original language: hidden link

I guess this is what you mean. I tried resending it for translation and saw it was not there, so I made a small change to that text (added a period at the end of the last list item) and the text appeared in the translation editor (and it also appeared as previously translated!).

It's all good now 🙂

2) Please check this video: hidden link
In short, that strong tag is not doing anything there, because divi is taking voer the styling. since you are adding the text BEFORE divi is rendered, it's read as a text, because that field is meant to be used with plain text and not HTML.

You can remove it and the changes won't be noticeable yet the result will be more accessibility friendly AND semantically correct in HTML (strong tags should be OUTSIDE heading tags, not inside!)

3) I'm no sure about this last question. in general, try to avoid using html when fields do not have the "text/visual" format, because they usually are not meant to be used like that.

December 16, 2024 at 5:45 pm #16518483

glebE

Thank you very much for your help!