Posted by wessex on December 2, 2008 at 2:01pm
| Project: | GMap Addons |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Whenever I try to overlay data, I get the browser error "gmap-auto1-gmap0" - clicking OK to the error loads the map and overlay as expected.
Any ideas what could be up?
Comments
#1
Seems like debug code was checked in.
Edit the file js/overlay_geoxml.js so that the line
alert (obj.map.getContainer().id);reads
// alert (obj.map.getContainer().id);or remove the whole line entirely.
HTH,
dziegel
#2
Thanks dziegel, I'll give it a try!
#3
It worked!
Thanks ever so much :-)
#4
Patch attached.
#5
--Ignore... found my error--
#6
things like this can be easily traced back to it's origin by overriding the window.alert function to something else, console.trace for instance (requires firebug or a console.trace compatible browser)
this isn't the prettiest, but it's an easy way to inject it before everything else from within a theme's template.php:
<?phpfunction mytheme_preprocess_page(&$vars) {
$vars['scripts'] = '<script type="text/javascript">window.alert = function(msg) { if (console) { console.trace(msg); } };</script>' . $vars['scripts'];
}
?>
#7
#4 Works for me. Can this be committed?
#8
I had this error too and commenting out the line as noted at #4 worked.
But why is this alert in the code? This has been there apparently for a long time seing the postdate of this thread. Obviously the developers think it needs to be there but why?
#9
Actually, the problem is not that I think it needs to be there, it's that I'm doing so poorly at remembering to maintain gmap_addons that it really *has* accidentally been left in for two years.
Fixed, thanks, and sorry for the ridiculous wait.
http://drupal.org/cvs?commit=488992
http://drupal.org/cvs?commit=488994
#10
hi bdragon,
Thanks for your reply to this! I'm glad this issue is sorted out now. And thanks for the nice software!
#11
Automatically closed -- issue fixed for 2 weeks with no activity.