Ticket #12871: auth_comments.diff

docs/ref/contrib/comments/index.txt

@@ -288 +288 @@
 
 .. _honeypot: http://en.wikipedia.org/wiki/Honeypot_(computing)
 
+
+Providing a comment form for authenticated users
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If a user is already authenticated, it makes little sense to display name, email,
+and URL fields, since these can already be retrieved from their login data and
+profile. In addition, some sites will only accept comments from authenticated users.
+
+To provide a comment form for authenticated users, build the form manually in your
+template as above, but manually provide the additional fields expected by the
+Django comments framework. For example, assuming comments are attached to the model
+"item"::
+
+    {% if user.is_authenticated %}
+        {% get_comment_form for item as form %} 
+        <form action="{% comment_form_target %}" method="POST"> 
+        {% csrf_token %}
+        {{ form.comment }} 
+        {{ form.honeypot }} 
+        {{ form.content_type }} 
+        {{ form.object_pk }} 
+        {{ form.timestamp }} 
+        {{ form.security_hash }} 
+        <input type="hidden" name="next" value="{% url item_view item.id %}" />
+        <input type="submit" value="Add comment" id="id_submit" /> 
+        </form> 
+    {% else %}
+        <p>Please <a href="{% url auth_login %}">log in</a> to leave a comment.</p>
+    {% endif %}
+
+In this example, the honeypot field will still be visible to the user; you'll need
+to hide that field in your CSS::
+
+    #id_honeypot {
+        visibility:hidden;
+    }
+
+If you want to accept either anonymous or authenticated comments, replace the 
+auth_login line above with a standard comment form, and the right thing will happen
+whether a user is logged in or not.
+
 More information
 ================