I commented on the same bug in another issue. The clusterer shows only "2" for clusters with many more than two markers, initially, but then becomes correct as soon as the map is zoomed. Enabling autozoom seems to correct the problem, but it persists after disabling autozoom.

CommentFileSizeAuthor
#10 first-autozoom.png672.01 KBkorayal
#10 after-manualzoom.png667.94 KBkorayal

Comments

marcushenningsen’s picture

marcushenningsen commented

I still have the problem with autozoom enabled. How do your gmap settings otherwise look?

webavant’s picture

webavant commented

I also had that same problem, at one point, where I would enable autozoom, but it still would not display the correct cluster amounts. I realized that autozoom was not actually occurring, despite having enabled it, because of some other contributing factor. I think it wasn't autozooming because I had the zoom level set higher (closer-in) than all of the nodes appearing in my gmap (some markers were off the edge). So I just set the zoom lower (further-out), autozoom took effect and the clusterer behaved correctly.

webavant’s picture

webavant commented
Status: Active » Closed (fixed)
webavant’s picture

webavant commented
Status: Closed (fixed) » Active

actually, nevermind

meji15’s picture

meji15 commented

I have the same problem with the initially-loaded map. The counter always says 2 when the map is first loaded but it shows correct result after zooming in/out.

Has anyone found any solution yet?

webavant’s picture

webavant commented

Enabling autozoom seems to be the solution. Works nicely now.

enzipher’s picture

enzipher commented

I can confirm that autozoom fixes the issue.

For anyone wondering how to enable this, use the below macro instead of [gmap]:
[gmap behavior=+autozoom ]

Cheers,

mablack’s picture

mablack commented

Grabbing the latest copy of MarkerClusterer.js from SVN - http://code.google.com/p/gmaps-utility-library-dev/ - also seems to fix the issue.

vodkov’s picture

vodkov commented
Version: 6.x-1.x-dev » 7.x-1.x-dev

Thank you for the tip.
[gmap behavior=+autozoom ] solved the problem for me.

korayal’s picture

korayal commented
Version: 7.x-1.x-dev » 6.x-1.x-dev
StatusFileSize
new after-manualzoom.png667.94 KB
new first-autozoom.png672.01 KB

I had a similar problem but autozoom fixed it.

But I still see wrong marker counts on the map. You can check:

https://burgerking.kuponmakinasi.com/admin/restorankontrol/map

As you can see when you zoom in to a cluster with the count "2", there is only one marker. So it looks like it's duplicating their count.

You can also check the numbers on the first load, and check them again after a zoom in and out, values on the first load are relatively more correct, but somehow it duplicates the others. (You can check the attached images)

jeni_dc’s picture

jeni_dc commented

I was faced with a situation where I couldn't have autozoom enabled on D7 for a particular map, and I can confirm the latest js from the link in #8 worked for me, too.

Thanks!

Jeni