Perhaps it was used by d.c.comments before we axed it?
--
Ticket URL: <https://code.djangoproject.com/ticket/25262>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by timgraham):
[https://groups.google.com/d/topic/django-
developers/XNe_BoomNyo/discussion django-developers discussion]
--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:1>
* stage: Unreviewed => Accepted
* easy: 0 => 1
Comment:
From the thread:
Me: A compromise could be to hide the field in the default ModelAdmin and
let those who want it to enable it with a custom ModelAdmin. What do you
think?
[[BR]]
Aymeric: That would resolve my problem of “WTF is this field” without
causing too much headache. We should also put a comment in the source code
stating that the field is unused but we don’t want to remove it because of
backwards-compatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:2>
* owner: nobody => Y3K
* status: new => assigned
Comment:
I'll take this one, as my first Django ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:3>
* has_patch: 0 => 1
Comment:
Github pull request: https://github.com/django/django/pull/5204
* Removed the field `enable_comments` from the `FlatPageAdmin` class.
* Added the change to release notes for 1.9
* Added the change to FlatPage documentation
--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b649f68649b0cba2de9e6bb8cf3d3fe468372c2e" b649f68]:
{{{
#!CommitTicketReference repository=""
revision="b649f68649b0cba2de9e6bb8cf3d3fe468372c2e"
Fixed #25262 -- Removed the enable_comments field from FlatPageAdmin.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25262#comment:5>