Jeremy,
The Google Maps action is built into Freeway, and it has a tiny but important problem that needs to be fixed before you release a new version of Freeway. The problem is that HTTPS is rapidly becoming the protocol of choice now, but the Google Maps action still uses HTTP. That’s fine until Freeway users move to a HTTPS site like I have. When that occurs, the Google Maps content is blocked by the browser because the page is trying to access it via HTTP rather than HTTPS.
All you need to do is just open the “Google Map.fwaction” and edit the 3 “http://maps.googleapis…” lines to be “https://maps.googleapis”. I am doing this manually and it works, but I don’t want to keep doing it every time a new version of Freeway comes out. If you update the code (taking only seconds to do) on your end, the problem is solved once and for all.
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at: