| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103 |
- =======================
- Oscar 0.6 release notes
- =======================
-
- Welcome to Oscar 0.6!
-
- These release notes cover the `new features`_ as well as `upgrading advice`_.
-
- .. _`new features`: `What's new in Oscar 0.6?`_
- .. _`upgrading advice`: `Upgrading`_
-
- Overview
- ========
-
- ...
-
- What's new in Oscar 0.6?
- ========================
-
- The payment models have been split into abstract- and concrete versions. This
- brings them inline with other Oscar apps and allows them to be customised.
-
- Search
- ~~~~~~
-
- Multi-partner dashboard
- ~~~~~~~~~~~~~~~~~~~~~~~
-
- Demo site
- ~~~~~~~~~
-
- Oscar now ships with a demo site along side the sandbox site. While the sandbox
- is a minimal Django project that uses Oscar with all its defaults, the demo site
- is a more realistic example of an Oscar project. It has a custom skin and makes
- many alterations to the default Oscar behaviour.
-
- It's features include:
-
- * A range of different product types: books, downloads, clothing
- * PayPal Express integration using django-oscar-paypal_
- * Datacash integration using django-oscar-datacash_
-
- .. _django-oscar-paypal: https://github.com/tangentlabs/django-oscar-paypal
- .. _django-oscar-datacash: https://github.com/tangentlabs/django-oscar-datacash
-
- Further reading:
-
- * :doc:`The demo site </internals/sandbox>`.
-
- Django 1.5 and custom user model support
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- Oscar now supports `custom user models`_, the headline new feature in Django 1.5. These can be used standalone
- or with a one-to-one profile model: Oscar's account forms inspect the model
- fields to dynamically pick up the fields for editing and display.
-
- There are some restrictions on what fields a custom user model must have. For
- instance, Oscar's default auth backend requires the user model to have an email
- and password field. New Oscar projects are encouraged to use the provided
- abstract user model as the base for their users.
-
- Further reading:
-
- * :doc:`How to use a custom user model </howto/use_a_custom_user_model>`.
-
- .. _`custom user models`: https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model
- .. _`documentation on user models`: https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model
-
- Accounts
- ~~~~~~~~
-
- The views and templates of the accounts section have been reworked to be clearer
- and easier to extend.
-
- Better bankcard handling
- ~~~~~~~~~~~~~~~~~~~~~~~~
-
- The bankcard model in the payment app has been greatly improved.
-
- Order processing changes
- ~~~~~~~~~~~~~~~~~~~~~~~~
-
- There are changes to order processing methods
-
- Upgrading
- =========
-
- Templatetags:
-
- * The ``basket_form`` templatetag has been altered to take the ``request`` as the
- first argument, not ``request.basket``.
-
- Templates:
-
- * The template ``customer/email/email.html`` has been renamed to
- ``customer/email/email_detail.html``.
-
- * The template ``customer/orders/order.html`` has been renamed to
- ``customer/orders/order_detail.html``.
-
- Payment app:
-
- * The `balance` method on the source object is not a property not a method.
|