Hi, I already had gmap module installed and (partially: see http://drupal.org/node/133062) working.
But after uploading the latest 5.x.1.x-dev version instead of maps only white space (corresponding to the map dimension) is displayed.
I did this update of the module some other times, but this is the first time I'm experiencing such kind of problems...

Comments

bdragon’s picture

bdragon commented

Please visit the settings page. I moved a lot of stuff around yesterday, and some of the settings changed places, so you need to visit the settings page and resave it. Especially check that a marker manager is selected. (Currently only the "no marker manager" one works properly)

bdragon’s picture

bdragon commented

Also, clear your browser cache, I changed one of the scripts slightly and if the old one was being used, it certainly could be causing the maps to disappear.

enli’s picture

enli commented

I downloaded version 5.x-0.6 and installed it. Everything works fine now... but it's a shame that the problem with the <a> tag hasn't still been fixed... Thanks for your work, anyway!

bdragon’s picture

bdragon commented

Yeah. 0.6 is the "Last known safe" version. I created it right before I committed the last batch of changes, because I did a lot of work in one day and *knew* *something* would break... ;)

mcarbone’s picture

mcarbone commented

I'm going to go back to the safe version, but it seems to me that this problem (and several other threads describing a similar one) is being caused by $element['#map'] not being properly set -- and so when theme_gmap uses that variable in the Drupal.extend, it's breaking.

mcarbone’s picture

mcarbone commented

Going back to 5.x-0.6 worked for me as well.

It occurs to me that since gmap is such an in-demand module, that perhaps we should prioritize getting an stable/official release out over creating new features. bdragon: you've been doing an amazing job w/ this module (it's noticeably getting better and better) -- ignore me if this is something you've already been working hard towards. If not, then I would suggest that after the next stable dev release, to freeze feature dev momentarily and concentrate on testing/bugs for an official release. I'm willing to both test and submit bug patches.

bdragon’s picture

bdragon commented

Yeah, I just fixed the #map problem. There was another problem that was causing warnings, and that is fixed now too.

1.0 will be feature-complete with 4.7 and api-frozen. I am still making api tweaks as I excersise different parts of gmap in a production site I am working on, and there are still a few lingering blocks of commented out stuff that has not been converted yet.

The only big things left at the moment are Marker Managers and WMS support. I am considering splitting WMS into a seperate module, now that the system is refactored well enough for that to be feasable.

bdragon’s picture

bdragon commented
Status: Active » Closed (fixed)

My last post here is still the case.