You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

v0.6.rst 4.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164
  1. =======================
  2. Oscar 0.6 release notes
  3. =======================
  4. Welcome to Oscar 0.6!
  5. These release notes cover the `new features`_ as well as `upgrading advice`_.
  6. .. _`new features`: `What's new in Oscar 0.6?`_
  7. .. _`upgrading advice`: `Upgrading`_
  8. Overview
  9. ========
  10. ...
  11. What's new in Oscar 0.6?
  12. ========================
  13. The payment models have been split into abstract- and concrete versions. This
  14. brings them inline with other Oscar apps and allows them to be customised.
  15. Search
  16. ~~~~~~
  17. Multi-partner dashboard
  18. ~~~~~~~~~~~~~~~~~~~~~~~
  19. Demo site
  20. ~~~~~~~~~
  21. Oscar now ships with a demo site along side the sandbox site. While the sandbox
  22. is a minimal Django project that uses Oscar with all its defaults, the demo site
  23. is a more realistic example of an Oscar project. It has a custom skin and makes
  24. many alterations to the default Oscar behaviour.
  25. It's features include:
  26. * A range of different product types: books, downloads, clothing
  27. * PayPal Express integration using django-oscar-paypal_
  28. * Datacash integration using django-oscar-datacash_
  29. .. _django-oscar-paypal: https://github.com/tangentlabs/django-oscar-paypal
  30. .. _django-oscar-datacash: https://github.com/tangentlabs/django-oscar-datacash
  31. Further reading:
  32. * :doc:`The demo site </internals/sandbox>`.
  33. Django 1.5 and custom user model support
  34. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  35. Oscar now supports `custom user models`_, the headline new feature in Django 1.5. These can be used standalone
  36. or with a one-to-one profile model: Oscar's account forms inspect the model
  37. fields to dynamically pick up the fields for editing and display.
  38. There are some restrictions on what fields a custom user model must have. For
  39. instance, Oscar's default auth backend requires the user model to have an email
  40. and password field. New Oscar projects are encouraged to use the provided
  41. abstract user model as the base for their users.
  42. Further reading:
  43. * :doc:`How to use a custom user model </howto/use_a_custom_user_model>`.
  44. .. _`custom user models`: https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model
  45. .. _`documentation on user models`: https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model
  46. Accounts
  47. ~~~~~~~~
  48. The views and templates of the accounts section have been reworked to be clearer
  49. and easier to extend.
  50. Better bankcard handling
  51. ~~~~~~~~~~~~~~~~~~~~~~~~
  52. The bankcard model in the payment app has been greatly improved.
  53. Order processing changes
  54. ~~~~~~~~~~~~~~~~~~~~~~~~
  55. There are changes to order processing methods
  56. Minor changes
  57. ~~~~~~~~~~~~~
  58. * detox_ is a new dependency, which allows running `tox` tests in parallel.
  59. .. _detox: https://pypi.python.org/pypi/detox
  60. Upgrading
  61. =========
  62. Templatetags:
  63. * The ``basket_form`` templatetag has been altered to take the ``request`` as the
  64. first argument, not ``request.basket``.
  65. Templates:
  66. * The template ``customer/email/email.html`` has been renamed to
  67. ``customer/email/email_detail.html``.
  68. * The template ``customer/orders/order.html`` has been renamed to
  69. ``customer/orders/order_detail.html``.
  70. * The template ``dashboard/orders/order_detail.html`` has been reorganised. The
  71. ``tab_transactions`` block has been renamed to ``payment_transactions``.
  72. * Alternative product class templates now use ``slug` field instead of
  73. ``name.lower()`` to determine their filename. If you have templates for
  74. specific product classes, please update your filenames accordingly
  75. Address app:
  76. * The ``UserAddress.salutation`` and ``UserAddress.name`` methods are now
  77. properties.
  78. * ``Country`` model's `is_highlighted` column is now integer field to allow
  79. fine-grained country selection. 0 = no highlighting
  80. Checkout app:
  81. * Checkout has a new option "Register and continue". Option value `new` in
  82. `GatewayForm` has changed to `guest` as `new` option is used for this feature.
  83. * Payment details - create_billing_address accepts kwargs so data can be passed
  84. to it from the final page of checkout.
  85. Payment app:
  86. * The `balance` method on the source object is not a property not a method.
  87. URLs
  88. ~~~~
  89. The named search URL ``search_default`` is renamed to ``search-default`` for
  90. consistency with the rest of Oscar.
  91. Migrations
  92. ~~~~~~~~~~
  93. There are new migrations in the following apps to be aware of.
  94. * Catalogue:
  95. - ``0011``: Higher ``max_length`` on FileFields and ImageFields
  96. * Promotions:
  97. - ``0003``: Higher ``max_length`` on FileFields and ImageFields
  98. * Address:
  99. - ``0003``: ``Country``'s ``is_highlighted`` is now an integer to allow
  100. finer control.
  101. * Order app:
  102. - The `date` field of the ``order.AbstractCommunicationEvent``, ``order.AbstractPaymentEvent`` and
  103. ``order.AbstractShippingEvent`` models have been renamed to ``date_created`` for
  104. consistency with the rest of Oscar.