erubbereu

Hello all,

The same problem occurs on 2 of our websites on which we use both Yoast SEO & WP Super Cache.

Indeed the bug still occurs as explained above by OP after the latest updates. And those 2 issue tracker links provided by @maybellyne give a 404 error. There are 2 threads (including this which also provides a php profiler) currently referring to this issue, and they are both marked as resolved.

Is your team aware of the problem? If so, do you have any estimation as of when this will be resolved?

Thank you.

@books1001 So the problem should be related to the WC 4.5 update. Not related to Table Rate for WooCommerce by Flexible Shipping plugin. We do not use this plugin but we also had the same problem after the WC 4.5 update.

I believe the WC developers should fix this on the next update.

• This reply was modified 4 years, 2 months ago by erubbereu.

Hello,

Can you check if the same issue applies to the following cases?

During checkout…

1. Select a country such as United Kingdom, Russia or any other country which supports the State/County field. Fill in all details, then check if shipping cost is calculated and appearing as before.

2. Select a country such as France or Germany (these countries do not support the State/County field.) and check again if the shipping is calculated and appearing.

I believe this problem is related to the latest WC 4.5 update and is somehow related to coutries that do not require or support the State/County field during checkout.

I’ve just patched the new version and can confirm that your fix resolved the issue.

And yes, you are correct about this.

Showing the country name, and the correct VAT country code in the raw response, will avoid confusion with countries, like Greece, which have a different code in the ISO system than the one used for VAT validation.

At least this was the case with us. We had to look into the log files to see that in fact the country code is correct.

Looking forward to the version including this tweak. You may mark this thread as resolved.

Again, thank you very much for the great support!!

That’s great news and I have to thank you again for the fast procedure.

We wouldn’t even consider using another alternative as we are very happy with the overall performance and functionality of WooCommerce EU VAT Assistant.

Okay, thank you.

If you manage to find a fix please let us know.

Understood,

Thanks for pointing that out.

We also found it strange that suddenly the plugin stopped validating VAT numbers although the VAT numbers were validating on the VIES webpage. We have faced similar situations in the past, but both the VIES webpage and the Plugin were not working.

So should we just wait for the VIES service to get activated again and stop rejecting request?

Hello,

Thank you for looking into this, please let us know if there is any service issue.

Until then, I guess we shall wait and try again later to see if the problem persists.

We will let you know if we have any more clue. Thanks again for your time!

On the debug log the following entries are shown:

[2020-03-19 12:12:18] wc-aelia-eu-vat-assistant.DEBUG: VAT number validation request. {“Request Arguments”:{“countryCode”:”EL”,”vatNumber”:”079212922″}} {“process_id”:986}
[2020-03-19 12:12:18] wc-aelia-eu-vat-assistant.DEBUG: VAT number validation complete. {“Country Code”:”EL”,”VAT Number”:”079212922″,”VIES Response”:false} {“process_id”:986}
[2020-03-19 12:12:18] wc-aelia-eu-vat-assistant.ERROR: EU VAT Number could not be validated due to errors in the communication with the remote service. {“Raw response”:{“valid”:null,”company_name”:null,”company_address”:null,”errors”:[],”raw_response”:null}} {“process_id”:986}

So, the countryCode should be correct. Can you advise what is the problem?

Hello, This is currently a problem with WPML Multilingual.
Check here

Hello,

This is currently a problem with WPML Multilingual.
Check here

Hello,

I also face the same problem with WPMail SMTP and Google Analytics Pro plugin.

Versions:
WordPress: 4.9.6
WordPress MS: No
PHP: 7.2.6
WP Mail SMTP: 1.2.5

Params:
Mailer: gmail
Constants: No

Debug:
There was a problem while retrieving Mailer for gmail: Could not json decode the token

When deactivating Google Analytics PRo plugin everything works as expected. No errors and mails are sent normally.

Can you please tell me how did you managed to solve the issue? Do we need to rename API classes names by hand? Should we wait for 1.3.0 version to be released?
Do you approximatelly know when 1.3.0 version will be out?

Regards, Othon