Outdated piece in Tutorial pt. 2

[michaelw]

Regarding: ​http://docs.djangoproject.com/en/dev/intro/tutorial02

Tabularline seems to have been renamed to Tabularline

and

Stackedeline to Stackedeline

[Russell Keith-Magee]

I can't see what you're referring to. Tabularline and Stackedeline haven't ever been used by Django, and I can't find any reference to them in the docs. TabularInline and StackedInline are used in tutorial 2, but those names are accurate (and have been for some time).

Unless you can provide more specific details as to what you think is wrong, I'm marking this invalid.

[michaelw]

The code in the tutorial does'nt work,

class ChoiceInline(admin.Tabularline):
...

will yield an error since there is no admin.Tabularline

from django.contrib import admin
dir(admin)

['AdminSite', 'HORIZONTAL', 'ModelAdmin', 'StackedInline', 'TabularInline', 'VERTICAL', 'builtins', 'doc', 'file', 'name', 'path', 'autodiscover', 'helpers', 'models', 'options', 'site', 'sites', 'util', 'widgets']

[Russell Keith-Magee]

Again - I can't find anywhere that says "Tabularline". The only section of Tutorial 2 that talks about tabular layout is the following:

Django offers a tabular way of displaying inline related objects; you just need to change the ChoiceInline declaration to read:

class ChoiceInline(admin.TabularInline):
    #...
With that TabularInline (instead of StackedInline), the related objects are displayed in a more compact, table-based format:

This correctly tells you to use Tabular*In*line, not Tabularline. Where are you seeing Tabularline?

[michaelw]

highlighted text, maybe this makes it more obvious

[michaelw]

Maybe the attachment helps.

I had a typo in the ticket creation, i meant to say:

TabularInline seems to have been renamed to Tabularline

[Russell Keith-Magee]

Screenshot of what the last comment should look like.

[Russell Keith-Magee]

It does help - it shows me that there is something very very wrong with your browser.

I've attached a screenshot of what my last comment should look like. I have no idea what is going on here, but your browser and/or font is eating "In"s. The raw HTML for this page contains Tabular*In*line, so something is going wrong with the rendering at your end.

[michaelw]

Haha, true.

Sorry for bothering.

[anonymous]

This is caused by the browser add-on Binnen-I Be Gone. Since Stacked-Inline and Tabular-Inline have "In" in the middle of the word, the add-on thinks they're German words that use nonstandard grammar and tries to fix them.