Documentation fix in comments customization page

[Thejaswi Puthraya]

The current documentation mentions that all the custom comment models must subclass from the BaseCommentAbstractModel which is not totally right.
In the example in the documentation, it adds a title field to the model after subclassing from BaseCommentAbstractModel but the form subclassed from CommentForm displays the Name, Email, URL etc. So these extra form fields like Name, Email etc are not saved into the db and is an easy way of confusing people.

Ideally, most cases would require to just subclass from the Comment model. Only in special cases, there will be a requirement to subclass from the BaseCommentAbstractModel.

So I have added a patch to clarify in the documentation.

[Thejaswi Puthraya]

git-patch against the latest checkout

[Malcolm Tredinnick]

Documentation fixes aren't feature additions. Slow down a bit with moving things to 1.1 beta. This is a normal bug that will be fixed in the normal flow of things.

[Thejaswi Puthraya]

Replying to mtredinnick:

Documentation fixes aren't feature additions. Slow down a bit with moving things to 1.1 beta. This is a normal bug that will be fixed in the normal flow of things.

Sorry about mis-labeling and thanks for pointing out the difference between the 1.1 and 1.1beta tag.

[Russell Keith-Magee]

(In [10566]) Fixed #10559 -- Clarified documentation on customization of comments pages. Thanks to Thejaswi Puthraya for the patch.

[Jacob]

Milestone 1.1 deleted