Kazu46Machi / earth-api-samples

Automatically exported from code.google.com/p/earth-api-samples
0 stars 0 forks source link

01/04/2009 (april) release of google earth does not work any more with IE8, or in HTTPS environment. #194

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi everybody,
Up to now everything was working well with IE8 and also with HTTPS pages. 
But since this mornig ( 01/04/09) a new google earth plugin release seems 
to be published. Now we have some problems:

1. Using IE8 as the browser :
The plugin is not loaded (HTTP and HTTPS pages).
We get a message like "the browser is not recognized" 

2. On HTTPS pages with at least IE7 ( cannot use IE8 because of point 1 ) :
Cannot load the plugin  is secure environment. Mixed content (HTTP and 
HTTPS ) is detected by the browser ( as with the previous release of the 
plugin ) But when we confirm not to load unsecure content, the plugin 
cannot be loaded. The page freeze empty.
In the manner, with the previous release, confirming not to load unsecure 
content did not make any problem, and the plugin was able to load 
correctly.

Any suggestions ?

Best regards
Zorg

Which plugin version are you using?

Which browsers and operating systems are affected?

Please provide any additional information (code snippets/links) below.

Original issue reported on code.google.com by hernande...@free.fr on 1 Apr 2009 at 10:26

GoogleCodeExporter commented 8 years ago
We've temporarily disabled IE8 support. See this post:

http://groups.google.com/group/google-earth-api-notify/browse_thread/thread/340f
fbd776b8f4e8

Regarding HTTPS, can you respond with a link to the site you are having trouble 
with?

Original comment by api.roman.public@gmail.com on 1 Apr 2009 at 6:31

GoogleCodeExporter commented 8 years ago
Hi,

thank you very much for your answer

here is the link for HTTPS issue: 

https://www.globeinfos.fr

It is a site dealing with real time vessel tracking. Even if the tracking 
service is 
free, some users need to keep their vessel positions secret ( fishermen, etc. ) 
So 
this kind of users have a personnal account to connect to their Vessel tracking 
page. So this confidentiality problem is the reason why we use HTTPS protocol.

You can login with the public account:
User: Belespoir
Password: MJaouen
( password is case sensitive )

Then click on the "arrow button" on the right side of the password to login.

You will be directed to a user page where you can access the tracking page : 2 
vessels are visibles in "Martinique".

Just play with with the security warnings option (Yes, No) and you will see the 
problem.

Thank you very much for your help :-)

Jose M. H.

Original comment by hernande...@free.fr on 2 Apr 2009 at 11:04

GoogleCodeExporter commented 8 years ago
Hm, I can't reproduce this. Can you try resetting the IE settings to defaults?

Original comment by api.roman.public@gmail.com on 2 Apr 2009 at 8:30

GoogleCodeExporter commented 8 years ago
Hi,
thanks for you repply.

Because my English is not very good, here is a link to a flash video(26Mo...)I 
made 
to try to give you a best idea of the problem.

https://www.globeinfos.fr/plugin/plugin.swf

Hope it will help ;-).

Best regards

Original comment by hernande...@free.fr on 3 Apr 2009 at 3:07

GoogleCodeExporter commented 8 years ago
Hi,
it seems that the plugin needs to reference the following link:

http://csi.gstatic.com/csi?v=2&s=earth_plugin&rls=5.0.11655.6079&it=prt.13011

in a Javascript file: Default.I.js

Best regards.

Original comment by hernande...@free.fr on 3 Apr 2009 at 4:13

GoogleCodeExporter commented 8 years ago
Ah, ok. We're looking into it.

Original comment by api.roman.public@gmail.com on 3 Apr 2009 at 7:23

GoogleCodeExporter commented 8 years ago
Hi Zorg,

We have made a change to the 1.x version of the google earth plugin loader to 
try to 
address the issue of mixing http and https.  Could you please test your page, 
changing the line:

  google.load("earth", "1");

so that it reads:

  google.load("earth", "1.x");

and please let us know if it fixes the problem for you.

-Thatcher

Original comment by tulr...@google.com on 4 Apr 2009 at 2:02

GoogleCodeExporter commented 8 years ago
Hi ThatCher,

Great job !! it works nicely !
Congratulations.

Thank you very much to you at all your team for your reactivity, and of course 
for 
solving this issue ;-) We appreciate  lot.

Just inform me if I must change again the line in the page. For the time beeing 
I 
keep it like this. Thank again :-)

Best regards
Jose H.(alias Zorg...)

Original comment by hernande...@free.fr on 4 Apr 2009 at 5:12

GoogleCodeExporter commented 8 years ago
The fix will be available in the stable version "1" loader within an hour or so.

Original comment by api.roman.public@gmail.com on 16 Apr 2009 at 6:23

GoogleCodeExporter commented 8 years ago
Hi everybody,

Thank you very much.
I switch to that version right now.

Best regards

Jose H.

Original comment by hernande...@free.fr on 1 May 2009 at 9:14