bluebananaconsulting

Hi Mike,

Was this filter implemented? I use wpjobmanager for a disabled charity, and the admins frequently post jobs on behalf of users. One of the admins uses a screen reader which is unusable with the backend!

It would be great to bypass the approval flow for logged-in admins via the frontend.

Thanks!

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

@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!

Thanks Mike, I really appreciate you taking the time to do this. It always amazes me the quality of work that goes into free WordPress plugins!

Cheers,

James

OK, I haven;t done a fresh install but I have been in contact with my host, TSOhost. We identified that an API key needs to be set because the API call limit was being hit by the aggregated number of calls coming from my cloud-based server.

I created and activated an API key and amended your test script you posted to @jobme. I know get a successful lookup:

array(5) { ["headers"]=> array(12) { ["content-type"]=> string(31) "application/json; charset=UTF-8" ["date"]=> string(29) "Tue, 09 Sep 2014 13:35:54 GMT" ["pragma"]=> string(8) "no-cache" ["expires"]=> string(29) "Fri, 01 Jan 1990 00:00:00 GMT" ["cache-control"]=> string(25) "no-cache, must-revalidate" ["vary"]=> string(15) "Accept-Language" ["access-control-allow-origin"]=> string(1) "*" ["server"]=> string(4) "mafe" ["x-xss-protection"]=> string(13) "1; mode=block" ["x-frame-options"]=> string(10) "SAMEORIGIN" ["alternate-protocol"]=> string(8) "443:quic" ["connection"]=> string(5) "close" } ["body"]=> string(111) "{ "error_message" : "The provided API key is expired.", "results" : [], "status" : "REQUEST_DENIED" } " ["response"]=> array(2) { ["code"]=> int(200) ["message"]=> string(2) "OK" } ["cookies"]=> array(0) { } ["filename"]=> NULL } array(5) { ["headers"]=> array(11) { ["content-type"]=> string(31) "application/json; charset=UTF-8" ["date"]=> string(29) "Tue, 09 Sep 2014 13:35:54 GMT" ["expires"]=> string(29) "Wed, 10 Sep 2014 13:35:54 GMT" ["cache-control"]=> string(21) "public, max-age=86400" ["vary"]=> string(15) "Accept-Language" ["access-control-allow-origin"]=> string(1) "*" ["server"]=> string(4) "mafe" ["x-xss-protection"]=> string(13) "1; mode=block" ["x-frame-options"]=> string(10) "SAMEORIGIN" ["alternate-protocol"]=> string(8) "443:quic" ["connection"]=> string(5) "close" } ["body"]=> string(1340) "{ "results" : [ { "address_components" : [ { "long_name" : "California", "short_name" : "CA", "types" : [ "administrative_area_level_1", "political" ] }, { "long_name" : "United States", "short_name" : "US", "types" : [ "country", "political" ] } ], "formatted_address" : "California, USA", "geometry" : { "bounds" : { "northeast" : { "lat" : 42.0095169, "lng" : -114.131211 }, "southwest" : { "lat" : 32.5342321, "lng" : -124.4096196 } }, "location" : { "lat" : 36.778261, "lng" : -119.4179324 }, "location_type" : "APPROXIMATE", "viewport" : { "northeast" : { "lat" : 42.0095169, "lng" : -114.131211 }, "southwest" : { "lat" : 32.5342321, "lng" : -124.4096196 } } }, "types" : [ "administrative_area_level_1", "political" ] } ], "status" : "OK" } " ["response"]=> array(2) { ["code"]=> int(200) ["message"]=> string(2) "OK" } ["cookies"]=> array(0) { } ["filename"]=> NULL }

So now I was wondering if I could modify your plugin file to test if this fixes my problem. (Not a good solution I know but just to test!) Could you help me format the string, since I’ve tried to make the change and new jobs and old jobs re-saved still aren’t geolocating.

I’ve changed the code in class-wp-job-manager-geocode.php starting at line 122 to add my API key before the sensor variable.

if ( false === $geocoded_address || empty( $geocoded_address->results[0] ) ) {
				$result = wp_remote_get(
					apply_filters( 'job_manager_geolocation_endpoint', "http://maps.googleapis.com/maps/api/geocode/json?address=" . $raw_address . "&key=AIzaSy+++API KEY+++SYPycYk&sensor=true&region=" . apply_filters( 'job_manager_geolocation_region_cctld', '', $raw_address ), $raw_address ),
					array(
						'timeout'     => 5,
					    'redirection' => 1,
					    'httpversion' => '1.1',
					    'user-agent'  => 'WordPress/WP-Job-Manager-' . JOB_MANAGER_VERSION . '; ' . get_bloginfo( 'url' ),
					    'sslverify'   => false

				    )
				);

As I say, this still isn’t geolocating jobs. How would you format the string?

Hi Mike,

I’m getting the same issue :

array(5) { ["headers"]=> array(12) { ["content-type"]=> string(31) "application/json; charset=UTF-8" ["date"]=> string(29) "Mon, 08 Sep 2014 20:09:21 GMT" ["pragma"]=> string(8) "no-cache" ["expires"]=> string(29) "Fri, 01 Jan 1990 00:00:00 GMT" ["cache-control"]=> string(25) "no-cache, must-revalidate" ["vary"]=> string(15) "Accept-Language" ["access-control-allow-origin"]=> string(1) "*" ["server"]=> string(4) "mafe" ["x-xss-protection"]=> string(13) "1; mode=block" ["x-frame-options"]=> string(10) "SAMEORIGIN" ["alternate-protocol"]=> string(7) "80:quic" ["connection"]=> string(5) "close" } ["body"]=> string(137) "{ "error_message" : "You have exceeded your daily request quota for this API.", "results" : [], "status" : "OVER_QUERY_LIMIT" } " ["response"]=> array(2) { ["code"]=> int(200) ["message"]=> string(2) "OK" } ["cookies"]=> array(0) { } ["filename"]=> NULL }

This is on a brand new install, with a new web hosting platform I’m trying out. There are only three jobs created. I did have Geojobmanager installed when I created the jobs, which I’ve now deactivated. I noticed jobs weren’t being geolocated which led me to this post.

Any idea why this might be happening?

Thanks,

James