cheers asbo - chips peas and gravy ty
Ive now abandoned trying to fix this with gmaps v2 as I understand this is now to be deprecated, it should still work but only up until next year. So Ive signed up for a new API key on gmaps v3 which should allow me more elements than what I had with my old APIv2 key .
Google maps doesnt have the best documentation for their API and because its relatively new theres not too much info about it on the web.
Believe it or not I wasted the best part of an hour yesterday with this from their
example codeSample code from their tutorialsrc="http://maps.googleapis.com/maps/api/js?key=YOUR_API_KEY&sensor=SET_TO_TRUE_OR_FALSE">
So what had I done wrong, why it wouldnt work? I put
src="
http://maps.googleapis.com/maps/api/js?key=YOUR_API_KEY&sensor=FALSE"
Why didnt it work.. because its case sensitive and should be
src="
http://maps.googleapis.com/maps/api/js?key=YOUR_API_KEY&sensor=false">
Does it say that in the API.. nope... yet they give the example in capitals! How god-damn stupid
Im only putting this out there in the hope that it gets indexed so that others dont waste as much time as I did with a rather vague error message. I literally banged my head on the desk when I found out what it was! Judging by the amount of problems out there with this one simple error, but nothing immediately showing the case sensitive solution.
Next problem, converting all the rest of the stuff to the new API format, and finding a way to pass some javascript results to php variables
(passing client side to server side cant be done straight off)