SOLVED: WPML Template Translation enables translation classes and ids

Bugs
1

Hello,
I have noticed that when I am translating Bricks-Templates via the WPML Translation Panel it also lists class names and ids to be able to be translated.
I think this is an issue as it will clearly break the page, when you don’t pay very close attention to miss something, wich should not be changed like id and class names and all other design related settings.

Please exclude these fields from being translatable.

Bildschirmfoto 2023-10-03 um 22.27.20
Bildschirmfoto 2023-10-03 um 22.27.201474×2512 428 KB

2

Hi @albertvisuals,

Thank you for your report. You’re right, those values should be excluded from translation. Can you please share where you’ve added those values? (which element & setting). A screenshot would be great :slight_smile:

3

Hello @charaf ,

Uff… that are really many. It seems to take almost all text-input fields and thinks they should get translated. The picture here is form the header menu, I used the “s_menu_drop_gallery-textwrapper” in interactions, custom css classes and so on.
I guess it would fields should be excluded in general and only fields, which should be able to be translated should be allowed for WPML to be touched.

Bildschirmfoto 2023-10-05 um 21.23.41
Bildschirmfoto 2023-10-05 um 21.23.412300×1830 364 KB

4

Hi @albertvisuals,

Thank you for the details. By default, we register all strings (it’s better not to miss any strings than to miss some but not include unneeded strings). But we’re working on a list of controls to exclude from translations and I have added your request to the mix :slight_smile:

5

Hi charaf,

i have the same problem. I noticed this in the latest changelog “WPML: Exclude certain controls that don’t need translation”. So i guess the fields i am talking about, are not adressed yet.

In my case its the “CSS classes” text-input field (under the Style Panel of any element). Maybe you can exclude this fields in a future update :slight_smile: thank you

1 Like
6

Yup they should be excluded in the next release :slight_smile:

7

Hi guys,
We’ve fixed this issue in Bricks 1.9.3, now available as a one-click update in your WordPress Dashboard.

Changelog: Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

8

aaaa , not good , you just disabled the translation possibilities of inline links id we can’t translate the CSS ID field anymore.
This is a big setback as in one-page designs there are a lot of inline links.