Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
If there's a need for a GMAP widget or formatter for Geo ( and surely there is! ), this should be handled by GMAP or another module. That way, we can have a variety of formatters and CCK widgets that provide output and input for Geo, but they don't all have to be maintained in a single module.
Does this mean that the old geo_gmap module could be launched as an independent module? What would need to be done to it?
It's a bit harsh to just remove the module before its functionality has been taken on by the gmap module. It breaks all my sites depending on it. As a result I've had to revert to the older version of geo for the moment, until I can work out what to do with the remains of geo_gmap to keep that functionality. Rather frustrating.
Comments
Comment #1
allie mickaI have removed the geo_gmap module entirely.
If there's a need for a GMAP widget or formatter for Geo ( and surely there is! ), this should be handled by GMAP or another module. That way, we can have a variety of formatters and CCK widgets that provide output and input for Geo, but they don't all have to be maintained in a single module.
Comment #2
martin_qDoes this mean that the old geo_gmap module could be launched as an independent module? What would need to be done to it?
It's a bit harsh to just remove the module before its functionality has been taken on by the gmap module. It breaks all my sites depending on it. As a result I've had to revert to the older version of geo for the moment, until I can work out what to do with the remains of geo_gmap to keep that functionality. Rather frustrating.
Comment #3
allie mickaI think that the geo_gmap functionality should be in its own module. However, it presently lives in the gmap_addons module, and seems to be working.