0
0
mirror of https://github.com/wagtail/wagtail.git synced 2024-11-29 17:36:49 +01:00
wagtail/docs/releases/0.9.rst

47 lines
2.0 KiB
ReStructuredText
Raw Normal View History

2014-11-12 16:03:31 +01:00
==========================================
Wagtail 0.9 release notes - IN DEVELOPMENT
==========================================
.. contents::
:local:
:depth: 1
What's new
==========
Minor features
~~~~~~~~~~~~~~
* Javascript includes in the admin backend have been moved to the HTML header, to accommodate form widgets that render inline scripts that depend on libraries such as jQuery
2014-12-01 10:44:05 +01:00
* Improvements to the layout of the admin menu footer.
2014-12-01 11:23:24 +01:00
* Added thousands separator for counters on dashboard
2014-12-02 10:22:52 +01:00
* Added contextual links to admin notification messages
2014-12-02 15:54:21 +01:00
* When copying pages, it is now possible to specify a place to copy to
2015-01-14 23:06:38 +01:00
* ``FieldPanel`` now accepts an optional ``widget`` parameter to override the field's default form widget
* Dropped Django 1.6 support
* Dropped Python 2.6 and 3.2 support
* Dropped Elasticsearch 0.90.x support
* Search view accepts "page" GET parameter in line with pagination.
2014-12-01 10:44:05 +01:00
2014-11-12 16:03:31 +01:00
Bug fixes
~~~~~~~~~
Upgrade considerations
======================
Support for older Django/Python/Elasticsearch versions dropped
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This release drops support for Django 1.6, Python 2.6/3.2 and Elasticsearch 0.90.x. Please make sure these are updated before upgrading.
If you are upgrading from Elasticsearch 0.90.x, you may also need to update the ``elasticsearch`` pip package to a version greater than ``1.0`` as well.
Javascript includes in admin backend have been moved
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To improve compatibility with third-party form widgets, pages within the Wagtail admin backend now output their Javascript includes in the HTML header, rather than at the end of the page. If your project extends the admin backend (through the ``register_admin_menu_item`` hook, for example) you will need to ensure that all associated Javascript code runs correctly from the new location. In particular, any code that accesses HTML elements will need to be contained in an 'onload' handler (e.g. jQuery's ``$(document).ready()``).