Oddly enough, another production site works without issue using the same store locator codebase. http://www.babyphatfragrances.com/product.html?pageId=store_locator_searchform This site calls in some sort of flash frame this url http://storelocator.cmkg.com/babyphatfragrance/StoreLocator.aspx.
I wish I know the "in some situations" part of the equation, so I can properly play by the rules to get the key validate properly. Thanks, Chris On Sep 20, 8:35 pm, Mike Williams <[EMAIL PROTECTED]> wrote: > Wasn't it Rossko who wrote: > > > > >As you've got no idea how those guys are calling your page in their > >iframe, maybe you could put a trap in your own page to read the > >window.location.host and see what's going on. In fact you could code > >a quick compare to see if it's what you expect, and only alert if not. > > You don't need to change your page. Just run a debugger on their page > and put a breakpoint inside the iframe. You get this: > > window.location.protocol = "http:" > window.location.host = "storelocator.cmkg.com" > window.location.pathname = "/CelineDionFragrance/StoreLocator.aspx" > > The problem isn't the window.location, it's the fact that, in some > situations. Google server somehow thinks that the page should be > validated as if it was using Google Premier rather than the free Google > API. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
