|
tixeventsadmin
|
August 16, 2016 at 1:44 am
I know you will probably tell me that this issue is fixed in EE4, but I unfortunately cannot migrate right now due to high volume traffic.. is there any way to patch in the needed API key without upgrading to EE4? I realize this might need custom coding.. I just wish to know if it is possible..
thanks!
|
|
Josh
|
August 16, 2016 at 9:22 am
Hi Tixeventsadmin,
We’ll plan on updating EE3 to include a means to add Google Maps API now that Google has changed their terms. In the meantime you can embed a static map onto your webpages. Here’s a link to a static map generator that you can use to get ready made maps html:
http://staticmapmaker.com/google/
|
|
tixeventsadmin
|
August 18, 2016 at 3:11 pm
But this only solves the problem on static pages.. what about the image of the map that goes on the ticket? Is there no way to bypass that map generator? Im thinking it might be simpler to just append the API Key via a script of some sort.. any ideas?
|
|
tixeventsadmin
|
August 18, 2016 at 3:11 pm
Or any idea on when this update you mention for EE3 might be available?
|
|
Tony
|
August 19, 2016 at 5:38 am
But this only solves the problem on static pages.. what about the image of the map that goes on the ticket?
The map added to the ticket uses the static map api so it will fix those calls.
Or any idea on when this update you mention for EE3 might be available?
The branch for this is currently under testing but is available HERE if you’d like to test it yourself.
You will find a new field within Event Espresso -> General Settings for the Google API Key.
|
|
tixeventsadmin
|
August 26, 2016 at 12:56 pm
Ok thanks Tony!
When would testing be finalized on your end?
|
|
Josh
|
August 29, 2016 at 1:20 pm
The testing is completed, the branch will get merged to Master and will be included in the next EE3 update release.
|
|
tixeventsadmin
|
September 2, 2016 at 2:53 pm
Awesome looking forward to it! thanks for the followup!
|
