django-utensils 0.2

SearchForm

Generic search form that can be used on any page.

Used by viewmixins.SearchFormMixin.

UniqueModelFieldsMixin

Mixin that enforces unique fields on ModelForm form fields.

Must be left of ModelForm when defining the form class (see https://code.djangoproject.com/ticket/13075).

There are two ways to list your unique fields depending on whether or not you want case insensitivity.

unique_fields = ['name', 'username']
unique_fields = ['name',  {'field': 'username', 'case_insensitive': True}]

List view pagination

The PaginateMixin returns the paginate by setting used by the pagination template tag {% pagination %} so the Django ListView functions can use it.

You will need to add utensils.context_processors.pagination to your context processors for the template tag to work. Set settings.PAGINATION_PAGE_SIZES to control the page size, if not set the default [20, 50, 100] is used.

List view ordering

The OrderByMixin allows easy ordering of list views. By including it the template tag ({% order_by 'field_name' %}) is given sorting context variables to work with. get_queryset is overidden to make use of these and order the object list.

Generic single-field search

The SearchFormMixin provides a handy way to add search to list views. Add the search_form manually in your template or use the included fragment {% include 'fragments/_search.html' %}.

Specify the fields you wish to search on, and how, by including a search_fields dictionary on your view like so:

class CustomerListView(SearchFormMixin, ListView):
    model = Customer
    search_fields = {
        'user__email':  'icontains',
        'first_name':   'icontains',
        'last_name':    'icontains',
        'postal_code':  'icontains',
    }

MessageMixin

By including and providing success_message and/or error_message attributes on your view class, messages will be added automatically to the request objects on events suchs as valid and invalid forms and formsets, object deletion etc.

PermissionRequiredMixin

This mixin verfies the user is logged in and has the required permissions to access the view. It’s a modified version of the django-braces mixin with an added bypass. Setting permission_required = False allows you to skip the check whilst keeping the mixin in a base view used across a project, for example.

Settings:

• permission_required - the permission to check for or False to skip check

• login_url - the login url of site

• redirect_field_name - defaults to “next”

• raise_exception - defaults to False - raise 403 if set to True

RedirectToNextMixin

If a next query string parameter is preset on a post() call it is assigned to the instance success_url.

StaffViewMixin

Combines MessageMixin, RedirectToNextMixin, StaffuserRequiredMixin (from django-brances), PermissionRequiredMixin to create a useful mixin that can be used on all staff views.

BaseListView

This view combines the pagination, order by and search mixins and adds an optional query set filter description that your templates can use.

class ActiveCustomerList(BaseListView):
    filter_description = u"Active"
    queryset = Customer.active.all()

{% block content %}
  <h2>
    {% if filter_description %}
      {{ filter_description|title }} customers
    {% else %}
      Customers
    {% endif %}
  </h2>
  <!-- more template -->
{% end block %}

Yields:

<h2>Active customers<h2>
<!-- more template -->

SetModelFieldView

This view can be used to set the value of a field on a model instance. GET will display a template (and should be used as a confirmation page) and the value will be set on POST. The view uses django.views.generic.detail.BaseDetailView to provide get_object().

class CustomerInactiveView(SetModelFieldView):
    """
    Ask the user if they're sure they want to make the customer inactive. If
    they confirm by submitting the form set is_active to False and save.
    """
    model = Customer
    field = 'is_active'
    value = False
    template_name = "customers/customer_inactive.html"

If you require more control and want to introduce some logic when selecting the value or field to alter you can override get_field() and get_value() instead of setting the field and value class attributes.