[TYPO3-english] wec_map 3.1.3, API

Brian Hauge Hansen brian.hauge at gmail.com
Tue Oct 25 18:52:37 CEST 2016


Maybe you can find some more information here, or contact the developer
directly: https://forge.typo3.org/projects/extension-wec_map

Den 23/10/2016 19.20 skrev "Axel Joensson" <a.joensson at web.de>:

> Hello,
> I have for some time been using the wec_map 3.1.1 ext. on a website now
> running under T3 ver. 6.2.27. Checking for ext updates I came across
> wec_map 3.1.3 and I am quite lucky to have tested the update on a cloned
> install first: version 3.1.3 denies service, requiring a "Google Maps
> API key".
> First question: Which API key would you like me to register? I found
> among others the Google Maps Android API, Google Maps JavaScript API,
> Google Static Maps API, Google Maps Embed API, Google Maps Directions
> API, Google Maps Distance Matrix API, Google Maps Elevation API, Google
> Maps Geocoding API, Google Maps Geolocation API, Google Maps Roads API
> and Google Maps Time Zone API. Not to mention the dozens of others APIs
> with similar names ...
> To register one of these in the developer console at
> <https://console.developers.google.com>, I guess around 100 Terms and
> Services Agreements are available to choose from, I would not be able to
> finish reading that this year, even if I knew which one to read and
> agree to. Maybe Google ought to point out that you need to hire a team
> of lawyers first, if you want to embed a Google map showing your
> location in your website? This is quite sick ...
> The wec_map manual (marked outdated for missing recent documentation
> standards; b.t.w., why are no longer text documents of the manuals
> available? Am I expected to only read manuals online?) shows a
> screenshot of the "API key Settings" section in the WEC Map Admin
> module, however, my ext in two fields only asks for "Google Maps Browser
> API key" (which is not available among the APIs listed in the developer
> console), while the manual screenshot ("Step 2: Configuration of
> API-keys") shows *one* field for the "Google Maps Browser API key" and
> *another* requiring a "Google Maps Server API key" (which of course
> isn't available at the console, too).
> I generated a "Google Maps Embed API" at the developers console, the
> domain is included in my developers account for many years by placing an
> ownership file generated by Google in the website root. I restricted the
> key for use only for that domain (by *.example.com/). Entering the key I
> obtained into the fields of wec_map didn't change a lot: While after
> update first a hint was printed on the frontend that I'd need an API
> key, entering it in the backend results in a white space in the
> frontend, where the map should show up, while everything necessary is
> present in the source code, but nothing displayed.
> So far my "solution" is not to update to wec_map 3.1.3 on the productive
> site, and in the long run to kick out all Google services from all
> websites I am working with. Any alternative?
> Regards,
> Axel
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

More information about the TYPO3-english mailing list