Hello @charlesbrewer,
I tried to access your site but the access is restricted by Wordfence, so I can’t test it directly.
You may want to make sure the site is publicly available (even temporarily for troubleshooting) with no restrictions so we can take a look at it.
Meanwhile, you may want to check our documentation about Google API and WP Job Manager. I’d like to make sure that the geolocation_lat and geolocation_long are always populated, so your map has something specific to use.
These settings are located in the bottom part of the Job edit screen in wp-admin. Screenshot here: https://cld.wthms.co/PfwWh3
When you enter a job location and save (or create a new job) it should pull these values from Google.
Hello,
We don’t seem to have those custom fields. However, it worked fine before, it not working has been a recent thing. We also have a staging website, where we also do not have these custom fields and it is working fine, though that still has version 1.35.3 of the WP Job plugin. Has something changed since then?
This is because the “remote” location search code they merged into the plugin now changes the location query completely.
Instead of just searching for the exact value you have “San Antonio, TX” it’s splitting it up into separate queries for each part of that wording “San” “Antonio” and “TX”
https://github.com/Automattic/WP-Job-Manager/blob/trunk/wp-job-manager-functions.php#L76-L92
So “San Antonio, TX” now becomes three queries “San” “Antonio” and “TX” .. which means that it’s matching on the “TX” value even when it’s not in San Antonio:
https://github.com/Automattic/WP-Job-Manager/pull/2261
Ooooh. Well that sucks. So how do I fix? I added our Google API code, it does have Geocoding API and it has billing enabled. I tried to to make a new job and I still don’t see those geo custom fields. Am I missing something else, and how do I update all the current jobs we have up as well? :/
Harder to do without the old plugin install 🙁
Hi @charlesbrewer –
This is indeed related to changes in the recent version of WP Job Manager. You can follow the GitHub issue here for updates on when this might be fixed:
https://github.com/Automattic/WP-Job-Manager/issues/2287
