Last modified: 2012-07-03 13:13:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39688, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37688 - Maps does not pass a V3 API key to Google
Maps does not pass a V3 API key to Google
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Maps (Other open bugs)
unspecified
All All
: Unprioritized critical (vote)
: ---
Assigned To: Jeroen De Dauw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-18 14:07 UTC by Neill Mitchell
Modified: 2012-07-03 13:13 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Neill Mitchell 2012-06-18 14:07:31 UTC
Hi.

The Maps documentation's installation instructions lists a variable to pass an API key to Google.
http://mapping.referata.com/wiki/Maps#Installation

This leads you to believe the facility is supported, allowing you to buy a license from Google to support >2500 geocodes per day.

However, the key is not passed into the V3 API, so you are limited to the anonymous access limit of 2500 geocodes a day. Any further geocode attempts fail.

The ability to pass the API key is required.

Thanks
Comment 1 Neill Mitchell 2012-06-18 15:29:22 UTC
I expect it is a common call, but just in case it's not, Semantic Maps needs to support this as well.

:)
Comment 2 Neill Mitchell 2012-07-03 12:46:13 UTC
Hi Jeroen.

Great news that Maps 2.0 is coming out. Will this fix be included?

Thanks!
Comment 3 Jeroen De Dauw 2012-07-03 13:06:47 UTC
This has been fixed on master and is in 2.0 alpha.
Comment 4 Neill Mitchell 2012-07-03 13:13:53 UTC
Great! Thanks Jeroen :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links