James Bennett avatar James Bennett committed 7daa4c8

Some doc updates, only partially finished.

Comments (0)

Files changed (2)

docs/quickstart.rst

 ~~~~~~~~~~~~~~~~~
 
 Begin by adding ``registration`` to the ``INSTALLED_APPS`` setting of
-your project, and specifying two additional settings:
+your project, and specifying one additional setting:
 
 ``ACCOUNT_ACTIVATION_DAYS``
     This is the number of days users will have to activate their
     that period, the account will remain permanently inactive and may
     be deleted by maintenance scripts provided in django-registration.
 
-``REGISTRATION_BACKEND``
-    This tells django-registration which backend to use for user
-    registration. Set this to
-    ``"registration.backends.default.DefaultBackend"``.
-
 For example, you might have something like the following in your
 Django settings file::
 
     )
     
     ACCOUNT_ACTIVATION_DAYS = 7 # One-week activation window; you may, of course, use a different value.
-    
-    REGISTRATION_BACKEND = "registration.backends.default.DefaultBackend"
 
 Once you've done this, run ``manage.py syncdb`` to install the model
 used by the default setup.
 ------------------------------
 
 To upgrade from a previous version of django-registration, you will
-need to make two changes, both to project configuration.
-
-First, add the setting ``REGISTRATION_BACKEND``, and set it to
-``"registration.backends.default.DefaultBackend"``. This is required
-to support the primary new feature in 0.8 (pluggable backends
-implementing different registration schemes), and will enable a
-backend which provides behavior identical to previous releases of
-django-registration.
-
-Then, if you were using the default ``URLConf`` provided in previous
-versions, you will instead need to use the ``URLConf`` provided by the
-default backend in 0.8, which is located at
-``registration.backends.default.urls``. So, for example, if you
-previously had this in your ``URLConf``::
+need to make one change, to your project's configuration: if you were
+using the default ``URLConf`` provided in previous versions, you will
+instead need to use the ``URLConf`` provided by the default backend in
+0.8, which is located at ``registration.backends.default.urls``. So,
+for example, if you previously had this in your ``URLConf``::
 
     (r'^accounts/', include('registration.urls')),
 
 you will need to change it to::
 
     (r'^accounts/', include('registration.backends.default.urls')),
+
+If you had set up custom URL patterns, you will need to consult the
+documentation for the registration views to see how to adapt your
+custom URL patterns for use with django-registration 0.8.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.