This topic has 10 replies, 3 voices, and was last updated 3 years ago ago by Olga Barlow
Hi !
Header builder > Contacts > “Text For Field” does not appear in WPML String translation. (Title appears)
Hi,
You can translate admin strings using WPML admin strings option and add them to your string translator https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
Also, follow the WPML documentation https://wpml.org/documentation/theme-compatibility/building-multilingual-ecommerce-sites-using-xstore-and-wpml/?aid=46060&affiliate_key=YI8njhBqLYnp
Let me know if you still have issues with translation after that and untranslated strings.
Regards
Thanks Rose,
Now first button translation does not appear.
[theme_mods_xstore-child][contacts_package_et-desktop][0]contact_subtitle
I have reordered, deleted, rebuild – [0] does not work.
https://gyazo.com/5ba94e277658460e4709dc7e708bd730
Hello,
Provide temporary wp-admin access.
Let us know what can’t be translated now.
Regards
Here You are:
We can’t login – https://gyazo.com/54c41fdc5802ef6e92fc36a273da7f5b
Do you need our IPs to add to Whitelist or can you temporarily disable the restriction?
Regards
Sorry, unblocked now!
Hello,
I have created header for the EN version and translated texts there https://prnt.sc/1183ied Check EN version now.
Regards
Hi Olga,
This can be just temporarily solution, right! Adding two more neighborhood languages, we will manage 4 headers plus mobile one, just because of software error. No good, but okay for upcoming week or two.
Will wait the fix in next update and Thanks anyway,
Tiit
Hello,
Actually, we created Multiple headers option and added a language selector to the conditions to allow users to translate headers content to other languages. So, it’s not a bug. That header element (Contacts) does not support WPML string translator well and there is no way to change that, unfortunately.
Regards
The issue related to '‘Header builder > Contacts : Not translateable’' has been successfully resolved, and the topic is now closed for further responses