OneGuyFromBarlick

Random popup box with the following text:

The key provided is not a valid Google API Key or it is not authorised 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: http://code.google.com/apis/maps/docume ... aining_Key

There is an OK box which clears the box but it re-appears from time to time.

Seems to be present when you first access the site on the portal page before login but can appear at any time on various pages I have visited.

Current browser Firefox 9.0.1

Will try it in Google Chrome and post if same.

I've just implemented a google map on the homepage "Portal", thats why it was throwing up that pop-up, it shouldn't appear anymore...(hopefully)

It's fine in Chrome (where I am now). i'll logout shutdown Firefox and try a relaunch. I will post again if nesc. Cheers

-------------------------------------------------------------------------------------

Applet working fine now in Firefox and Chrome. A nice touch Doc..

Happening today in Firefox ..

I had it on my first log in 09.00hrs, but not since

Discussing this error in the Admin thread. Doc should pick it up at some point.

every page load since yesterday

Manifests itself on first visits to new pages and of course it has a major effect on the presence (or not) of the Google Map on the portal page.

I saw the message for the first time this morning when I logged in via the Active Posts page but not on any of the subsequent page openings. I next viewed the site just now (about 5.00pm) via the Active Posts page (not logged in) and saw this thread so I opened the Portal Page and I got the message. Opened the Portal again twice and got it each time. Then logged in and tried. Same behaviour. But nothing with other pages.

Has it gone?

for good?

Not by my reckoning, if you open threads that have not been visited recently it manifests on every page. It's getting to be quite irritating as if you open multiple tabs such as running down all the unread items, it jumps from one to the other until you have OK'd every error box.

I saw it once yesterday, but not yet today.

I get it occasionally. Not a big hassle just an annoyance.....

definitely still here, on every page again

I only get it once a day. Could it be that lack of adverts due to being a donor cuts the incidence down? Try donating and see whether it improves things.....

Still got it, it seems to appear on forums with photos

The problem will not go away until the site is updated with a new API key. The error will manifest itself on any pages that have content or background tasks running provided by Google, such as analytics or the Google map on the Portal page. It manifests as a transient error as acknowledging the error box will then allow you to browse the page. Any background tasks that need the key though will have been disabled.

I've mailed Doc but I know he's busy at the moment.

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/docu ... aining_Key

Yes,I usually if not always get the above message, but only on OGFB site. I have Firefox v 13.0.1 on Mac computer, with AdBlockPlus and Ghostery apps installed.
It is irritating!

Graham

Donate to cut the incidence down as adverts vanish. Then put up with it until Doc gets back on line and gets round to fixing it. He's just flit so he's thronged.

As an FYI it appeared on my blackberry too

API thingy appears still from time to time, on one page firefox tells me that its waiting for maps.googleapis.com ( think I have remember link correctly as its stopped/stopped waiting ), hope that helps towards tracking the naughty link down.

While I was doing some house keeping on the site I stumbled across a small piece of programming code that I think was responsible for the google API key warning message. I removed the offending code and hopefully it should not be appearing again. (Fingers crossed)

Brilliant Doc, it has gone.

I sincerely hope this is the Final Solution! (And I've not been really bothered by it....)