ff kk

After a while trying….it turned out to be Cloudflare JS/CS options. They need to be turned off. Your plugin now works totally fine with Woocommerce. Thanks.

Hello, Do we have any news on this issue? Still not compatible…Thanks.

Hi,

Its nice that SOL gets more functions but the problem is that there will also be more potential for incompatibilities and it might get slower.

It did not work with CSS and JS minification on in SOL 1.3.2, i.e. the page did not load with youtube embedded video.

Thanks.

The latest update of Enfold improved the compatibility. NOw the only problems are that CSS and JSS minifcation don’t work with Enfold anymore as previously and that there are problems between SOL and youtube embeds. Maybe, you can take a look. Thanks.

Thanks. Don’t get me wrong. Your plugin is a great plugin. It is simple and effective. However, we already replaced it on 2 site with WP Rocket and want to keep it on this site with Enfold. Testing now 1.4.1, it still breaks the site. Nothing changed in SOL settings. It only works if we turn off all speed advanced optimization options, which then does not make sense anymore. Pls just check it with Enfold. We just wait, maybe next updates in SOl will resolve it. Maybe, I will then register a free account.

Hi,

in version 1.4 SOL now we have to disable the whole advanced optimization of SOL so it would work. Before version 1.4 we could enable all options in advanced optimization of SOL and it would still work fine.

Now in 1.4 SOL, we have to disable also the remove query strings option so it would work. If we enable any of these options, then unfortunately the screen is blurred – totally useless. I did not check the debug.log for errors as this is an obvious incompatibility with Enfold and version 1.4; if it persists we have to switch to SOL alternatives.

Thanks.

This issue remains unresolved even if WPML states it is fully Dokan compatible. Pls resolve this issue and make it really 100 % Dokan compatible. Right now, it still does not translate into the correct currency when adding a product and only filling out the non-regular price fields.

Thanks.

With update Woo 3.1 now the switcher does not work anymore. Switching language switches currency for a moment, but then goes back to only one currency for all languages.

Also the price filter does not show the correct currency at first load. We combined CSS in WP Rocket, which solved this issues, i.e. price filter shows correct currency at first load, but only in IE Edge. It broke the site in Mozilla for example. Pls make Woo Multilingual work correctly for the Woocommerce standard price filter and the Woocommerce Multlingual currency switcher.

Thanks.

https://www.ads-software.com/plugins/dokan-wpml/

Thanks. We are looking forward to it. Many WP users who decide for a payment solution working with Dokan will also be glad.

Nevertheless, checking the current situation: turning plugins on/off, it turned out that Dokan WPML is not compatible with the Mangopay plugin. It leads to a bug, where one cannot click the coupon and login window/link within the Woocommerce checkout screen.

Please take care of this; ideally in addition to some compromise on the Mangopay registration information for users as the buyers will add nationality, birthday at checkout anyway, but for checking out the marketplace this information seems a little too much. Often on other platforms it’s as simple as email and password for registration. It’s already quite difficult to match buyers and sellers, this would make it very very difficult. And no buyers and sellers, then there is no transaction, no KYC.

Hi,

I understand the KYC process: https://docs.mangopay.com/guide/kyc. It should be used for vendors, but I am not sure it applies to customers as well.

fripss has got a point. It makes on-boarding of customers much more difficult (on a marketplace). Nobody understands why he/she needs to provide birthday, nationality, living country to buy something. Yes, of course once payment is due they need to provide it, but to many this request of information seems scary. You know in what times we live: Wikileaks & Co.

For Dokan, once you make it compatible as you said with next update, it would be useful if you integrate Mangopay with the Dokan registration frontend, because currently First Name, Last Name appears twice. Once for Mangopay and once for Dokan vendors.

If you put in those extra-info only in the Dokan-vendor registration part instead of the customer registration part, then it is fine. Vendors will get that but not customers. Some customer just want to check out the platform before they buy, hard to check if one needs to register with all sorts of very personal information.

So please be so kind and adjust it in the next release. Highly appreciated.

Hi,

I understand the KYC process: https://docs.mangopay.com/guide/kyc. It should be used for vendors, but I am not sure it applies to customers as well.

fripss has got a point. It makes on-boarding of customers much more difficult (on a marketplace). Nobody understands why he/she needs to provide birthday, nationality, living country to buy something. Yes, of course once payment is due they need to provide it, but to many this request of information seems scary. You know in what times we live: Wikileaks & Co.

For Dokan, once you make it compatible as you said with next update, it would be useful if you integrate Mangopay with the Dokan registration frontend, because currently First Name, Last Name appears twice. Once for Mangopay and once for Dokan vendors.

If you put in those extra-info only in the Dokan-vendor registration part instead of the customer registration part, then it is fine. Vendors will get that but not customers. Some customer just want to check out the platform before they buy, hard to check if one needs to register with all sorts of very personal information.

So pls be so kind and adjust it in the next release. Highly appreciated.

Hope you guys make progress. By the way, using Query Monitor for debugging, it turned out that

there are duplicate queries:

WCML_Multi_Currency_Orders->get_orders_currencies()
2 calls
Plugin: woocommerce-multilingual
1 call
Plugin: woocommerce
1 call
WCML_Admin_Currency_Selector->set_dashboard_currency()
1 call
WCML_Admin_Currency_Selector->show_dashboard_currency_selector()
1 call

Maybe, something you could improve additionally if it is an issue…

The issue with the price filter was correct prior Woo 3.x and all connected Woocommerce Multilingual, WPML updates. Now if you sit in the UK or US, you might see it correctly. But sitting in Germany, we see the price filter showing EUR for English at first load. Once changing price range, it works correctly. Pls confirm it is a Woo Multilingual issue as we suspect. Pls resolve.

As users, we just hope you guys can solve this issue. Seems not to be straightforward. Also the Woo price filter is reacting slowly, i.e. only when you change price range it would begin to show correct currency. Else, when loading first time it always shows base currency. Might be connected. Thanks.