Closed GoogleCodeExporter closed 8 years ago
arcato.us,
Glad you've got the admin maps working. For the databrowse maps to work you
must maintain the name `geometry` for your !GeoDjango field in the
admin.
If you have not changed the name of this field in your models, then the next
step to debug would be to load up firebug in mozilla firefox 2 or 3 and
check for javascript errors.
I'd happily accept patches for the field name issue, as this geodatabrowse app
should ideally provide the flexibly to change the !GeoDjango field.
Original comment by dane.spr...@gmail.com
on 1 Sep 2008 at 9:58
Strange, I tried again and saw the map once or twice -- seemingly on the first
invocation, but that behavior wasn't consistent.
I haven't changed the geometry column, and Firebug shows no errors. Behavior
is the
same on both Firefox 3 and Internet Explorer...
Original comment by arcato...@gmail.com
on 6 Sep 2008 at 9:52
Arcatos.us,
You 'saw the map'? That is pretty odd that it could appear unpredicatably and
you would still not see javascript errors. You must be changing some of your
settings.
Really, I can imagine only two main things could be going on:
1) the custom templates for the databrowse are not being found and loaded so
that only the WKT of the geometry field is being displayed and therefore NO
javascript is being called.
This will be obvious because the site name will not say `Geographic
Databrowse`. You need to make sure that these templates are being loaded:
http://geodjango-basic-
apps.googlecode.com/svn/trunk/projects/geographic_admin/templates/databrowse/
2) The custom templates are found and there are javascript errors you should be
able to see in firebug that will point to the syntax problem or some other
loading problem which is
preventing the OpenLayer js to be called as well as the custom js in:
http://geodjango-basic-
apps.googlecode.com/svn/trunk/projects/geographic_admin/templates/databrowse/obj
ect_detail.html
Original comment by dane.spr...@gmail.com
on 9 Sep 2008 at 12:58
Arcatos,
I'd like to resolve this issue. Any progress on figuring out what's wrong with
your installation?
Original comment by dane.spr...@gmail.com
on 29 Sep 2008 at 5:20
Closing this since it seemed like an isolated, non-replicable issue
Original comment by dane.spr...@gmail.com
on 17 Nov 2008 at 5:49
Original issue reported on code.google.com by
arcato...@gmail.com
on 1 Sep 2008 at 4:04