Plugin issues?

Hi Thomas,

Thanks for the kind words — I’m sorry that you are having trouble with the plugin.

I maintain a couple of ecommerce sites that use my plugin with separate API keys, and currently neither of those are experiencing this problem. This leads me to believe that there is something amiss with your API key.

I’ve noticed that getAddress.io have revamped their pricing options since I last looked at their website, which pricing tier (if not Free) are you using with your API key please?

Thanks,
Gareth.

Hi GazChap,

I’m also hitting this same issues. The API key works fine and been testing using a direct call to the API on getaddress.io however it doesnt seem to work with your app.

I have had it working before however it seems upgrading to woo commence version 8.1.1 has stopped it working? It seems that the plugin is also not tested on the new version of wordpress. 6.3.1

• This reply was modified 1 year, 1 month ago by johnlopez0987.

I’ve been testing on my test environment, which is running WP 6.3.1 and WooCommerce 8.1.1, and everything works fine.

I am using an API key that, at this point, is a few years old. I’m wondering if it may be an issue related to new keys, perhaps under their new pricing model.

I’ll try it with a new account and see if I can replicate the same issue.

I just tried this with a brand-new API key and have confirmed that the issue occurs for me now. Switching back to my old account API key stops the issue occurring, so it must be related to new API keys.

I will look into this and resolve as soon as possible.

Thanks for the update Gaz.

I’m running with the free version currently, I will be switching to paid service once al up and running. The Keys seem to work fine when you call direct:

https://api.getAddress.io/autocomplete/{Postcode}?api-key={apiKey}

If you can let me know when you have a published fixed i can then continue using your app. Which is a great app!

• This reply was modified 1 year, 1 month ago by johnlopez0987.

getAddress support have confirmed that the API endpoint that I use in my plugin has been phased out as of last week, and that any new API keys created since then will not work in the same way.

I have the information that I need to fix it up in my plugin, I’ll aim to get this done over this weekend!

Hi both,

I’ve just released a v3.0 update to the plugin which rewrites the lookups to use the new getAddress.io API instead of the old one.

The new API is usable by both “new” API keys and legacy API keys, so should be backward compatible with older API keys.

Note that test postcodes (those that do not count towards your API usage) do not appear to be supported any more, so I’ve removed references to those.

I’ve also added a custom database table to store lookup results for 24 hours, in addition to the caching done by the JavaScript, to help minimise API usage.

Thanks for your bug reports! Please update and let me know here if your problems are resolved!

Cheers,
Gaz.

Gaz, Update seems to be working. Thanks for the quick turn around on this.

Thanks for the confirmation, and no problem!

I’ll mark this as resolved.

Hi Gazhap

Thanks for the fix, it works like a charm. And sorry for the late heads up, great work, appreciated ??

You’re welcome, Thomas!