shawnshuailin / google-maps-utility-library-v3

Automatically exported from code.google.com/p/google-maps-utility-library-v3
Apache License 2.0
0 stars 0 forks source link

Only 1 marker displayed when multiple markers are added #296

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Demo link or sample code:
http://google-maps-utility-library-v3.googlecode.com/svn/tags/markerwithlabel/1.
1.9/examples/basic.html

What steps will reproduce the problem?
1. Go to the link specified above

Expected result:
There should be 2 markers, each having its own label.

Actual result:
There is just 1 marker, and there are 2 labels. Only the last of the 2 expected 
markers is displayed.

Version: 1.1.9

Browser / Operating System:
At least seen on FF/Linux and Boat Browser/Android

Additional comments:

Original issue reported on code.google.com by erikstob...@gmail.com on 4 Mar 2014 at 3:19

GoogleCodeExporter commented 8 years ago
This used to work fine. Behavior seen just recently.

Original comment by erikstob...@gmail.com on 4 Mar 2014 at 3:24

GoogleCodeExporter commented 8 years ago
Same here - started within the last 24 hours. The labels appear in the correct 
place but the all the icons are at the location of the last marker created.

I'm using 1.1.8 of MarkerWithLabel and changing my Maps call from
...maps.google.com/maps/api/js?sensor=false
to
...maps.google.com/maps/api/js?sensor=false&v=3.15
seemed to fix it.

...although that seems to be the version you are loading yet still goes wrong 
on your page? Goes wrong with 3.16 for me - ok in 3.15

...still ... there may be a clue in there somewhere...

Original comment by romynpg on 4 Mar 2014 at 5:33

GoogleCodeExporter commented 8 years ago
I've the same problem with FF/XP and Chrome/XP. Changing to v=3.15 works 
correctly to me too.

Original comment by mario.fe...@gmail.com on 4 Mar 2014 at 8:47

GoogleCodeExporter commented 8 years ago
Thanks for your responses guys. You really helped me out!

I'm experiencing the same as you:
* Using ...maps.google.com/maps/api/js?sensor=false&v=3.15 works
* Using ...maps.google.com/maps/api/js?sensor=false&v=3.16 goes wrong
* Using ...maps.google.com/maps/api/js?sensor=false goes wrong as well

So I guess MarkerWithLabel is no longer compatible with Google Maps API 3.16 
(and higher).

Original comment by erikstob...@gmail.com on 5 Mar 2014 at 8:15

GoogleCodeExporter commented 8 years ago
I had the same issue that started yesterday 3/4/14 and inserting &v3.15 
corrected my problem.

Original comment by mike.sae...@gmail.com on 5 Mar 2014 at 8:27

GoogleCodeExporter commented 8 years ago
I am encountering the same issue. We'll have to explicitly define Google maps 
api version while referencing it and it works well upto 3.15. It seems that 
some recent update on Google maps api broke MarkerWithLabel code.

Original comment by st...@finethemes.com on 20 May 2014 at 12:58

GoogleCodeExporter commented 8 years ago
I have the same issue as exactly described by the last comment. 
This issue was working on all stable versions of the maps API up until 3.15

Previously we had also explicitly defined the most stable version of the Maps 
V3 API by including "v=3" in the API key bootstrap URL. 

Any ideas what is causing it? 

Original comment by Ruaidhri...@gmail.com on 22 May 2014 at 12:02

GoogleCodeExporter commented 8 years ago
This has already been fixed in v.1.1.9

See comments on
https://code.google.com/p/gmaps-api-issues/issues/detail?id=6447

Original comment by kaska...@google.com on 23 May 2014 at 7:33

GoogleCodeExporter commented 8 years ago
Not a helpful response at all. 
If you are talking about the MarkerWithLabel library we are using version 1.1.10

Original comment by Ruaidhri...@gmail.com on 23 May 2014 at 8:46

GoogleCodeExporter commented 8 years ago
The linked Demo is working for me in FF and Chrome, can you please provide 
further details on what exactly is not working for you in 1.1.10?

Original comment by me...@google.com on 23 May 2014 at 3:04

GoogleCodeExporter commented 8 years ago
I experienced this issue using the packed version of 1.1.10 ... when I switched 
to the unpacked version, the bug was fixed.

Original comment by kimbodes...@gmail.com on 4 Jul 2014 at 8:58