Removed obsolete contrib.comments upgrade guide
The old comment system was pre-1.0.
This commit is contained in:
parent
35a0fff28a
commit
44815bad6b
|
@ -11,12 +11,6 @@ Django includes a simple, yet customizable comments framework. The built-in
|
|||
comments framework can be used to attach comments to any model, so you can use
|
||||
it for comments on blog entries, photos, book chapters, or anything else.
|
||||
|
||||
.. note::
|
||||
|
||||
If you used to use Django's older (undocumented) comments framework, you'll
|
||||
need to upgrade. See the :doc:`upgrade guide </ref/contrib/comments/upgrade>`
|
||||
for instructions.
|
||||
|
||||
Quick start guide
|
||||
=================
|
||||
|
||||
|
@ -350,7 +344,6 @@ More information
|
|||
models
|
||||
settings
|
||||
signals
|
||||
upgrade
|
||||
custom
|
||||
forms
|
||||
moderation
|
||||
|
|
|
@ -1,78 +0,0 @@
|
|||
===============================================
|
||||
Upgrading from Django's previous comment system
|
||||
===============================================
|
||||
|
||||
Prior versions of Django included an outdated, undocumented comment system. Users who reverse-engineered this framework will need to upgrade to use the
|
||||
new comment system; this guide explains how.
|
||||
|
||||
The main changes from the old system are:
|
||||
|
||||
* This new system is documented.
|
||||
|
||||
* It uses modern Django features like :doc:`forms </topics/forms/index>` and
|
||||
:doc:`modelforms </topics/forms/modelforms>`.
|
||||
|
||||
* It has a single ``Comment`` model instead of separate ``FreeComment`` and
|
||||
``Comment`` models.
|
||||
|
||||
* Comments have "email" and "URL" fields.
|
||||
|
||||
* No ratings, photos and karma. This should only effect World Online.
|
||||
|
||||
* The ``{% comment_form %}`` tag no longer exists. Instead, there's now two
|
||||
functions: ``{% get_comment_form %}``, which returns a form for posting a
|
||||
new comment, and ``{% render_comment_form %}``, which renders said form
|
||||
using the ``comments/form.html`` template.
|
||||
|
||||
* The way comments are include in your URLconf have changed; you'll need to
|
||||
replace::
|
||||
|
||||
(r'^comments/', include('django.contrib.comments.urls.comments')),
|
||||
|
||||
with::
|
||||
|
||||
(r'^comments/', include('django.contrib.comments.urls')),
|
||||
|
||||
Upgrading data
|
||||
--------------
|
||||
|
||||
The data models for Django's comment system have changed, as have the
|
||||
table names. Before you transfer your existing data into the new comments
|
||||
system, make sure that you have installed the new comments system as
|
||||
explained in the
|
||||
:doc:`quick start guide </ref/contrib/comments/index>`.
|
||||
This will ensure that the new tables have been properly created.
|
||||
|
||||
To transfer your data into the new comments system, you'll need to directly
|
||||
run the following SQL:
|
||||
|
||||
.. code-block:: sql
|
||||
|
||||
BEGIN;
|
||||
|
||||
INSERT INTO django_comments
|
||||
(content_type_id, object_pk, site_id, user_name, user_email, user_url,
|
||||
comment, submit_date, ip_address, is_public, is_removed)
|
||||
SELECT
|
||||
content_type_id, object_id, site_id, person_name, '', '', comment,
|
||||
submit_date, ip_address, is_public, not approved
|
||||
FROM comments_freecomment;
|
||||
|
||||
INSERT INTO django_comments
|
||||
(content_type_id, object_pk, site_id, user_id, user_name, user_email,
|
||||
user_url, comment, submit_date, ip_address, is_public, is_removed)
|
||||
SELECT
|
||||
content_type_id, object_id, site_id, user_id, '', '', '', comment,
|
||||
submit_date, ip_address, is_public, is_removed
|
||||
FROM comments_comment;
|
||||
|
||||
UPDATE django_comments SET user_name = (
|
||||
SELECT username FROM auth_user
|
||||
WHERE django_comments.user_id = auth_user.id
|
||||
) WHERE django_comments.user_id is not NULL;
|
||||
UPDATE django_comments SET user_email = (
|
||||
SELECT email FROM auth_user
|
||||
WHERE django_comments.user_id = auth_user.id
|
||||
) WHERE django_comments.user_id is not NULL;
|
||||
|
||||
COMMIT;
|
|
@ -32,8 +32,8 @@ Refactored ``django.contrib.comments``
|
|||
carried out a major rewrite and refactoring of Django's bundled
|
||||
comment system, greatly increasing its flexibility and
|
||||
customizability. :doc:`Full documentation
|
||||
</ref/contrib/comments/index>` is available, as well as :doc:`an
|
||||
upgrade guide </ref/contrib/comments/upgrade>` if you were using
|
||||
</ref/contrib/comments/index>` is available, as well as an
|
||||
upgrade guide if you were using
|
||||
the previous incarnation of the comments application..
|
||||
|
||||
Refactored documentation
|
||||
|
|
|
@ -391,8 +391,8 @@ Comments
|
|||
--------
|
||||
|
||||
If you were using Django 0.96's ``django.contrib.comments`` app, you'll need to
|
||||
upgrade to the new comments app introduced in 1.0. See
|
||||
:doc:`/ref/contrib/comments/upgrade` for details.
|
||||
upgrade to the new comments app introduced in 1.0. See the upgrade guide
|
||||
for details.
|
||||
|
||||
Template tags
|
||||
-------------
|
||||
|
|
|
@ -194,8 +194,8 @@ Refactored ``django.contrib.comments``
|
|||
As part of a Google Summer of Code project, Thejaswi Puthraya carried out a
|
||||
major rewrite and refactoring of Django's bundled comment system, greatly
|
||||
increasing its flexibility and customizability. :doc:`Full documentation
|
||||
</ref/contrib/comments/index>` is available, as well as :doc:`an upgrade guide
|
||||
</ref/contrib/comments/upgrade>` if you were using the previous incarnation of
|
||||
</ref/contrib/comments/index>` is available, as well as an upgrade guide
|
||||
if you were using the previous incarnation of
|
||||
the comments application.
|
||||
|
||||
Removal of deprecated features
|
||||
|
|
Loading…
Reference in New Issue