Variation not displaying in translated language

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	-
-	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	19:00 – 22:00	-

Supporter timezone: Europe/Paris (GMT+02:00)

This topic contains 42 replies, has 2 voices.

Last updated by leonidasI 4 years, 9 months ago.

Assisted by: Yvette.

Author	Posts
January 7, 2021 at 7:11 pm #7796859
leonidasI	Hi just a follow up. Anything?
January 8, 2021 at 12:04 pm #7800511
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	Yes. The behaviour has been escalated to development (as you already know) but they have added 2 workaround suggestions for anybody with this situation. I am aware that one is not useful to you but perhaps the second (???). Workaround 1: - Set attribute to "Do not translate" However this makes the label of the attribute not translateable Workaround 2 (with label translation): -Set attribute to "Display as translated" - Translate label -Set attribute as "Do not translate" - Update translation of the product Just for your information - they are taking an active count on how many tickets are currently open with this problem but there are only 2. Not to say it is not important but it will affect the priotisation of the fix.
January 9, 2021 at 3:41 pm #7806713
leonidasI	Hi thanks for the update, It troubles me for many months now! If i set the attribute to No translate it works but with the original language and not the translated. The workaround 2 is not working.
January 11, 2021 at 8:21 am #7813369
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	I will advise the 2nd tier supporters that the 2nd workaround is not effective and see if they have any other suggestions.
January 12, 2021 at 10:43 am #7823421
leonidasI	Ok thanks
January 12, 2021 at 11:15 am #7823719
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	They have responded with: " the only extra workaround we found is to duplicate the product to the second language. In this case, the terms are displayed translated, as expected." That´s surprises me but I hope it works for you.
January 14, 2021 at 8:26 pm #7848297
leonidasI	Please explain this is what i was doing up to now of course i was translating check the video, hidden link
January 15, 2021 at 12:12 pm #7852451
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	It´s hard for me to understand what your video is showing as I don´t read Greek and the interface you are using does not appear to be the standard WordPress interface. What I gather the 2nd tier supporter is referring to is the following steps using the STANDARD wordpress interface with a minimal setup (no extra plugins active) - Translate all global attributes - WPML Duplciate an existing original language product to the 2nd language - Now, check if the GR view of the product is shwoing the translated labels or not. That is my understanding of what the 2nd tier wrote.
January 15, 2021 at 2:34 pm #7854013
leonidasI	You dont need to read greek i can put spanish there, they have zero meaning is just for test the problem is when i use the fronted wcfm as this is a multivendor marketplace i mention before this. We did this many times with default wc process still the same, i will pay someone to have a look on this and locate the problem as it became really tiring for me and i guess for you also. I gave you a stage site to see for yourselves. Anyway i will see if i have any results i will keep you posted.
January 15, 2021 at 5:20 pm #7855557
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	Understood. I cannot offer you any more ideas since this is now in the hands of our developers and they will prioritise any fixes/work that has to be done. I am sorry for that.
January 20, 2021 at 8:59 am #7884673
leonidasI	Its alright if we cant fix it then we have to remove wpml no other choice :/ Thank you
January 20, 2021 at 9:41 am #7884975
Yvette Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+02:00)	If this is something that cannot be fixed - I would imagine you could ask for a refund here: https://wpml.org/purchase/refunds/ I cannot guarantee that it would be given but I do think that it could be worth the effort to try (?). I´m sorry that the workarounds were not effective.
January 20, 2021 at 11:21 am #7886183
leonidasI	I dont want a refund Yvette i have full pack i have other sites also with wpml. Its clearly a compatibility issue between wpml and wcmf from wclovers. You should work to resolve it together because it will eventually catch up with more problems. When i disable the wpml string translate plugin everything works. I see what i can do Thank you for everything