G’day Enfy,
The plugin does address lookups (geocoding queries) on the server side and stores the resulting coordinates in transients — temporary records — for up to 1 week. If it can’t resolve the address (e.g. Google can’t find it, or it has multiple results) then it lets the browser-side code try again. If it still can’t get a result, you get a pop-up alert in the browser
The Flxmap Ignore Bad Address add-on works by throwing away any maps that didn’t get a server-side address lookup result. If it’s throwing away all of the maps now, that means that the plugin isn’t getting address lookup results. If the maps work OK when you deactivate that add-on, it means the addresses are OK, so it must be something on the server.
I can only guess what’s going on, but maybe:
- you have added centre coordinates and address to the map, but the centre coordinates have the wrong format so it’s forcing an address lookup for every map
- you have a plugin that is messing up remote HTTP requests
- you have a plugin that is blowing up memcached and preventing transients from storing addresses, and your site is over the Google Maps API query quota
I’d guess that the problem is #1, but it could be #2. Can you provide a link to the website please so that I can see one of the maps in question?
cheers,
Ross