I am trying to use Google maps in the Fancybox skin but I am getting the error "Geocoder failed due to: REQUEST_DENIED" that is associated with not having an API key. However, I do have an API key from Google and that key works perfectly well in the Gromit skin, so I have no idea what the problem really is. Any help would be appreciated. Thanks
I generated another API key, also unrestricted, and it also caused the same error.
As a test, using the same album, I simply changed the skin to Gromit, placed the newly generated API key, and did a "Make album/make changes". The new Gromit based skin brought up the Google maps with no problem.
If you want maps, but with a more modern appearance than Gromit, try Saturn, which has a Gromit-like thumbnail page, but with a lightbox instead of separate slide pages. Or for a more contemporary appearance, try Neptune, which has a justified gallery of thumbnails (the next release will offer fixed-shape thumbnails, as well), and the same lightbox as Saturn.
Thanks, Gromit. I have just looked at both Saturn and Neptune and they are quite nice, but they lack one feature that FancyBox has, which is the ability to go into full screen mode. I like the full screen option for my slide shows of travels. Nonetheless, I see that you offer some good alternatives to your eponymous skin.
My last set of tests have been with the newly generated API key that does not have - or _ in the key. FancyBox still gets the error with that key. I did not forward that to you, but I can if you think it would help, however I don't think that is the problem.
Thanks to Gromit's suggestion I have just completed some tests, simply by changing the skin, setting the map key (and related bits) and doing a "Make album/changes only" and looking at the results with Preview.
Skins Gromit, Saturn, and Neptune all work just fine with the API key and bring up Google maps with no problem
Skins FancyBox and PhotoSwipe generate the Google map error.
The specific error that comes back is Geocoding Service: This API project is not authorized to use this API. which suggests that the issue has to do with authorization, not whether the key itself is valid. In any case there seems to be something different about how you and Gromit handle the interaction with Google in your code.
Sorry, I think I had replaced that album on my website a couple of times in testing and that had introduced some additional (spurious) errors. The following should bring up a clean version of the FancyBox site with just the original error.
Given the behaviour so far, I suspect that all your testing with your keys will result in no problem with the maps. The problem will show up when someone else with keys generated for a different Google Project uses your skin. What we need now is a bit of help. Perhaps Gromit could run a test or two of your skins on albums known to be good with his skins? My bet is that he will have the problem as well.
As much as I've enjoyed this thrashing about, I guess it's time to confess. When I saw your original post, and did about 60 seconds of Googling, I was pretty sure I knew what the problem is. I haven't done a thorough test, but I'm about 98% sure my first hunch was correct.
Now, what's it worth to both of you to find out how to fix this?
OK, I'll take pity on you. In short, Fancybox is calling upon one of the Google maps API's that's "beyond" the basic functionality. The tipoff is that the error message refers to "geocode," which is a separate service. On my old API keys, it's enabled by default, so the Fancybox maps work. But maybe with a newer key, that's apparently not the case. Just be aware that it's billed at a different rate.
Head for your Google maps API console, then see the series of screenshots attached, in order. After the last step, look for an "enable" button somewhere.
Thanks for your belated assistance, Gromit. That worked, and the test site is now bringing up the Google Maps as expected.
I'm afraid I know next to nothing about Google APIs and simply followed the instructions I found, I believe, in one of the forum posts here. I suspect the instructions for using Google Map APIs are going to get a bit more complicated.