#13617: USE_L10N results in faulty javascript code in GeoDjango with some
locales
--------------------------------+-------------------------------------------
Reporter: piquadrat | Owner: jbronn
Status: assigned | Milestone: 1.3
Component: GIS | Version: 1.2
Resolution: | Keywords: L10N gis gmaps
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------+-------------------------------------------
Comment (by Federico Hlawaczek <f...@e42.com.ar>):
I encounter this problem also. For me, changing the max_resolution from a
float to a string solved the problems so far. In options.py use:
{{{
class OSMGeoAdmin(GeoModelAdmin):
...
max_resolution = "156543.0339"
}}}
Instead of:
{{{
class OSMGeoAdmin(GeoModelAdmin):
...
max_resolution = 156543.0339
}}}
Haven't thoroughly tried this enough to be completely sure that it solves
the problem for OSMGeoAdmin. But seems like a good work around until a
nicer solution is in place.
--
Ticket URL: <http://code.djangoproject.com/ticket/13617#comment:13>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
