• After wondering why the Google Maps Javascript API keeps complaining about an unauthorised webpage, I realised the plugin writes https://maps.google.com/maps/api/js?v=3.24& #038;key=***************** (the blank between & and # is on purpose for displaying here – there’s no blank in the page’s code) instead of https://maps.google.com/maps/api/js?v=3.24&key=***************** into the page’s source code.
    When opening both versions directly in a browser it turns out the API isn’t accepting the decimal encoded ampersand and thus the key isn’t recognised at all.

    Does anyone else experience this behaviour?
    And when did it start? The plugin used to work like a charm (my fault I didn’t test the directions functionality but only the widget’s appearance itself after the last x updates – who knows for how long this hasn’t been working. The client never complained about it.).

    Cheers

    • This topic was modified 8 years, 6 months ago by Carib Design.
    • This topic was modified 8 years, 6 months ago by Carib Design.
Viewing 1 replies (of 1 total)
  • Plugin Author webaware

    (@webaware)

    G’day Carib Design, long time no speak ??

    That URL is correct — for HTML. The &# 038; (no space) is an HTML-encoded ampersand, &, so in fact the URL will load correctly. If you view the page source in Firefox and click on the link, it will load the script correctly. Try it on the demo / doco site, where you’ll see that it’s the same:

    https://flexible-map.webaware.net.au/

    If you’re having a problem with the API key, it’s most likely one of the following:

    * you haven’t added all of the domain names to the API key
    * you haven’t enabled the Google Maps JavaScript API for the project

    cheers,
    Ross

    • This reply was modified 8 years, 6 months ago by webaware. Reason: new forum is buggering up HTML entities in code tags
Viewing 1 replies (of 1 total)
  • The topic ‘Plugin writes “& #038;” instead of “&” in API URL – key won’t be recognised’ is closed to new replies.