This snippet adds support for OSM maps for GeometryField in Admin TabularInlines.
The one possible issue with this snippet is that the OSMGeoInlineForm has to know about the parent ModelAdmin which it does through the code
`model_admin_instance = admin.sites.site._registry[self.parent_model]`
which won't work if you don't use the default model admin to register the model admin. I'll try and come up with a work around and edit the snippet.
Due to the need to mess around with inline style sheets and IE not playing ball with just copying the innerHTML I've settled on using the jQuery.Rule plugin which I've included here as the last version published on the site was incompatible with jQuery 1.4.2 and I found a pathced version online, I also had to modify it due to the Django admin using the compatibility mode of jQuery so there is no global jQuery variable it's django.jQuery instead.
1. Create an osmgeo_inline.py file in your app and copy the top code into it.
2. Create the template file in a directory called admin within a template directory for your app, the template file must be called osmgeo_tabular_inline.html, and copy the middle code into it.
3. Create the jquery rule plugin file in your media or admin-media js directory and copy the bottom code into it. Don't forget to change the OSMGeoInlineForm's class Media's js = ('.....',) to the correct path to the file if need be.
4. In your admin.py you can create inline models using OSMGeoTabularInline just as you would TabularInline.
Examples all based on the following in models.py
from django.contrib.gis.db import models
class MyModel(models.Model):
name = models.CharField(max_length=64)
route = models.LineStringField(srid=settings.WGS_SRID)
class MySubModel(models.Model):
mymodel = models.ForeignKey(MyModel)
name = models.CharField(max_length=64)
location = models.PointField(srid=settings.WGS_SRID)
Example 1 - basic usage (admin.py):
from django.contrib.gis.admin import OSMGeoAdmin
from myapp.osmgeo_inline import OSMGeoTabularInline
from myapp.models import MyModel, MySubModel
class MySubModelInline(OSMGeoTabularInline):
model = MySubModel
class MyModelAdmin(OSMGeoAdmin):
inlines = [MySubModelInline]
admin.site.register(MyModel, MyModelAdmin)
Example 2 - overriding the default map widget params and setting the inline map's centre point to match the main models map centre (admin.py):
from django.contrib.gis.admin import OSMGeoAdmin
from myapp.osmgeo_inline import OSMGeoTabularInline
from myapp.models import MyModel, MySubModel
class MySubModelInline(OSMGeoTabularInline):
model = MySubModel
class MyModelAdmin(OSMGeoAdmin):
inlines = [MySubModelInline]
params = {'map_width: 200, 'map_height': 200]
def get_formset(self, request, obj=None, **kwargs):
centre = None
if obj is not None:
centre = obj.route.centroid.transform(900913, clone=True)
self.params['default_lon'] = centre.coords[0]
self.params['default_lat'] = centre.coords[1]
self.params['default_zoom'] = 12
return super(TrailSubmissionInlineBase, self).get_formset(request, obj, **kwargs)
admin.site.register(MyModel, MyModelAdmin)
I've not looked at StackedInlines because I don't use them but all that would be needed is to add a class OSMGeoStackedInline(StackedInline) that was a copy of OSMGeoTabularInline but with a template based on the StackedInline template - the javascript code in var initMap = function(row) would probably have to be adapted though.
A simple django-admin filter to replace standar RelatedFilterSpec with one with the "All"/"Null"/"Not null" options.
It applies to all relational fields (ForeignKey, ManyToManyField).
You can put the code in the `__init__.py` or wherever you want.
The `_register_front` idea is copied on [this snippet](http://djangosnippets.org/snippets/1963/)
**UPDATE: Now works in Django 1.4**
Based on luc_j:s snippet (http://djangosnippets.org/snippets/2108/) to show values in ManyToManyFields in the admin. This snippets does that, but also links each value to its corresponding admin change page.
To use, just set the raw_id_fields to the value you want, and let your form inherit from ImproveRawIdFieldsForm.
This creates an admin interface for each model in the "your_appname" app. It also adds each column to the admin list view.
Place this in the admin.py of "your_appname".
Using jQuery UI (with Grappelli in use) to add "drag and drop" reordering of items in the admin list view. The model must have an "order" field to store the order value in.
You've filtered your changelist in your admin site and you want to edit a few entries here; you click on an object, edit it and press save, and you end up back at the default unfiltered changelist view. This ModelAdmin override is so that if you press "save" (not "save and add another", or "save and continue editing") you end up back at your filtered changelist.
There are other ways out there and other snippets to do similar; however I hadn't seen one to only redirect if you pressed save so this is what I came up with. Hopefully it's useful.
Point '^accounts/login/$' or whatever your custom login path is to the 'negotiate_ntlm' view.
This allows you to keep anonymous authentication enabled on IIS and easily lock down just the parts of the site you need to (e.g. [admin](http://djangosnippets.org/snippets/2127/)).
Forces admin site to use your custom login.
Very useful when using RemoteUserBackend.
See [here](http://djangosnippets.org/snippets/2128/) for a use case.
The new changelist supports clicking on a column header to order by that column, like iTunes. Unlike iTunes, which sorts by track number if you click the Artist or Album column header, it can only order by the column clicked on. By adding a property to my ModelAdmin, and subclassing ChangeList, I was able to make it also sort by track number when sorting by Artist or Album.
[Blog post](http://python-web.blogspot.com/2010/07/sorting-by-more-than-one-field-in-admin.html)
[Repository with full example](http://github.com/benatkin/tuneage)
This middleware will prevent access to the admin if the users IP isn't in the INTERNAL_IPS setting, by comparing the request path with the reversed index URL of the default admin site, ultimately raising a 404 (unless DEBUG = True).
Automatically register models for the Django-admin.
This snippet aids in the process of keeping your admin.py up-to-date with the models in your apps, have all models automatically added to the admin and reflect any future changes without updating the file.
[zweckdev.com](http://zweckdev.com/)
Adds drag-and-drop ordering of rows in the admin list view.
The only requirements is that the model has a field holding the position and that the field is made list_editable in the ModelAdmin. The changes of the ordering are applied after clicking 'Save'.
The included javascript uses [jQuery UI's sortable](http://jqueryui.com/demos/sortable/) plugin
Inspired by snippets [#1053](http://djangosnippets.org/snippets/1053) and [#998](http://djangosnippets.org/snippets/998/). Another similar snippet using AJAX is [#2047](http://djangosnippets.org/snippets/2047/).
Makes models orderable on the change list page of the admin using drag and drop with jQuery UI (via sortable()). So you can order your objects in more easy way.
Inspired by snippets [#1053](http://djangosnippets.org/snippets/1053/) and [#998](http://djangosnippets.org/snippets/998/)
First, ordering field to your model (default called 'order). You can specify other name for this field, but you should add 'order_field' attr to model (i.e order_field = 'your_new_order_field_name')
Also, snippet adds 'order_link' field to admin's changelist and hides it by javascript.