Closed (duplicate)
Project:
GMap Module
Version:
5.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Mar 2008 at 03:54 UTC
Updated:
30 Jun 2008 at 23:54 UTC
Gmap was all working fine in Firefox and IE, until I decided to try enabling Clusterer2. I did so, found it wasn't working correctly, so decided to disable it (go back to the default "No manager (use addOverlay directly)" mode...
But now the gmaps popups are completely broken?! The map loads, I can see the markers, and scroll around. But as SOON as I click a marker to trigger a popup, the whole map flicks to a blank grey box.... and no popup is revealed.
It seems as though enabling the Clusterer and then disabling it, was enough to break my gmap installation?
Comments
Comment #1
mediafrenzy commentedI just checked in the source code of the generated page, and this is being added as well?? Should that be there, considering I've switched off all the management?
Comment #2
mediafrenzy commentedI should add that I'm talking about the /map/node URL... I only have GMAP, GMAP_location and Location installed.
Ok, I've figured something else out. The map loads, complete with markers, and when you click a marker, the viewport flies way too far up or down, thus displaying only grey (out of the google maps worldmap). I can then zoom way out, and reveal the world map in its entirity, complete with the marker popup I selected!
Then if I click another marker, it does the same thing - flies way too far up into the grey space again.... and once again if I drag way back down, I can find the map with the new marker popup showing....
Is this a clue for any one familiar with how gmap works?
Comment #3
mediafrenzy commentedAlso, if I set the action for clicking a marker to "open link", it seems to work fine, the new page loads etc...
But if I keep it set on "open info window" to trigger that little google popup window, what I describe above happens...
Comment #4
kovalski-1 commentedGot the same behavior starting yesterday on two sites with very different gmap configs. This has to be some change in google's API, and it has nothing to do with clusterer, since I haven't enabled it. (one site uses xoverlay and the other uses google manager).
I should also note that I'm not using map/node but views.
It sems that when the map is scrolled to accomodate for the popup the scroll ammount parameters went crazy :) (actually it's zooming in and scrolling far far away)
Comment #5
pshadow commentedSame here. I'm using views to display nodes with locations. Worked fine up til yesterday. Thought maybe it was the Cluster thing as mediafrenzy mentioned, but I didn't have it set though thought maybe it was doing something anyway since the default was 150 markers which also happens to be the number I have just surpassed on the map, but I changed that number and still not working. tried to enable and disable and still no luck.
Comment #6
kovalski-1 commentedAfter tracing a little with firebug, I found that this happens in a call to openInfoWindowHtml.
Google's documentation (http://code.google.com/apis/maps/documentation/reference.html) lists this method as taking 2-3 params, however the code in marker.js (l. 36- if (marker.text) {marker.marker.openInfoWindowHtml(marker.text); }) only passes the html content, might this be the problem?
Comment #7
tom_o_t commentedSame problem on my Drupal 5.x sites, and I can see it on other people's sites too. Not affecting my Drupal 4.7 site for some reason.
I've changed the title of the issue to be more descriptive of what the problem seems to be...
I couldn't find anything on any of Google's pages about updates to the Google Maps API in the last couple of days, but I could have been looking in the wrong place.
Comment #8
mediafrenzy commentedOh thanks for the input guys. Thats an interesting development, and a relief to hear its not just something that exploded on my site.
If anyone has any further info on this, please let us know... I'm not a coder, but can help test any possible solution that someone comes up with.
Comment #9
pshadow commentedSomeone found a fix that looks to be working for me:
http://drupal.org/node/231473
Comment #10
bdragon commentedI'm assuming it was the problem described by me in #25 of http://drupal.org/node/231473.