Google Maps API key message

monotonic

The Living Force
My browser gave me a message on the SOTT homepage today saying something along the lines of the API key for Google Maps was not accepted or revoked or something, and that the message should be given to the person who made it. I tried reloading the page to get the message to show up again but it didn't work.
 
monotonic said:
My browser gave me a message on the SOTT homepage today saying something along the lines of the API key for Google Maps was not accepted or revoked or something, and that the message should be given to the person who made it. I tried reloading the page to get the message to show up again but it didn't work.

The API key is valid, so it seems to have been a Google Hiccup (it's a new feature they just released).

I did have to give our "project" an official name when I visited the Google Developer's Console to see if anything was wrong, which was new. So, maybe something broke when they enabled this naming thing.

In any case, everything seems okay.
 
Mr. Scott said:
monotonic said:
My browser gave me a message on the SOTT homepage today saying something along the lines of the API key for Google Maps was not accepted or revoked or something, and that the message should be given to the person who made it. I tried reloading the page to get the message to show up again but it didn't work.

The API key is valid, so it seems to have been a Google Hiccup (it's a new feature they just released).

I did have to give our "project" an official name when I visited the Google Developer's Console to see if anything was wrong, which was new. So, maybe something broke when they enabled this naming thing.

In any case, everything seems okay.

FYI: I get this google message on certain topics as I read them sequentially from the home page of SOTT.
So far, I have had 5 pop-ups.

Google Warning message said:
Google has disabled use of the Maps API for this application. The provided key is not a valid Google API Key, or it is not authorized for the Google Maps Javascript API v3 on this site. If you are the owner of this application, you can learn about obtaining a valid key here: https://developers.google.com/maps/documentation/javascript/tutorial#api_key
 
dant said:
FYI: I get this google message on certain topics as I read them sequentially from the home page of SOTT.
So far, I have had 5 pop-ups.

Google Warning message said:
Google has disabled use of the Maps API for this application. The provided key is not a valid Google API Key, or it is not authorized for the Google Maps Javascript API v3 on this site. If you are the owner of this application, you can learn about obtaining a valid key here: https://developers.google.com/maps/documentation/javascript/tutorial#api_key

What are the specific URLs to the pages giving you the error?

I can't make the error happen no matter what I do, including opening 30 SOTT pages at once. Maybe it's a regional issue with certain Google servers?

ADDED:

Just to explain what this error message actually is all about:

A Google API is a chunk of code that lets you access Google services and use them on your web site, in your app, or whatever. For example, you can go to maps.google.com and use Google Maps. But, if you want to use a Google Map on your own web site, it's not free and unlimited because you're using a Google product on your site - not theirs.

Thus, many Google APIs require a key that is limited to certain servers or domains, so that they can track and limit usage to Google services. We use the Google Maps API for WorldView. We have our own API key that is locked to SOTT's servers.

If someone tries to use our API key on their server, they would see the exact error message some of you are seeing lately.

But, we have an API key, it's valid, it's locked to our sites, and we're well under our usage limits. Even if we go beyond our usage limits, it will still work, but we'll have to pay for the usage.
 
I have noticed this message a couple of times already. It doesn't always appear directly, for instance I just had it on the front page, but only after scrolling down quite a bit. I cannot reproduce it though...

Clipboard01.jpg
 
Hmm, I fixed one little problem... & is now &amp; in the URL string for the API <script> include tag.

Dunno why that would cause a problem only now, but who knows...
 
For the record, Mr. Scott, the same message that The Mechanic got, I just got on this article:

http://www.sott.net/article/290121-Was-CIA-torture-report-release-planned-by-the-CIA
 
Nienna said:
For the record, Mr. Scott, the same message that The Mechanic got, I just got on this article:

http://www.sott.net/article/290121-Was-CIA-torture-report-release-planned-by-the-CIA
It's a strange bug because when I try that link I don't get the message, although Mr Scott has changed something in the mean time I think...

Speaking of that, if this is the url you mentioned Mr Scott:

https://maps.googleapis.com/maps/api/js?key=AIzaSyDScrkzCvrYxXBl6aisHu_o7kHzgEDCA-0&amp;libraries=places&amp;sensor=false&amp;language=en

then it seems allright to me now. Escaping the & like that is necessary in html indeed. I've always found it kinda ugly because the url is in quotes anyway so there's no need to escape anything except quotes but I didn't design the standard, so..

Also, http://validator.w3.org/check?uri=http%3A%2F%2Fwww.sott.net&charset=%28detect+automatically%29&doctype=Inline&group=0 does return a few errors in the code but as far as I can tell nothing to really worry about. Worth checking out though.
 
I just realized that the Google Maps API was being included on every single SOTT page, which is quite silly. I did it that way for testing purposes when developing WorldView, but then forgot to limit when it was loaded when WorldView went live. :oops:

The API is only needed for a few editor-only pages, and publicly for all WorldView maps (which always load using a different, custom template, usually via an iframe).

So, now the API will only load when necessary. That should pretty much "fix the glitch", and improve initial page load times.
 
I just got the same message that The Mechanic received. It popped up seconds after the SOTT main page loaded.
 
Wow, this is getting annoying...

So, I generated a new API key, which now seems to have a different format and an expiration date (???).

I also modified the allowed web sites without using a wildcard for the subdomain, which some other users claimed had caused them problems with the Maps API in the past.

We'll see what happens now.
 
Ooookay, apparently the "sensor" parameter is also deprecated now, so I removed that as well...
 
Scotty,

Just go the google api message message when I clicked the back button after reading http://www.sott.net/article/290147-Cow-flees-slaugherhouse-in-Pocatello-Idaho
I navigated there from the sott.net home page

Running Safari 7.1 on Mavericks.
 
Back
Top Bottom