Fixed #4133 -- Fixed broken links in docs. Thanks, Gary Wilson
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5064 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
53eddd4a0f
commit
39aa40d108
|
@ -100,14 +100,14 @@ change:
|
|||
|
||||
.. _caching: ../cache/
|
||||
.. _custom template tags and libraries: ../templates_python/
|
||||
.. _database lookup: ../db_api/
|
||||
.. _database lookup: ../db-api/
|
||||
.. _django-admin utility: ../django-admin/
|
||||
.. _fastcgi integration: ../fastcgi/
|
||||
.. _flatpages: ../flatpages/
|
||||
.. _generic views: ../generic_views/
|
||||
.. _internationalization: ../i18n/
|
||||
.. _legacy database integration: ../legacy_databases/
|
||||
.. _model definition: ../model_api/
|
||||
.. _model definition: ../model-api/
|
||||
.. _mod_python integration: ../modpython/
|
||||
.. _redirects: ../redirects/
|
||||
.. _request/response objects: ../request_response/
|
||||
|
|
|
@ -144,7 +144,7 @@ custom methods:
|
|||
Raises ``django.contrib.auth.models.SiteProfileNotAvailable`` if the current site
|
||||
doesn't allow profiles.
|
||||
|
||||
.. _Django model: ../model_api/
|
||||
.. _Django model: ../model-api/
|
||||
.. _DEFAULT_FROM_EMAIL: ../settings/#default-from-email
|
||||
|
||||
Manager functions
|
||||
|
@ -757,7 +757,7 @@ This example model creates three custom permissions::
|
|||
The only thing this does is create those extra permissions when you run
|
||||
``syncdb``.
|
||||
|
||||
.. _model Meta attribute: ../model_api/#meta-options
|
||||
.. _model Meta attribute: ../model-api/#meta-options
|
||||
|
||||
API reference
|
||||
-------------
|
||||
|
|
|
@ -6,7 +6,7 @@ Once you've created your `data models`_, Django automatically gives you a
|
|||
database-abstraction API that lets you create, retrieve, update and delete
|
||||
objects. This document explains that API.
|
||||
|
||||
.. _`data models`: ../model_api/
|
||||
.. _`data models`: ../model-api/
|
||||
|
||||
Throughout this reference, we'll refer to the following models, which comprise
|
||||
a weblog application::
|
||||
|
@ -85,7 +85,7 @@ There's no way to tell what the value of an ID will be before you call
|
|||
unless you explicitly specify ``primary_key=True`` on a field. See the
|
||||
`AutoField documentation`_.)
|
||||
|
||||
.. _AutoField documentation: ../model_api/#autofield
|
||||
.. _AutoField documentation: ../model-api/#autofield
|
||||
|
||||
Explicitly specifying auto-primary-key values
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -1801,4 +1801,4 @@ interface to your database. You can access your database via other tools,
|
|||
programming languages or database frameworks; there's nothing Django-specific
|
||||
about your database.
|
||||
|
||||
.. _Executing custom SQL: ../model_api/#executing-custom-sql
|
||||
.. _Executing custom SQL: ../model-api/#executing-custom-sql
|
||||
|
|
|
@ -512,7 +512,7 @@ type, create an initial data file and put something like this in it::
|
|||
As explained in the `SQL initial data file`_ documentation, this SQL file can
|
||||
contain arbitrary SQL, so you can make any sorts of changes you need to make.
|
||||
|
||||
.. _SQL initial data file: ../model_api/#providing-initial-sql-data
|
||||
.. _SQL initial data file: ../model-api/#providing-initial-sql-data
|
||||
|
||||
Why is Django leaking memory?
|
||||
-----------------------------
|
||||
|
|
|
@ -84,9 +84,9 @@ Flatpages are represented by a standard `Django model`_, which lives in
|
|||
`django/contrib/flatpages/models.py`_. You can access flatpage objects via the
|
||||
`Django database API`_.
|
||||
|
||||
.. _Django model: ../model_api/
|
||||
.. _Django model: ../model-api/
|
||||
.. _django/contrib/flatpages/models.py: http://code.djangoproject.com/browser/django/trunk/django/contrib/flatpages/models.py
|
||||
.. _Django database API: ../db_api/
|
||||
.. _Django database API: ../db-api/
|
||||
|
||||
Flatpage templates
|
||||
==================
|
||||
|
|
|
@ -691,5 +691,5 @@ fails. If no message is passed in, a default message is used.
|
|||
document for more details).
|
||||
|
||||
.. _`generic views`: ../generic_views/
|
||||
.. _`models API`: ../model_api/
|
||||
.. _`models API`: ../model-api/
|
||||
.. _settings: ../settings/
|
||||
|
|
|
@ -71,7 +71,7 @@ are first evaluated, so if you want to pass in a QuerySet via
|
|||
``extra_context`` that is always fresh you need to wrap it in a function or
|
||||
lambda that returns the QuerySet.
|
||||
|
||||
.. _database API docs: ../db_api/
|
||||
.. _database API docs: ../db-api/
|
||||
|
||||
"Simple" generic views
|
||||
======================
|
||||
|
|
|
@ -175,7 +175,7 @@ class, though::
|
|||
verbose_name = _('my thing')
|
||||
verbose_name_plural = _('mythings')
|
||||
|
||||
.. _Django models: ../model_api/
|
||||
.. _Django models: ../model-api/
|
||||
|
||||
Pluralization
|
||||
~~~~~~~~~~~~~
|
||||
|
|
|
@ -66,6 +66,6 @@ Redirects are represented by a standard `Django model`_, which lives in
|
|||
`django/contrib/redirects/models.py`_. You can access redirect
|
||||
objects via the `Django database API`_.
|
||||
|
||||
.. _Django model: ../model_api/
|
||||
.. _Django model: ../model-api/
|
||||
.. _django/contrib/redirects/models.py: http://code.djangoproject.com/browser/django/trunk/django/contrib/redirects/models.py
|
||||
.. _Django database API: ../db_api/
|
||||
.. _Django database API: ../db-api/
|
||||
|
|
|
@ -27,7 +27,7 @@ data to (see `Serialization formats`_) and a QuerySet_ to serialize.
|
|||
(Actually, the second argument can be any iterator that yields Django objects,
|
||||
but it'll almost always be a QuerySet).
|
||||
|
||||
.. _QuerySet: ../db_api/#retrieving-objects
|
||||
.. _QuerySet: ../db-api/#retrieving-objects
|
||||
|
||||
You can also use a serializer object directly::
|
||||
|
||||
|
|
|
@ -874,7 +874,7 @@ Default: ``Django/<version> (http://www.djangoproject.com/)``
|
|||
The string to use as the ``User-Agent`` header when checking to see if URLs
|
||||
exist (see the ``verify_exists`` option on URLField_).
|
||||
|
||||
.. _URLField: ../model_api/#urlfield
|
||||
.. _URLField: ../model-api/#urlfield
|
||||
|
||||
USE_ETAGS
|
||||
---------
|
||||
|
|
|
@ -276,8 +276,8 @@ you want your admin site to have access to all objects (not just site-specific
|
|||
ones), put ``objects = models.Manager()`` in your model, before you define
|
||||
``CurrentSiteManager``.
|
||||
|
||||
.. _manager: ../model_api/#managers
|
||||
.. _manager documentation: ../model_api/#managers
|
||||
.. _manager: ../model-api/#managers
|
||||
.. _manager documentation: ../model-api/#managers
|
||||
|
||||
How Django uses the sites framework
|
||||
===================================
|
||||
|
|
|
@ -159,7 +159,7 @@ put into those elements.
|
|||
{{ obj.description }}
|
||||
|
||||
.. _chicagocrime.org: http://www.chicagocrime.org/
|
||||
.. _object-relational mapper: ../db_api/
|
||||
.. _object-relational mapper: ../db-api/
|
||||
.. _Django templates: ../templates/
|
||||
|
||||
A complex example
|
||||
|
|
|
@ -577,5 +577,5 @@ For full details on the database API, see our `Database API reference`_.
|
|||
When you're comfortable with the API, read `part 2 of this tutorial`_ to get
|
||||
Django's automatic admin working.
|
||||
|
||||
.. _Database API reference: ../db_api/
|
||||
.. _Database API reference: ../db-api/
|
||||
.. _part 2 of this tutorial: ../tutorial02/
|
||||
|
|
|
@ -219,7 +219,7 @@ template. Note that we use ``dict()`` to return an altered dictionary in place.
|
|||
If you'd like to know more about how that works, The Django database API
|
||||
documentation `explains the lazy nature of QuerySet objects`_.
|
||||
|
||||
.. _explains the lazy nature of QuerySet objects: ../db_api/#querysets-are-lazy
|
||||
.. _explains the lazy nature of QuerySet objects: ../db-api/#querysets-are-lazy
|
||||
|
||||
In previous parts of the tutorial, the templates have been provided with a context
|
||||
that contains the ``poll`` and ``latest_poll_list`` context variables. However,
|
||||
|
|
Loading…
Reference in New Issue