ff kk

Thanks for your concern. It actually depends on the browser. Sometimes it fails to switch correctly after 2, 3, 4 times depending on your browser.

To replicate, pls install WP Rocket and Woo Multilingual with at least 3 languages and set up for each language the respective currency (only one currency for each language), then switch languages in different browsers a couple of times, it will break eventually, i.e. language switches but currency stalls. Then again, one needs to switch back and forth to get it right. It looks like Roulette a little. Hope that is useful. Would be great if these two plugins can work together.

Yes, we have updated to latest versions, everything up-to-date. Yes, improvements are visible, but our luck with the switcher would run out after 3 switches. Then it just won’t work properly with WP Rocket. These improvements might work fine with W3TC etc., but not with WP Rocket. Ask phj123; probably he also needs a fix and since WP Rocket and Woo Multilingual is used often, it might be a fix for a lot of users (potential users), some might have switched to competitor solutions already.

Could you make any progress; problems seem to be still there unfortunately?

We mean the backend menus just do not show up.

Hope things are going forward. Else, let me know and I can write them an email. Last update solved some issues on the frontend ate least. With Woo 3.0, however, now the Woo price filter totally is not compatible with WPML/Woo Multilingual anymore as it now only shows one main currency (base currency) even when switching the language.

Sure. And by the way, a viable solution should also take into account the standard Woocommerce price filter as it currently does not work, supposedly because it draws only from the base currency. Thanks.

Yes, I did. They will forward your concern to the relevant department/team. We are just the customers, but I told them that as many of their customers have asked for multi-currency feature in Dokan it is also in their best interest to resolve this. And it seems it is almost resolved, a couple of mappings. They say that they are just very busy with Woocommerce 3.0 integration. Just keep asking them to provide what you need to resolve it. Hope it will get resolved soon, then many of Dokan clients will also use WPML/Woocommerce Multilingual I assume.

Cheers.

Correction: “then he would click on WPML language switcher and pick UK English” should be and pick German.

Thanks for your feedback.

So Woocommerce must have a base currency, because taxes are paid in base currency. In the backend for the case that base currency, e.g. in EUR, is empty, then it will show on product overview.

Pls take for example again the seller in EUR and the seller in GBP. Assume seller in EUR sells in German market so he/she would click on Dokan seller dashboard – product, add price in EUR. Fine.

Now, take the British seller who sells in UK only so it makes sense for him/her only to add price for product in GBP. Then, EUR field stays empty. Now if he/she decides to sell the same product in EUR, then he would click on WPML language switcher and pick UK English, then add a product in EUR. Hence, the field in EUR is filled.

For us, we can add a conversion rate from base to all other currencies, but not the other way around if there is more than one currency, e.g. USD, GBP, etc. Because then, it is unclear which exchange rate to convert from USD – EUR or from GBP – EUR for the same product. It should in ideal Foreign Exchange markets lead to the same EUR price for any exchange rates, but sometimes there are discrepancies.

To answer your questions: If the seller puts in GBP in Dokan user interface/frontend and we fill in EUR, then there is a price in EUR that is shown for WPML language switcher German/EUR for example, but the price in GBP remains. It just allows the product to be shown for GBP and EUR. So setting the backend price works fine, but then that would not be a Dokan incompatibility issue anymore. For any regular price set in backend it shows the correct price in frontend. Only the Dokan seller who changes price change always the base currency, even if the GBP seller changes GBP product price. IN this case, in the backend he resets the EUR regular price and the GBP price adjusts automatically to this new EUR price.

Hope, it’s somewhat clear. I know it can be confusing so I am happy we don’t need to fully understand the code.

Thanks.

Cheers.

Hi,

Yes, the fields for the regular prices other than base currency are fine, but the mapping from the seller interface/dashboard is still incorrect. The latest update of Dokan 2.5.3 and Woocommerce Multilingual 4.1.1 resolved, however, all the currency discrepancies on the frontend. I.e. now switching languages shows the correct currency.

To explain the mapping problem:

Assume base currency is in EUR and another currency is in GBP. Regular price in EUR is empty and the field that Woocommerce Multilingual provides, i.e. the regular price in GBP is filled e.g. with 15 GBP. Then start with language German for example and switch to English, i.e. GBP, and go to Dokan seller dashboard – products – edit product. What happens now is that once updated the field for price of product in GBP, i.e. change from 15GBP to 17GBP. But then it maps this price of 17GBP into the regular price field for EUR and it shows up in the backend of products overview as price in EUR, i.e. it filled the regular price field in EUR, but did not change anything of the GBP price of the product.

This mapping problem must be resolved for dokan seller dashboard – shipping. There are 4 fields, where one adds prices/costs for shipping. These are “Default Shipping Price”, “Per Product Additional Price “, “Per Qty Additional Price ” and “Cost”. Hence, any viable solution must map these fields from GBP to GBP, from USD to USD. Currently, it is from GBP to EUR, from USD to EUR and so on.

You already resolved half of it. Please resolve the rest. And we can be happy again.

Thanks.

Hi,

To be honest: If choosing between investing time in solving a problem I already stated and need to state twice or just selecting an alternative product other than SOL that already works, I prefer to select the 2nd option.

Thanks.

Cheers.

Hi,

Sorry, I was wrong. The WP object cache was on. After turning it off, it did not work anymore. The plugin must be turned off. Please check this issue and improve.

Cheers

Hi,

Yes, I assume so. Well, the issue seems to be gone now, maybe due to last update of SOL. The behavior is irregular. I checked with IE and Chrome, but it happened in both. After each step I emptied browser cache, CDN cache and SOL cache. These are currently the only caches we use, i.e. actually SOL was deactivated. That is when it definitely resolved the issue.

When activating only cache and compression, it works fine now .
When activating only cache, compression and resource group, i.e. excl. minification it works fine.
When activating all, it works fine.

I hope it’s gone and we can reach SOL again. Else, I will let you know. Maybe you can test somehow and see different results.

Cheers.

Hi,

To give you guys some more info and maybe make the problem more easy to solve. It actually all runs down to the “regular price” in WC, i.e. the base currency. All other problems seem to be connected to it. Else, it almost works fine.

Problem: Theoretically or from an algorithmic point of view without looking too much into the code. A solution would be for example that as Woocommerce creates “Regular Price” field, WC Multilingual plugin creates additional price fields from the Regular Price field/base currency and fills them with conversion/exchange rates. Then Dokan must map the “Regular Price” for example in UK English/GBP into the WC Multilingual GBP field and not the EUR Regular Price field. You can check this going into Dokan Seller Dashboard, then Products and enter some price not in EUR (assuming EUR is set as base currency/default currency). It all updates into EUR. It should be a mapping problem. Please find a solution that is also compatible with all Dokan add-ons, else it will produce new compatibility issues. Once solved, please report to WeDevs/Dokan so that they can update their frontend.

Thanks a lot.

Yes, thanks. Works.