• Resolved Tony G

    (@starbuck)


    On the Search page, the map displays the location based on the selected Geolocation API. Frequently, different services will be able to resolve an IP where others will not. So the search pattern here is:

    1) Select the first API
    2) Click Search Now.
    3) Scroll down past the Whois info to the map.
    4) Note that the location was not found, so the map is focused on 0.0/0.0.
    5) Select the next API.
    6) Go back to 2 and repeat until an accurate map is found.

    That seems to be a waste of time.

    I think it would help a lot if (optionally) the plugin could query all of the active services, and then display the map only for the first service that doesn’t return 0.0/0.0 coordinates.

    It’s good that the API ID remains selected when we go back to the page. I’m not sure if that’s an accident but it would be nice to know if it was intentional. I hope that remains the default if it is not set to do this loop of queries. But if this new feature is active, and each API in the list is queried, it doesn’t matter which API is pre-selected, we only care about the last one.

    As an added bonus, it would be helpful if a count could be stored for each API, incremented each time it finds a non-zero lat/lon. Then rather than going through the list in the default order, it can go through the list in the order of the most-successful service to the least successful. This will reduce the number of queries, and thus reduce rendering time for that page.

    Finally, as another “bonus”, please set the Whois section to remember its collapsed/open setting. Note that in step #3 above we need to scroll past that all the time to see the map. Personally, I often don’t care about the Whois info, I’m just interested in the map. So I’d rather not have to scroll over it all the time.

    Arigatoo!!!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi Tony,

    Thank you so much for your good proposal many times!

    I’ll try to achieve all of them.

    One thing about:

    As an added bonus, it would be helpful if a count could be stored for each API, incremented each time it finds a non-zero lat/lon.

    The DBs on local server (Geolite2, Maxmind and IP2Location) don’t have latitude/longitude information unless you download city DBs using custom filter like ip-geo-block-maxmind-zip-ipv4. On the other hand, all the REST APIs have them.

    So if we can choose multiple APIs and the map is centered with non-zero lat/lon, I think it’ll be OK.

    Anyway, please give me for some time.

    Thanks again!

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi Tony,

    I implemented the following 2 functions:

    1. The Whois section remembers its collapsed/open setting.
    2. Mutiple IPs in the table can be selected accross the pages for bulk action.

    I’d appreciate you if you download the following js and replace it with the original one.

    https://raw.githubusercontent.com/tokkonopapa/WordPress-IP-Geo-Block/3.0.15a1/ip-geo-block/admin/js/admin.min.js

    I hope this can help to accelerate your workflow a bit.

    Thanks.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi Tony,

    Almost all your requests have been implemented in the new version 3.0.15.

    Please refer to the new filter hooks ip-geo-block-logs[-preset] and update your drop-in-admin.php. It can add a new UI of preset filter to make analysys of logs easy.

    new UI of preset filters

    Thank you as always!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Request: Auto-Search Geolocation API for Map’ is closed to new replies.