Hi Jim
Are you using any plugins e.g. geo my wp, which could prevent this geolocation triggering?
The geo location data is normally generated from the ‘location’ field once the job is published. Either something is blocking this, the field contents are invalid, or there is an error (server error logs may reveal more).
Thread Starter
jobme
(@jobme)
Hi Mike,
No, no such plugins. I only have the Autolocation for job manager that fills the location as the user types in – no other geo-type of plugins. Even if deactivate that, it still doesn’t work.
As plugins I have the following:
All your wp job manager plugins
The ones that were recommended by the theme (e.g. gravity forms)
A backup plugin
Follow up emails for woo commerce
Woo commerce checkout field editor
and an automated pdf invoice plugin
I don’t see any of those to be an issue as they have nothing to do with geolocation. You can check the website at http://jobmeup.gr
Feel free to post a job (it’s the first drop down on the third menu) and select wire transfer.
Unfortunately I have no access to server error logs but typically media temple (the host) would let me know if there is any issue.
> I don’t see any of those to be an issue as they have nothing to do with geolocation.
Actually, auto-location.. I know google has a request limit daily – do you have a lot of traffic? If this limit was reached it could prevent geolocation working. Did it stop working around the time you added that plugin?
> Unfortunately I have no access to server error logs but typically media temple (the host) would let me know if there is any issue.
I believe MT have something in their admin panel for viewing logs. They don’t notify users of PHP errors.
Thread Starter
jobme
(@jobme)
no way traffic is an issue (just me trying to develop the site). I have this plugin from day one, but I only recently noticed that ads don’t appear on the map. From what I understand given the fact that the two oldest ads only show on map, maybe the dates would fit. But turning it off, wouldn’t save the problem? Because i checked a lot of times deactivating it.
MT do have some logs that unfortunately just now enabled them. but I am chatting with them right now to check.
Do you suspect the auto location?
Try adding this code to one of your templates, e.g. theme footer.php:
$result = wp_remote_get(
"http://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 );
See what gets output.
Thread Starter
jobme
(@jobme)
actually it displays the exact code you sent me. should i have it inside a php tag?
Thread Starter
jobme
(@jobme)
stupid question before…
anyway, that’s the output:
array(5) { [“headers”]=> array(12) { [“content-type”]=> string(31) “application/json; charset=UTF-8” [“date”]=> string(29) “Wed, 27 Aug 2014 17:19:07 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 }
Thats it then – OVER_QUERY_LIMIT.
https://developers.google.com/maps/documentation/geocoding/#Limits
2500 is the limit. I suspect the plugin for guessing location is hitting this API too often and not caching results. To be sure, disable it and check again in 24 hours.
Thread Starter
jobme
(@jobme)
I disabled the plugin, added a new job and still doesn’t generate the custom fields. Or this is what you mean to wait for 24 hours regardless of the auto location plugin?
Yeah – you need to wait for tomorrows quota.
Thread Starter
jobme
(@jobme)
great…. let’s hope it works. As a general note, the site is only used by me with no more auto-filled test ads than 1 or 2 per day.
Truly appreciate your support once again…
Thread Starter
jobme
(@jobme)
It’s been nearly 24 hours with the same message there – that I supposedly exceed the daily limit. I came across this article: http://www.raymondcamden.com/2013/2/13/Getting-a-quote-error-with-Google-and-youve-barely-touched-your-limit where basically says to Turn ON API access. I certainly haven’t done that and have no clue where to do it. Is this something I should do?
Thanks
These requests are not tied to an API key so thats not relevant I don’t think.
Thread Starter
jobme
(@jobme)
Ok, way past 24 hours, definitely much more than the latest autocomplete plugin use but still says it exceeds the limit. Is there any case that the fault could be somewhere else?
Thread Starter
jobme
(@jobme)
And from the error logs, the only maybe valuable thing is that:
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] Accept: */*\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] \r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < HTTP/1.1 401 Unauthorized\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < Date: Thu, 28 Aug 2014 17:16:13 GMT\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < Server: tfe_a\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < content-type: application/json; charset=utf-8\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < strict-transport-security: max-age=631138519\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < Content-Length: 156\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < Accept-Ranges: bytes\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < Via: 1.1 varnish\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < X-Served-By: cache-tw-lax1-cr1-3-TWLAX1\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < X-Cache: MISS\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < X-Cache-Hits: 0\r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] < \r
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] * Connection #0 to host cdn.api.twitter.com left intact
[Thu Aug 28 10:16:13 2014] [error] [client 2.84.44.205] * Closing connection #0
