Fixed #22547 -- Added some links to tutorial 2.
Thanks bjb at sourcer.ca for the suggestion.
This commit is contained in:
parent
e049c88603
commit
b0d032f9fc
|
@ -204,7 +204,8 @@ up into fieldsets:
|
||||||
|
|
||||||
admin.site.register(Question, QuestionAdmin)
|
admin.site.register(Question, QuestionAdmin)
|
||||||
|
|
||||||
The first element of each tuple in ``fieldsets`` is the title of the fieldset.
|
The first element of each tuple in
|
||||||
|
:attr:`~django.contrib.admin.ModelAdmin.fieldsets` is the title of the fieldset.
|
||||||
Here's what our form looks like now:
|
Here's what our form looks like now:
|
||||||
|
|
||||||
.. image:: _images/admin08t.png
|
.. image:: _images/admin08t.png
|
||||||
|
@ -350,8 +351,9 @@ Here's what it looks like at this point:
|
||||||
|
|
||||||
By default, Django displays the ``str()`` of each object. But sometimes it'd be
|
By default, Django displays the ``str()`` of each object. But sometimes it'd be
|
||||||
more helpful if we could display individual fields. To do that, use the
|
more helpful if we could display individual fields. To do that, use the
|
||||||
``list_display`` admin option, which is a tuple of field names to display, as
|
:attr:`~django.contrib.admin.ModelAdmin.list_display` admin option, which is a
|
||||||
columns, on the change list page for the object:
|
tuple of field names to display, as columns, on the change list page for the
|
||||||
|
object:
|
||||||
|
|
||||||
.. snippet::
|
.. snippet::
|
||||||
:filename: polls/admin.py
|
:filename: polls/admin.py
|
||||||
|
@ -396,8 +398,10 @@ attributes, as follows:
|
||||||
was_published_recently.boolean = True
|
was_published_recently.boolean = True
|
||||||
was_published_recently.short_description = 'Published recently?'
|
was_published_recently.short_description = 'Published recently?'
|
||||||
|
|
||||||
Edit your :file:`polls/admin.py` file again and add an improvement to the Question
|
Edit your :file:`polls/admin.py` file again and add an improvement to the
|
||||||
change list page: Filters. Add the following line to ``QuestionAdmin``::
|
``Question`` change list page: filters using the
|
||||||
|
:attr:`~django.contrib.admin.ModelAdmin.list_filter`. Add the following line to
|
||||||
|
``QuestionAdmin``::
|
||||||
|
|
||||||
list_filter = ['pub_date']
|
list_filter = ['pub_date']
|
||||||
|
|
||||||
|
@ -423,9 +427,13 @@ scenes, limiting the number of search fields to a reasonable number will make
|
||||||
it easier for your database to do the search.
|
it easier for your database to do the search.
|
||||||
|
|
||||||
Now's also a good time to note that change lists give you free pagination. The
|
Now's also a good time to note that change lists give you free pagination. The
|
||||||
default is to display 100 items per page. Change-list pagination, search boxes,
|
default is to display 100 items per page. :attr:`Change list pagination
|
||||||
filters, date-hierarchies and column-header-ordering all work together like you
|
<django.contrib.admin.ModelAdmin.list_per_page>`, :attr:`search boxes
|
||||||
think they should.
|
<django.contrib.admin.ModelAdmin.search_fields>`, :attr:`filters
|
||||||
|
<django.contrib.admin.ModelAdmin.list_filter>`, :attr:`date-hierarchies
|
||||||
|
<django.contrib.admin.ModelAdmin.date_hierarchy>`, and
|
||||||
|
:attr:`column-header-ordering <django.contrib.admin.ModelAdmin.list_display>`
|
||||||
|
all work together like you think they should.
|
||||||
|
|
||||||
Customize the admin look and feel
|
Customize the admin look and feel
|
||||||
=================================
|
=================================
|
||||||
|
|
Loading…
Reference in New Issue