Huge issue with Geolocation

@jobme, as I was doing this in a test development site locally, I trashed the database and started over. Geocoding is working fine now so I suspect previously geocoded lookups were being cached somewhere. This may not be an option for you though if your site is live!

This might be useful for that https://pippinsplugins.com/transients-manager-plugin/

Transients for geocoding all start with geocode_

Hi Mike,

Me again! I’ve been setting up a dev site live online and I’m running into the same issue we had before – but this time my fix isn’t working!

My API key is valid since I can use it to call a geocode request in the footer as you suggested, but new jobs aren’t being looked up – the metafields just aren’t appearing. Is there any way of accessing logs so I can see what’s going on when the plugin saves the post and performs the lookup?

I’ve got

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

in my wp-config.php but I’m not seeing anything being generated. Would errors in your plugin show up here?

Just to rule out conflicts I’m running a blank install on a new database with only wpjobmanager installed.

Thanks,

James

Errors would yes, but it may not necessarily trigger an error if its the timeout thing (or its cached in a transient). If you want to add additional logging, do so around here https://github.com/mikejolley/WP-Job-Manager/blob/master/includes/class-wp-job-manager-geocode.php#L123

Hello guys,
I have the same problem, all meta geolocation do not fill up when I add a place for a job.
I tried to add an API key, but it still does not work.

Weird because everything works perfectly locally.

Have you any idea to solve this problem?

Thank you in advance,

Nac

@nastynac not at the moment, but by all means do some debug as suggested in this post. At least check if you’re hitting the limit, or if its just wp_remote_post related.

Hi Mike,

It’s indeed an error with wp_remote_post.

I have this message:

$result = wp_remote_get( "https://maps.googleapis.com/maps/api/geocode/json?address=california&sensor=false", array( 'timeout' => 5, 'redirection' => 1, 'httpversion' => '1.1', 'user-agent' => 'WordPress/WP-Job-Manager-' . JOB_MANAGER_VERSION . '; ' . get_bloginfo( 'url' ), 'sslverify' => false ) ); var_dump( $result );

But I don’t know how to fix it.

As @jobme, when I click on the location from my dashboard, it sends me to the good spot, but it doesn’t geocode.

What error did the above give you?

Don’t forget that when you add an API key to the string you need to use HTTPS! I fell foul of that.

I realized that the problem occurred when I did the plugin update because in local I use the old version and everything works fine without using API key.

I did a reinstall with a new database, but now no custom post geolocation field appears …

I do not know what to do now.

What do you recommend?

@nastynac What your local does makes no difference – the geolocation limits imposed by google look at the server making the request. What error did your wp_remote_post give?