mirror of
https://github.com/django/django.git
synced 2025-12-15 21:45:20 +00:00
Fixed #14112 -- Various Markup fixes for the docs. Thanks to ramiro for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13628 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
5d4c37af7c
commit
a323fd3c5e
11 changed files with 74 additions and 29 deletions
|
|
@ -5,8 +5,6 @@ The Django admin site
|
|||
.. module:: django.contrib.admin
|
||||
:synopsis: Django's admin site.
|
||||
|
||||
.. currentmodule:: django.contrib.admin
|
||||
|
||||
One of the most powerful parts of Django is the automatic admin interface. It
|
||||
reads metadata in your model to provide a powerful and production-ready
|
||||
interface that content producers can immediately use to start adding content to
|
||||
|
|
@ -831,7 +829,7 @@ problems:
|
|||
|
||||
Since this is usually not what you want, Django provides a convenience wrapper
|
||||
to check permissions and mark the view as non-cacheable. This wrapper is
|
||||
:meth:`AdminSite.admin_view` (i.e. ``self.admin_site.admin_view`` inside a
|
||||
:meth:`AdminSite.admin_view` (i.e. ``self.admin_site.admin_view`` inside a
|
||||
``ModelAdmin`` instance); use it like so::
|
||||
|
||||
class MyModelAdmin(admin.ModelAdmin):
|
||||
|
|
@ -1010,6 +1008,8 @@ information.
|
|||
``InlineModelAdmin`` objects
|
||||
============================
|
||||
|
||||
.. class:: InlineModelAdmin
|
||||
|
||||
The admin interface has the ability to edit models on the same page as a
|
||||
parent model. These are called inlines. Suppose you have these two models::
|
||||
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ Methods on ``ContentType`` instances
|
|||
|
||||
Takes a set of valid :ref:`lookup arguments <field-lookups-intro>` for the
|
||||
model the :class:`~django.contrib.contenttypes.models.ContentType`
|
||||
represents, and does :ref:`a get() lookup <get-kwargs>` on that model,
|
||||
represents, and does :lookup:`a get() lookup <get>` on that model,
|
||||
returning the corresponding object.
|
||||
|
||||
.. method:: models.ContentType.model_class()
|
||||
|
|
@ -370,7 +370,7 @@ This enables the use of generic relations in forms and the admin. See the
|
|||
|
||||
The :class:`~django.contrib.contenttypes.generic.GenericInlineModelAdmin`
|
||||
class inherits all properties from an
|
||||
:class:`~django.contrib.admin.options.InlineModelAdmin` class. However,
|
||||
:class:`~django.contrib.admin.InlineModelAdmin` class. However,
|
||||
it adds a couple of its own for working with the generic relation:
|
||||
|
||||
.. attribute:: generic.GenericInlineModelAdmin.ct_field
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ You will need to download the `initialization SQL`__ script for SpatiaLite::
|
|||
If ``init_spatialite-2.3.sql`` is in the same path as your project's ``manage.py``,
|
||||
then all you have to do is::
|
||||
|
||||
$ python manage.py test
|
||||
$ python manage.py test
|
||||
|
||||
Settings
|
||||
--------
|
||||
|
|
@ -166,9 +166,9 @@ must be used. To use this runner, configure :setting:`TEST_RUNNER` as follows::
|
|||
|
||||
.. note::
|
||||
|
||||
In order to create a spatial database, the :setting:`DATABASE_USER` setting
|
||||
(or :setting:`TEST_DATABASE_USER`, if optionally defined on Oracle) requires
|
||||
elevated privileges. When using PostGIS or MySQL, the database user
|
||||
In order to create a spatial database, the :setting:`USER` setting
|
||||
(or :setting:`TEST_USER`, if optionally defined on Oracle) requires
|
||||
elevated privileges. When using PostGIS or MySQL, the database user
|
||||
must have at least the ability to create databases. When testing on Oracle,
|
||||
the user should be a superuser.
|
||||
|
||||
|
|
|
|||
|
|
@ -166,8 +166,9 @@ For more documentation, read the source code in
|
|||
ReStructured Text
|
||||
-----------------
|
||||
|
||||
When using the `restructuredtext` markup filter you can define a :setting:`RESTRUCTUREDTEXT_FORMAT_SETTINGS`
|
||||
in your django settings to override the default writer settings. See the `restructuredtext writer settings`_ for
|
||||
When using the ``restructuredtext`` markup filter you can define a
|
||||
:setting:`RESTRUCTUREDTEXT_FILTER_SETTINGS` in your django settings to override
|
||||
the default writer settings. See the `restructuredtext writer settings`_ for
|
||||
details on what these settings are.
|
||||
|
||||
.. _restructuredtext writer settings: http://docutils.sourceforge.net/docs/user/config.html#html4css1-writer
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue