Question

Photo of Jim Michael

0

API error when using Chrome on OSX

7

I'm sure it's just something misconfigured in my browser, but when I access Rock beta via Chrome (33.something) on OSX (10.9.2) I get the following popup constantly:

Does anyone know what I need to modify to stop this? I don't see the same via Chrome on Windows.

 

  • Photo of Jim Michael

    0

    Ok, there's a bit more to the story... last week I thought I had this working by enabling the static maps API, but today I logged in and BAM, there was the error again. Determined to find out what was happening I logged back into the google code portal with the intent of verifying my API key once again... when I noticed the "Referers" entry for our key... which is *.wcrossing.org/*.

    Then it all made sense... I typically access my Rock dev box via its short name of http://rockdev, even though its full name is http://rockdev.wcrossing.org. When accessed via the short name of http://rockdev, the referer isn't valid and I get the error (Google thinks some other domain is using my key.) Adding to the confusion all along (and completely explaining the seemingly random nature of this error), when I would HAPPEN to click the Rock logo in the upper left of my site to go to the homepage, it would turn into http://rockdev.wcrossing.org, and of course the API error would go away.

    Wow, that was a long way around the barn, but at least I now know how/why that error was occurring and how to fix it!

  • Photo of Jon Edmiston

    1

    I had this happen once before. You might check your Google API key (Admin Tools > General Settings > Global Attributes > Google API Key). If the key is not valid you'll get that message repeatedly. You might try blanking it out. If that works confirm that your key is correct. We'll need to find a way to key this from happening even if the key is invalid.

  • Photo of Jim Michael

    1

    This ended up resolving itself. Hadn't tried it in a couple of weeks, but without changing anything I tried again today and the alerts never popped up. Trey thinks it might have been a timing issue after initially creating the API key as he saw something similar.

  • Photo of Jim Michael

    0

    Thanks Jon. You are correct that we had a Google API key entered I was unaware of (my webdev has been messing around ;-) ) and it IS valid, but for some reason on my install of OSX it pops up the error. And it's not just in Chrome... Safari provides the same error. Yet my developer has no troubles with either browser on his install of OSX, so it must be something Google doesn't like about my machine I'll have to investigate. At least it's clearly not a Rock issue at this point!

  • Photo of Adam Mosley

    0

    Same issue here. I will update if it resolves after time. Otherwise, I would love input from others.

  • Photo of Jim Michael

    0

    Ahhhhh! This just started happening again... this time on FireFox in Windows.

     

    This same browser has been used to access our Rock site without issue for months without anything changing in the Google API setting... but I *did* do one thing that may have caused this: I wiped out all history and cache on this browser (for other reasons) a few hours before logging into Rock and getting this error (which occurs with just about every new page I nav to within Rock.)

    Not SURE it was due to the cache reset, but it sure was coincidental if not (and if it was due to the cache reset, I have no idea why this happens or how to fix it.) I guess I'll just have to wait and see if it "goes away" again like it did the first time I saw this.

  • Photo of David Turner

    0

    FYI, I'm able to reproduce this if I specify an invalid Google API key in Rock, or the the key is not configured with the appropriate services turned on...

    2014-06-19_103956.png

    Rock needs the Javascript API and the Static Maps API enabled.  Have you enabled both of these for your key?

    • Jim Michael

      Jim Michael

      Bingo! We had Google Maps JS API v3 enabled, but not Static Maps API. Flipped that and the error has gone away. Thank you!