gazchap

Apologies for the delay, I’ve been away! This error was caused by a similar issue to the previous one, I’ve fixed this in 3.2.3 which I’ve just pushed.

However, can you clarify if postcode lookups are still NOT working for you? If so, then before I mark this as resolved I’d like to get to the bottom of what’s happening with your specific case.

Apologies for the delay responding to this, I tried replying while I was away on vacation last week but it clearly didn’t work.

Anyway, I’ve just pushed a minor update (v3.2.2) which should fix this error, at least in the sense that the error itself shouldn’t cause the plugin to fail and write an error to the error logs.

As to why the error was generated in the first place, are you sure that the API key/domain token in your plugin settings is correct and has not expired?

Adding some custom CSS is the way to go here — I did apply some styling of my own in the plugin to try and correct this alignment issue but it doesn’t always work depending on the theme.

Thanks for letting me know!

Does that “Apartment/suite” field appear on the checkout? It doesn’t seem to be in the first screenshot you posted.

Yes, you will need both address line fields to be present in order to capture the address as returned by the plugin.

Thanks for the kind words! Glad you find the plugin useful ??

I have to admit, the existence of these Checkout Blocks has completely passed me by. I’ll take a look at this on my test install and see if I can figure out what’s required to make it compatible.

Thanks for the report.

This undefined array key error is now fixed in an update to 3.2.1.

I’ll fix the error with the undefined array key ASAP, but that in itself would only be an issue if there was an error being returned from the getAddress.io API I believe — can you contact me at gazchap [at] gmail [dot] com and I can help diagnose this further?

Depending on my availability, within the next week or two — I’m in something of a state of flux, currently!

I can add this as an option, yes. Leave it with me!

Very strange. I’ll look into it, but I’m at a loss initially.

As far as I’m aware the only reason my plugin would automatically deactivate by itself is if WooCommerce is deactivated at any point.

Does WooCommerce also deactivate?

I don’t have a firm timeline for that I’m afraid, it’ll just be “when it’s done”.