Location Tools: Migration and Repair
Overview
WP Job Manager Geolocation 3.0 stores indexed job and resume locations in WPGeo location storage. The Tools tabs provide two different maintenance workflows:
- Scan for Missing Job Locations or Scan for Missing Resume Locations repairs missing indexed locations for existing posts.
- Location Upgrade performs the one-time migration of the legacy
places_locatorrows used by version 2.3.3.
These tools have different purposes. The repair scan examines current WordPress posts. The versioned migration copies the legacy location table as migration data, including rows whose posts no longer exist.
Scan for missing locations
For jobs, go to Job Listings → Settings → Geolocation → Tools and use Scan for Missing Job Locations.
For resumes in Pro, go to Resumes → Settings → Geolocation → Tools and use Scan for Missing Resume Locations.
The scan:
- processes the selected post type in small AJAX batches;
- leaves an existing indexed WPGeo location unchanged;
- reuses WP Job Manager latitude and longitude metadata when coordinates already exist;
- reports imported, skipped, and failed records in the progress panel.
Geocode locations missing coordinates
This option is disabled by default. Enable it only when posts have an address but no usable coordinates and you want the tool to call the configured geocoder.
Geocoding requests can consume quota and incur Google Maps Platform charges. The tool geocodes only when the option is explicitly selected for that run.
Location Upgrade
The Location Upgrade panel appears in the Jobs Tools tab. While the 3.0 migration is incomplete, it processes job and resume legacy rows together and displays the saved progress. After completion, it displays the completion message instead of the runner.
The migration:
- copies every valid legacy location row into WPGeo location storage in bounded batches;
- does not require the related job or resume post to still exist;
- does not geocode addresses;
- retains supported legacy location metadata;
- does not modify or delete the legacy table;
- persists its cursor and retries safely after an interruption or failed batch.
The legacy table is retained for rollback safety, but it is not a complete backup of the website. A reliable rollback requires restoring the matching plugin files and database backup together.
Automatic migration
After upgrading from 2.3.3, the plugin automatically processes one bounded legacy-location batch during each eligible page request until migration completes. This avoids attempting to migrate a large table in one request.
Administrators see a warning while migration is pending:
WP Job Manager Geolocation is still migrating existing locations. Location-based search results may be incomplete until it finishes.
The notice disappears automatically when the migration completion marker is written. It does not need to be dismissed.
Finish or resume manually
- Open Job Listings → Settings → Geolocation → Tools.
- Find Location Upgrade.
- Review the migrated and total row counts.
- Click Finish / Resume Migration.
- Keep the page open while the progress runner processes consecutive batches.
You can click Pause and resume later. If another request owns the migration lock, wait briefly and resume rather than starting overlapping runs.
When finished, the panel displays:
Location migration is complete. Existing legacy locations were left intact for rollback.
Verification and rollback
Before upgrading a production job board, create a complete file and database backup and test the upgrade on staging.
After migration:
- Confirm that the migration notice has disappeared.
- Run a location search with a known job and verify its distance and marker.
- Open a single job and verify its map.
- In Pro, repeat the search and map checks for resumes.
- Use the missing-location scan only if current posts still lack indexed locations.
- Clear page, object, and CDN caches before the final public test.
If you must roll back, restore the complete pre-upgrade database and the matching 2.3.3 plugin files. Do not delete WPGeo rows or the legacy table manually as a substitute for a tested backup.