Location search doesn't work

[subforma]

Hello 😉

It is not disposable issue. All new event don’t work 🙁

[Brook]

Oh no! That is a big problem.

In order for that field to be blank in your database, something has to be preventing it from being written. Your server likely lacks a connection to Google when you create the venue. If the server itself can not contact Google Maps while the venue is first being saved, then it will not be able to get the Latitude and Longitude.

Is your website server on a shared IP? If so it is possible that Google has limited your servers IP from making Google Maps requests. It limits all IPs to 12000 a month. And shared servers frequently go over this limit, as do other shared IP setups.

If you run the PHP portion of this relevant articles code on your server, and do the print_r($loc); as outlined, what happens? Do you get a proper latitude and longitude, or is there an error along the way?

I really appreciate your working with me on this Subforma. I know it has taken us a while to get the problems isolated and communicated to one another. Please let me know what happens, and if you have further questions.

Cheers!

– Brook

[subforma]

This reply is private.

[Brook]

For sure! Try creating a new file on your server. Perhaps create a file named “gmaps-test.php” in your root web directory. Paste this inside of the new file: http://pastebin.com/xsNvZp1F

Assuming that is in your root directory, you can then visit yoururl.com/gmaps-test.php. It is likely the page will just say “null” or some kind of error. In which case we have confirmed that Google is blocking your IP.

What was the result of that test?

– Brook

[subforma]

I made it 😉

file:
http://informator.org.pl/wp-content/uploads/2015/02/phpfile_1.jpg

place on sever:
http://informator.org.pl/wp-content/uploads/2015/02/phpfile_2.jpg

and result:
http://informator.org.pl/gmaps-test.php

[Brook]

Alright Subforma. Thank you for doing that! We have finally isolated the problem, and confirmed it. I am seeing this error message right now, which leaves no ambiguity:

You have exceeded your daily request quota for this API

The only good option at this point is to switch servers. If you switch to another shared server, you will change IPs. And the other IP might not be facing quota limits. However that’s not guaranteed. To be guaranteed that you are not facing those limits, you want an IP unique to your site. Most VPS plans have a unique not share IP. If you switch to one of those you should again not face issues.

You can also pay Google to increase your quota, and modify our application to use an API key. But that will cost you time and money, when it is likely much cheaper for you to just upgrade your server to one that does not share an IP. Plus, you will get a better/faster website if your upgrade your server.

Does that make sense? Will one of those options work?

– Brook

[Brook]

Since this topic has gone for a spell without an update I am going to archive it. If you do need further assistance, please feel free to open another topic. We would love to help.

– Brook

[Author]

Posts