https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362014-03-23T06:59:16ZEcoinformatics RedmineMetacatUI - Bug #6480: Google Maps API fails often https://projects.ecoinformatics.org/ecoinfo/issues/6480?journal_id=215802014-03-23T06:59:16Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>I thought we had wired it up so that if there was a gmaps load failure, the app would still load, but the map would just not render. I have seen (though not recently now that It hink about it) the site fail to load because of the gmaps api. I would just refresh the page and it would work. Not sure if that is related to what you are seeing.</p> MetacatUI - Bug #6480: Google Maps API fails often https://projects.ecoinformatics.org/ecoinfo/issues/6480?journal_id=215832014-03-24T23:24:14ZLauren Walkerwalker@nceas.ucsb.edu
<ul></ul><p>For some reason it only happens in the Statistics View, so far. The DataCatalog View will load fine for me in those cases but I have to continuously reload the StatsView until I stop getting the error. I have had cases where the GMaps API fails and then list view loads, but for this particular view it stops the rendering of the whole page, even though GMaps isn't needed.</p> MetacatUI - Bug #6480: Google Maps API fails often https://projects.ecoinformatics.org/ecoinfo/issues/6480?journal_id=216152014-04-03T14:05:09ZLauren Walkerwalker@nceas.ucsb.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Works For Me</i></li></ul><p>I haven't been able to recreate this error so I will come back to it later if needed.</p> MetacatUI - Bug #6480: Google Maps API fails often https://projects.ecoinformatics.org/ecoinfo/issues/6480?journal_id=217082014-05-08T18:45:10ZLauren Walkerwalker@nceas.ucsb.edu
<ul><li><strong>Subject</strong> changed from <i>Google Maps API fails often for profile view</i> to <i>Google Maps API fails often </i></li><li><strong>Status</strong> changed from <i>Works For Me</i> to <i>In Progress</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> changed from <i>1.5.0</i> to <i>1.6.0</i></li></ul><p>This is still an issue for many people and makes the app nonfunctional. It is happening in any view since Require.js tries to load GMaps upon page load, regardless of the current view.</p> MetacatUI - Bug #6480: Google Maps API fails often https://projects.ecoinformatics.org/ecoinfo/issues/6480?journal_id=217972014-09-11T14:53:04ZLauren Walkerwalker@nceas.ucsb.edu
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>These Gmap errors were occurring because the app would define the GMaps URL in the Require configuration, then would soon after "require" the Gmaps component in the app. On fast connections, the app would have received a response from Google, would "require" the Gmaps component ok, and would continue loading the rest of the app.</p>
<p>On slower connections, the app would still be waiting for a response from Google before it "required" GMaps, and would fail.</p>
<p>The Google Maps component of the app is now loaded and defined first in the app.js file before all other Require.js configuration. This makes the app wait for a response from Google before continuing to load. The app can still work offline for development purposes by removing the Google Maps option (i.e. removing the Google Maps API key in index.html).</p>