-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Earth not visible when completely offline #2
Comments
If you run local webserver in python - what error do you see in developer console? |
Well I didn't run a webserver in python. I used apache.
|
Your requests to webglearth.com came, because you didn't adapt the The other requests to google-analytics.com come from the webglearth's source code. That's something I also just stumbled upon while testing the offline-capability. So @klokan, why is it that you collect data? And why don't you share this information on your website? Also if it should throw an uncatched error, it would break the rest of the JavaScript, what probably happened to OP. |
We need the tracking via Google Analytics for the CDN hosted version of WebGLEarth API. Feel free to make a pull request removing it here - and ideally another PR into https://github.com/webglearth/webglearth2 where inclusion of the tracking code will be wrapped by a constant defined by a new "define" in the plovr api.json. We are busy on other tasks right now, unfortunately. We may get to this at later point, if time allows. But if you make the PRs we review and accept it. |
I have apache running on Ubuntu 15.04. I used that to access index.html. It worked. Later, I cleared my browser's cache and disconnected myself from the Internet. It stopped working. When I now open index.html, I just see a blank page with a gradient; no earth.
I thought maybe I haven't set up things correctly, so I turned off security restrictions in Firefox (by setting
security.fileuri.strict_origin_policy
tofalse
). But earth was again absent when I directly opened index.html.The text was updated successfully, but these errors were encountered: