Django admin – inline inlines (or, three model editing at once)

Each Answer to this Q is separated by one/two green lines.

I’ve got a set of models that look like this:

class Page(models.Model):
    title = models.CharField(max_length=255)

class LinkSection(models.Model):
    page = models.ForeignKey(Page)
    title = models.CharField(max_length=255)

class Link(models.Model):
    linksection = models.ForeignKey(LinkSection)
    text = models.CharField(max_length=255)
    url = models.URLField()

and an that looks like this:

class LinkInline(admin.TabularInline):
    model = Link
class LinkSectionInline(admin.TabularInline):
    model = LinkSection
    inlines = [ LinkInline, ]
class PageAdmin(admin.ModelAdmin):
    inlines = [ LinkSectionInline, ]

My goal is to get an admin interface that lets me edit everything on one page. The end result of this model structure is that things are generated into a view+template that looks more or less like:

{% for ls in page.linksection_set.objects.all %}
         {% for l in ls.link_set.objects.all %}
        <li><a href="{{l.url}}">{{l.title}}</a></li>
         {% endfor %}
{% endfor %}

I know that the inline-in-an-inline trick fails in the Django admin, as I expected. Does anyone know of a way to allow this kind of three level model editing? Thanks in advance.

You need to create a custom form and template for the LinkSectionInline.

Something like this should work for the form:

LinkFormset = forms.modelformset_factory(Link)
class LinkSectionForm(forms.ModelForm):
    def __init__(self, **kwargs):
        super(LinkSectionForm, self).__init__(**kwargs)
        self.link_formset = LinkFormset(instance=self.instance, 
                               or None,

    def is_valid(self):
        return (super(LinkSectionForm, self).is_valid() and 

    def save(self, commit=True):
        # Supporting commit=False is another can of worms.  No use dealing
        # it before it's needed. (YAGNI)
        assert commit == True 
        res = super(LinkSectionForm, self).save(commit=commit)
        return res

(That just came off the top of my head and isn’t tested, but it should get you going in the right direction.)

Your template just needs to render the form and form.link_formset appropriately.

Django-nested-inlines is built for just this. Usage is simple.

from django.contrib import admin
from nested_inlines.admin import NestedModelAdmin, NestedStackedInline, NestedTabularInline
from models import A, B, C

class MyNestedInline(NestedTabularInline):
    model = C

class MyInline(NestedStackedInline):
    model = B
    inlines = [MyNestedInline,]

class MyAdmin(NestedModelAdmin):
    pass, MyAdmin)

My recommendation would actually be to change your model. Why not have a ForeignKey in Link to LinkSection? Or, if it’s not OneToMany, perhaps a ManyToMany field? The admin interface will generate that for free. Of course, I don’t recommend this if links don’t logically have anything to do with link sections, but maybe they do? If they don’t, please explain what the intended organization is. (For example, is 3 links per section fixed or arbitrary?)

You can create a new class, similar to TabularInline or StackedInline, that is able to use inline fields itself.

Alternatively, you can create new admin templates, specifically for your model. But that of course overrules the nifty features of the admin interface.

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .