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+01:00)
This topic contains 26 replies, has 2 voices.
Last updated by peterC-12 4 years, 8 months ago.
Assisted by: Yvette.
| Author | Posts |
|---|---|
| February 8, 2021 at 1:14 pm #8032797 | |
|
peterC-12 |
Hmmm, my answer on 1 feb2021 was not recorded apparently. It was this: Hello Yvette, Of course they were the first ones I approached. They replied they only provide basic WPML support. So this might be part of a bigger issue. One that might prove valuable to WPML because it affects many more companies. I you like, I can install a plugin from a totally different developer and demonstrate the exact same problem ? Best regards Peter |
| February 9, 2021 at 10:36 am #8039881 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
The sandbox site expired again and sod id the work. Argh. Can you do it one more time - I can use the explanation you already gave from the last message. The sandbox sites expire in 5 working days. |
| February 10, 2021 at 4:56 pm #8054743 | |
|
peterC-12 |
OK. 5 days is a bit short 🙂 Same thing as the previous time, but now for the product "Belt". 1) I reinstalled everything on the new test site. Booster plus is implemented and activated. 2) I also activated the WPML setting of Booster (to be found at Woocommerce/Booster Settings/Emails&Misc/Booster WPML). I did not change the default settings of this part (so it's the same as on my regular websites) 3) I added and activated the booster wholesale pricing module 4) I added and activated a second plugin (from a totally different developer) to show the same problem: Calculated Fields Form The issue: => please verify that this is the starting position for both products before you change anything Now, when you press 'update' in the English version (with or without changing anything else), the wholesale pricing setting in the Spanish version automatically gets wiped clean. Same happens to the settings from the Calculated Fields Form on the spanish product. (both the The team can test it themselves. If the investigating team wants to play around with booster wpml settings, they can at Woocommerce/Booster Settings/Emails&Misc/Booster WPML/settings. As said, I did not change anything here. Hopefully they find something ! Have a great day ! Peter |
| February 15, 2021 at 4:29 pm #8090217 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
I set the following custom fiields to be "Copy" and I don´t see the wiping out of translated fields behaviour. Is this the behaviour you are expecting to happen? Screencast: hidden link Can you try it on your side? |
| February 15, 2021 at 4:45 pm #8090255 | |
|
peterC-12 |
Hello Yvette, This is not at all what I expect to happen. Your setting simply copies / forces a setting from one product-language on the other one. So now, with your change, a setting in the Spanish language gets wiped clean and replaced with the setting of the English/original language. But the settings are different in each language. (I noticed also that in the sandbox the second plugin which showed the same 'wiped out' behaviour is gone. Why ? Because here it's very clear that the settings can not be the same in the different languages) Best regards Peter |
| February 15, 2021 at 5:18 pm #8090447 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
We have to focus on one plugin at a time - the additional plugin just confuses the case. So you are expecting to be able to put different wholesale prices in different languages? Our approach, in general, is to have all pricing information to be THE SAME in all languages. Nevertheless, as this is not a protected field "tehcnically" you should be able to set the same custom fields to "translate" instead of "copy" and have different values. Can you confirm that you expect to have different wholesale price conditions per language? |
| February 15, 2021 at 5:31 pm #8090549 | |
|
peterC-12 |
Hello Yvette, My question, and this whole support thread is not about pricing. It's about the fact that custom fields get wiped clean on updating the original language version. The wholesale field is just an example of this problem occurring. But if it helps to find the problem, yes, absolutely, I expect to have different wholesale price conditions per language. I expect that if I set them differently, that they stay different (unless I change them directly in the relevant language of course). As you mention it's not a protected field, so I am very curious how we can make it work. Best regards Peter |
| February 15, 2021 at 5:51 pm #8090605 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
Got it. Now I understand why you included the other plugin. As it is not pricing related, perhaps I will escalate that one instead. |
| February 15, 2021 at 6:47 pm #8090791 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
Escsalated again to compatibility team. |
| February 15, 2021 at 8:47 pm #8091031 | |
|
peterC-12 |
OK ! Thanks Peter |
| February 16, 2021 at 8:14 am #8093781 | |
|
Yvette Supporter
Languages: English (English ) Spanish (Español ) Timezone: Europe/Paris (GMT+01:00) |
Did I say that? TECHNICALLY, if the field is not locked by WCML as a pricing related field, then it should be sufficient to edit the original product and set the custom field to "Translate". This allows you to enter different values for that custom field in each language. However, WCML will normally protect pricing-related fields so that only one single view of that information is presented on yoru multilingual shop. The design of WCML is to aid in presenting a shop in many languages but not to have a different shop in each language. Therefore, product catalogues, for example, should all appear the same in each language. In your case, I am not sure what the right answer is. You have presented 2 cases where the expected behavior is not happening. This may be a bug in our code or an incompatibility with the plugins. This will be determined by the compatibilty team. How they decide to fix it is out of my hands but I would guess they would choose to keep the approach of maintaining all pricing/stock fields synchronised. The short answer you your question would be to set the values in each field and then DO NOT update the sourc product since that is the action that blanks it out. |
| February 16, 2021 at 8:31 am #8094043 | |
|
peterC-12 |
Hello Yvette, Thanks for explanation. Hopefully the compatibility team finds something ! I will try to play around with settings a bit more then. Because indeed, the expected behaviour is not happening. And your suggestion (= not to update a source product) is basically to live with the exact problem I reported. Maybe not ideal, but ok, I am very happy with WPML in general 🙂 Thanks for the investigation so far ! Have a great day ! Best regards Peter |