view gpp/templates/forums/spammer.html @ 552:9e42e6618168

For bitbucket issue #2, tweak the admin settings for the Post model to reduce slow queries. Define our own queryset() method so we can control the select_related(), and not have it cascade from post to topics to forums to categories. Removed 'topic' from list_display because MySQL still sucked with 2 inner joins. Now it seems to be tolerable with only one join to User.
author Brian Neal <bgneal@gmail.com>
date Wed, 25 Jan 2012 20:07:03 -0600
parents 3c48a555298d
children
line wrap: on
line source
{% extends 'base.html' %}
{% load url from future %}
{% load bio_tags %}
{% block title %}Deactivate Spammer: {{ post.user.username }}{% endblock %}
{% block content %}
<h2>Deactivate Spammer: {{ post.user.username }}</h2>

{% if can_moderate and can_deactivate %}
<p>Please confirm that you wish to mark the user
{% profile_link post.user.username %} as a
spammer based on <a href="{% url 'forums-goto_post' post.id %}">this post</a>. 
If you confirm, the user's account will be deactivated, and all posts and comments
left by the user will be deleted.</p>
<p><strong>This is a drastic action, so please be absolutely sure
you wish to proceed!</strong></p>
<form action="." method="post">{% csrf_token %}
   <input type="submit" value="Deactivate {{ post.user.username }}" />
</form>
{% else %}
   {% if can_moderate %}
   <p>That user is no longer a stranger, and can't be deactivated like this. Please
   contact the site admin if that user is now posting spam.</p>
   {% else %}
   <p>Sorry, but you don't have permission to deactivate spammers in that post's forum.</p>
   {% endif %}
{% endif %}
<hr />
<p>
<a href="{% url 'forums-goto_post' post.id %}">Return to the post</a>.
</p>
{% endblock %}