Prior to this change, it was possible to select child products in the
product dashboard. A new function get_parent_products_queryset was
introduced, analogues to the existing get_related_products_queryset. It
is not based on the BrowsableManager as I can envision scenarios where
that is extended to respect status fields or such like, which we should
ignore when selecting a parent field. Otherwise it wouldn't be possible
to e.g. add a few hidden products with child products.

Two issues in tests with the G library were fixed as well, were
unintentionally child products were created. If the product field is
left unspecified, it seems to pick a product instead of leaving it as
None.

Both first view and successive view's query counts have been halved.
First view query count dropped from 99 to 45.

It was causing problems with Excel, which didn't recognise it and showed
a strange symbol.  I can't find a compelling reason to keep it, so it
goes.

Most mixins will override functions of base classes and hence belong
before them.

Fixes #818

In a few cases, django.templatefilters.date was used to format a
datetime as string. This filters expects localtime, but was always
passed time in UTC.
Introduced a helper function that should be used instead of the template
filter.

A recent change to the URL pattern means these don't resolve.

The intention was to disable autocompletion for the title, which should
now work.

This requires a formset for stockrecords instead of a single form (which
actually is easier to handle than the previous situation).  We have to
pass the product_class through to the formset forms though which is
mildly tricky.

- Make get_primary_address a property
- Assign partner to address when creating a new one (fixes a bug)
- Only show success messages after a success

As Oscar is only shipping with support for one partner address by
default, it made sense to have it directly editable in the partner
manage view.

Without it, Sphinx' autodoc for oscar.apps.dasboard.views would not
list the view nor it's members.

Caused by reworking of the user creation form.

All code handling email addresses has been update to use a new function
normalise_email, to have one consistent way of handling email addresses.

This function lowercases the domain part of an email address if it can
find an @, so it works on partial addresses as well.

A check in ProductForm's __init__ caused an error when the parent field
is not present. It is reasonable to believe that this field would be
omitted for deployments that sell only canonical products. Hence, the
existence of the field is checked before altering it.

- Only handles Datacash payments at the moment

- Add new block for payment tab
- Rename transactions block
- Provide transactions in get_context_data
- Better handling of empty iterables

Filenames can easily get longer than 100 characters, and that causes
Django to fail hard (I think with a DatabaseError), because it's
currently not validated (see Django #11027)

This fix increases the character limit to 255 chars. Going much higer
can cause trouble with MySQL.

Fixes #625. Thanks for reporting go to @soloweb.

- Add more links
- Add event details to line detail page

Replace with get_full_name to better support User models that don't have
a first_name and last_name.

Now supports Django 1.5. Adapted CategoryForm to use the new
movenodeform_factory to build it's Meta class.

This is required to allow the pages component of the dashboard to
continue to work correctly.

This commit provides two mechanisms for passing format information from
Django to JS.

1. An options object can be passed to the oscar.dashboard.init method
   that provides default values for the formats.  This is optional - the JS
   itself has some hard-coded defaults.

2. Form elements can defined data attributes that specify format
   information directly.  This is implemented for the datetime inputs
   within the offers dashboard.

They weren't using dicts for parameters to work around the ordering
issue.

Avoids a key error when a referer is not available.

Also removed BulkEditMixin from the PartnerListView as it was not used.

null=True is only useful for a few edge cases where one wants to
separate between '' and None.  If null=True was found, it was removed.
If blank=True was not set already, it was set instead.  If default=None
was set, it was removed (defaulting to '').

I then grepped the source code for tests 'is None' and 'is not None',
and checked the instances where default=None was set.

Fixes #584

- Correct breadcrumbs
- Use {{ form.is_bound }} where appropriate
- Rearrange forms on partner detail page
- Add help text to forms

- Merged PartnerUpdate and PartnerUserList view for a better UX
- Created new ExistingUserForm to allow for updating user details
  without changing password
- PartnerUserUpdateView now enforces user being associated to partner
- Added Undo link when unlinking user
- Enrich user details when creating in form instead of view

Use Django conventions for:

- View class names
- app.py view attribute names
- template names

Plus change URL names to try and be as conventional as possible.

- Use conventional breadcrumbs and titles
- Simplify a few things

Details:

- Make translatable some captions in list.html
- Make translatable caption in order_list.html
- Make translatable fieldname in apps/offer/models
- Make translatable caption in range_list.html
- Make translatable values in column 'is_active'
- Make translatable caption in voucher_list.html
- Make clickable link in discount description
- Make translatable caption in voucher_detail.html
- Display full description for field 'Usage'
- Make translatable field 'Promotion type'
- Make translatable caption in review_list.html
- Set output format for value due local settings.  Russians use a comma
  (not a dot) to distinguish between the whole and the remainder.

Fixes #650

- Removed detail view
- Moved Create button to top
- Moved Reset filtering button next to Search button
- Added success messages to update and delete views