aovivo

Hi Tim,

unfortunately the EU has overturn the “Privacy Shield” deal – including ‘safe harbor’ extension, as per decision made on the 16th July 2020.

As I understand (from the point of view of CJEU) the US government cant and wont be able to serve an “adequate level of protection” of user data compared to the GDPR.

That means NONE of the collected data of any EU-Customer is allowed be sent to any US server…

What is your response to that?

thanks in advance
Pedro

@mouli
Thanks for getting back.
Good to know that is it simply not possible with the current WooCommerce version.

For me, it it a logical step, but I understand that most of the stores work the way it is right now…
I guess there are a lot products that are simple and natural in their first variation – think of a loaf of bread that you buy in the bakery which is naturally and in its basic version uncut, but if the customer wants it, the service is offered by request.. or there are even loafs of bread that are already cut, because a majority of the customers cut them anyways (but maybe dont have a professional cutter at home to do so)…

I wish this was an option in the future, maybe as a filter, do change that behavior.

that said, thanks for understanding and getting back.
my best regards and keep up the good work!
aovivo

@mouli
I am not sure I understand. Why would I want to remove the grind attribute? wouldnt this remove all ‘grind’ options for my 2nd level variations? thats not what I am looking for.

Again:
I have 1 product, with three 1st level variations (250g, 500g, 1000g),but only one of them is to be grinded (lets say there only exists a 500g that is grinded).
All other variations (250 g, 1000 g) can be purchased as whole beans only (not grinded) – and therefor would not need to display that line of variation.

If this is not possible at all with WooCommerce, than so be it… I just thought – why displaying a line with a 2nd level variation/attribute if it does not exist for that product…

@eastofwest
Wow, thanks for the efforts.

The scenario you are describing is exactly what I already have.
What I want is, the second variation (the whole drop-down menu) NOT to show at all…

View post on imgur.com

why I want that:
first, it makes immediately clear, that there is no option at all (although I can have a preselected ‘unground’)
secondy, it does bloat my pdf invoice, since it is adding an extra line that is not needed.

For that I probably have to point out, that the standard ‘state’ of my coffee is ‘unground’/ whole beans, since most of the customers grind their coffee themselves.

hope I could explain.

Thanks again.
Regards
Pedro

yep, same here – WordFence finds that view.php belongs to an ‘old’ “Loco Translate” version “2.4.0

Didnt solve with 14.0.3 for me either. I am still running WooCommerce 3.9.3 though. However, I disabled most of the plugins, except WooCommerce…

14.0.2 didnt work for me either..

Same here with Version 14.0.1

@murlyn
Yes, its the ENFOLD theme and they offered a fix after a while… however they are taking a bit longer than usual since they promised a quick update of the theme including other fixes whereon I am waiting for.

its an error in the woocommerce-mod-.js – file.

You would need to replace it – check here: https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_7_4/woocommerce-mod.js

Hi Mohit,

thanks for the quick response.
As I stated in my post, I rolled out any plug-ins conflicts by deactivating all but WC.
I also changes to standard theme, no luck either.

I just moved a copy to a different host and different php-Version, same problem there…
I keep digging – unfortunately there is no ‘specific’ error to find in a log…
I just cant add a product from a grouped product to the cart…

regards
Pedro

Hi there – in my case it seems to be a bit different.

The hint was here: https://bugs.php.net/bug.php?id=72198

So what basically solved the problem for now was the separately compilation and linking of libiconv.

But I will also look into the bug you pointed out – however, the used username does apply to the issue…

thanks again for your input – hope this helps somewhere/someone else…
I will update this if anything else strange occurs, though…

my best regards
Pedro

I did rate, thanks.
Looks like Chrome is more sensitive in this case concerning extra characters, since the other big browsers I checked(IE, Opera Firefox) display the sorting correctly, despite the extra characters. Anyhow, I will check the tables in future like you suggested. have a great weekend!

MEISTER! looks like it did the job. How could you find this so quick? I guess I will encounter those type of errors now and then, so it would be great to know how you do the magic! ??

I guess you just earned yourself a beer!

I see the error in Chrome and Opera, but the sorting still seems to work on IE and Firefox… can you confirm?

Could this be related – https://github.com/woocommerce/woocommerce/issues/23694 ?

YES – same issue!
I run three larger WC shops for more than 5 years now. The issue has never been there! no tax calculation or whatsoever needed to be changed… in fact it was totally exemplary and accurate compared to other shop systems…

so I hope someone can locate the error.
thanks in advance
Pedro