Error OPC 316

[atrus80]

Hi Stan,

Pls find attached error picture after installing latest OPC 316. For now we have switched back to OPC 311 which was the version we had before.

Looking forward to your comments.

Rgrds,
Chris

[admin]

Hello Chris,
you always must go to the configuration and click save, so any missing variables are saved into the configuration file even when they are empty. This error was caused by a missing configuration variable.

I will soon release 317 which fixes some other less important notices + a die statement in case no country is used.

Stan

[atrus80]

Thanks for the info Stan. We have now installed OPC 317 and it's working ok.

However we noticed the following: with OPC 317 our customers with EU VAT ID are being charged with tax now which is wrong. I guess there is some change in the EU VAT system which causes this issue?

Chris

[admin]

Hello, yes, please select which field is configured for VAT at the tax field. It does not have to be euvat id if you allow an incorrect VAT numbers. For example the VM js VAT validation sometimes fails for HU and RO VAT numbers. For this reason now using type "euvatid" in shopper fields is now optional.

You can also set up your home VAT prefix which will always be charged VAT.

All of this is within the Tax tab in the latest releases.

Best Regards,
Stan