Hi there Alfred,
Initially I thought there was problem with updates done on backend side of bad_ip and that backward compatibility failed, but I found there actually was error on plugin side and that there was equal sign missing in request parameter..
Thank you for noticing this.
I’ve just released new version of plugin with work being done on bad query checking against bad_ip public database, and patched the unlist request formatting. If problem continue after update, make sure to clean page cache.
Did redesign bad_ip unlist page too, to better present information about unlist status in case when IP is not in database anymore.
I’ll add that there is scenario when you have blocked IP, then someone else issued unlist request and removed that IP from bad_ip database, but you will still have that IP in your report, so in that case if you send request to unlist that IP, you will get message with Status: No IP found for the unlist request
Thanks again for your productive comments
Regards