Troubleshooting: map pins and radius search

Coordinates are looked up in the background after a job or resume is saved, so a pin never appears at the moment of saving. The job map shows jobs that have coordinates. See Job map.

A job has no pin on the map

Cause. One of these:

• The job has no Location term, or its only location is a word such as “Remote”, “Anywhere”, “Hybrid” or “Work from home”. These jobs are skipped on purpose.
• The background lookup has not run yet. It runs through Action Scheduler when it is installed, or WP-Cron otherwise, so a site with WP-Cron disabled and no other runner never looks anything up.
• The lookup failed. A failed lookup leaves the job without coordinates and shows no error.
• The map provider is Google Maps or Mapbox and its API key is empty or wrong.

Fix.

1. Edit the job and check it has a real place in Location.
2. Make sure your scheduled tasks run (a real cron hitting wp-cron.php, or Action Scheduler with a runner).
3. Under Settings > Integrations, check the provider and key. Use Leaflet / OpenStreetMap to test, since it needs no key.
4. Save the job again. Saving queues a new lookup for any job that has no coordinates yet. A job that already has coordinates is looked up again only when its location changes.

Old jobs are missing pins after an upgrade

Cause. When you upgrade from an older Pro version, a background sweep looks up published jobs and resumes that have no coordinates, 25 at a time, with a pause of about 1.1 seconds between lookups. The pause keeps the sweep inside the free OpenStreetMap limit.

Fix. Wait. A large board can take a while. On Google or Mapbox you can shorten the pause with the wcbp_geocode_throttle_us filter (microseconds, default 1100000).

The place search box says “Too many location searches”

Cause. Each visitor IP address can run 30 new place searches per hour. Searches for text that was looked up recently are answered from a saved result and do not count.

Fix. Wait and try again, or raise the limit with the wcbp_geocode_rate_limit filter. Return 0 to remove the limit.

The place search finds nothing

Cause. The provider found no place for that text, or the lookup failed. The failure is remembered for an hour, so the same text fails the same way until then.

Fix. Try a city name or a fuller address. On Google or Mapbox, check that the Geocoding API is enabled on your key.

Radius search returns no jobs

Cause. Radius search only matches jobs that already have coordinates. The radius is in kilometres, from 1 to 500, and defaults to 25.

Fix. Check that the jobs you expect have pins on the map, then widen the radius.