atuljain / django-gmapi Goto Github PK

What steps will reproduce the problem?
1. Navigate to a page with a django-gmapi map

What is the expected output? What do you see instead?
The static map shows fine, but when the javascript map replaces it, all the 
markers on the map disappear and IE complains of an 'unspecified error'.

What version of the product are you using? On what operating system?
1.0.1, Windows XP Pro SP 3


Please provide any additional information below.

IE error message:
Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; 
.NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET 
CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Timestamp: Wed, 30 Mar 2011 20:42:44 UTC


Message: Unspecified error.
Line: 32
Char: 527
Code: 0
URI: http://maps.gstatic.com/intl/en_us/mapfiles/api-3/4/7/main.js

I have a map with dozens of markers. With the Javascript map, that's fine, but 
I'm running up against the static API URL length limit. This is mostly because 
I'm using several custom icons with long URLs, and each is getting repeated 
several times within the map.

Part of the problem is the URL for the static image comes out like this:
...
markers=icon:http://long.url|lat,long&
markers=icon:http://long.url2|lat,long&
markers=icon:http://long.url|lat,long&
markers=icon:http://long.url2|lat,long&
markers=icon:http://long.url3|lat,long&

I'd appreciate it if the URL was condensed by combining markers with the same 
style in the form:

markers=markerStyles|markerLocation1| markerLocation2|... etc.

as specified here: 
http://code.google.com/apis/maps/documentation/staticmaps/#Markers

Using version 8218a4973b8e74e34254670aa3a6b7656d6fa85a

Specifying a custom marker icon without a shadow causes a silent failure - the 
jquery plugin fails on the call to parse() on line 172 of the jquery plugin 
(couldn't see an error message).

If specifying an icon without a shadow is not a reasonable thing to do (I'm new 
to the Google Maps API!) then it might be nice to raise an error when the 
marker is rendered.