Thanks for the suggestion David. Would you point me to the documentation? We'll test it and report back. The Google changes are breaking many folks' maps - we need to get our Exhibit maps back online. Our problems began when we changed our domain name, and the Google Maps 'grandfathering' no longer applied.
/jay On Monday, November 14, 2016 at 6:28:04 AM UTC-6, David Karger wrote: > > Instead of adding a ?gmapkey parameter to the url, use the data-ex-apikey > attribute in the tag where you load the extention. > > On 11/14/2016 6:41 AM, Jay Gray wrote: > > Yes, Luis, it is your Exhibit. > You original used Exhibit 2; we have not updated it, although have learned > from it. > The reason I featured it in this post is because it uses your Gmap ID. > While it may work for you (because Google "grandfathered existing sites > that do not use a Gmap ID), it does not work on our IP address. > > We've encountered what may be a conflict between the Exhibit 3 method of > loading a Google Map ID and the Google Processor. We described it here: > https://groups.google.com/forum/#!topic/simile-widgets/_SXCaMfLi7g > > Google changed their policies on June 22. See discussion here: > https://churchthemes.com/page-didnt-load-google-maps-correctly/ > > So my question to you is: > How do you assign your Gmap ID to an Exhibit 3 "../map-extension.js" and > have it correctly processed by Google (where you can verify in Google > Chrome dev tools that it has been properly parsed)? > > Perhaps we should be using: > > https://api.simile-widgets.org/exhibit/HEAD/extensions/map/scripts/google-maps-v2-view.js > > My thought was to ask you to 'debug' is issue because you have > successfully used the Gmap ID in the past. > Would you be willing to update one of your Exhibits that use Google Maps, > apply your Google MAP API Key, and show use an implementation that works? > > We'll then use your implementation, replace your API key with ours, and > test it. > > FYI, the Chrome platform basically requires HTTPS: > All Exhibit libraries are HTTPS active, but you may also have to update > your Bootstrap libraries. > > Tell me if I need to do something to help with your testing. > > Many thanks for your continuing help. > > /jay > > > > > On Monday, November 14, 2016 at 4:50:05 AM UTC-6, Luis Miguel Morillas > wrote: >> >> Hi, Jay, >> >> What map are you talking about? Is it mine? >> >> I think you are mixing exhibit2 and exhibit3 code. >> >> Saludos, >> >> -- luismiguel (@lmorillas) >> >> >> 2016-11-14 11:15 GMT+01:00 Jay Gray <[email protected]>: >> > Hey Luis >> > >> > May I ask you about your use of Google Maps? >> > We've looked at your map and timeline with the data type "Ciências, >> Artes e >> > Humanidades" >> > That Exhibit contains 117 items >> > >> > You use: >> > >> > href=" >> > >> http://api.simile-widgets.org/exhibit/3.1.0rc/extensions/map/map-extension.js?service=google2&gmapKey=ABQIAAAA5JLLfCE9c7HAtg25QM2KCRRyiP6mHEsQpwvxB19-hS9Kgd8RYhSXEtJVAXDUCZPqwtZZi7-HUYUYrw"; >> >> >> > >> > We can't load your map using the string: >> "service=google2&gmapKey=YOUR-ID" >> > >> > If you used the latest Exhibit lib: >> > >> > <script rel='exhibit-extension' type='text/javascript' >> > src=' >> https://api.simile-widgets.org/exhibit/HEAD/extensions/map/map-extension.js'></script> >> >> >> > >> > how would you assign your gmapKey to "../map-extension.js"? >> > Can you implement an update that runs in Chrome? >> > >> > Thanks for your help here. >> > >> > /jay >> > >> > >> > On Monday, September 19, 2016 at 2:23:59 AM UTC-5, Luis Miguel Morillas >> > wrote: >> >> >> >> Hi all >> >> >> >> What's the reason exhibit 3 only supports Google Maps? An easy >> >> maintenance? >> >> >> >> Could it be interesting to work integrating osm, leaflet or other? >> >> >> >> >> >> Best, >> >> >> >> -- luismiguel (@lmorillas) >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "SIMILE Widgets" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected]. >> > To post to this group, send email to [email protected]. >> > Visit this group at https://groups.google.com/group/simile-widgets. >> > For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "SIMILE Widgets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/simile-widgets. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/simile-widgets. For more options, visit https://groups.google.com/d/optout.
