mirror of
https://github.com/Hopiu/wagtail.git
synced 2026-05-20 04:51:55 +00:00
31 lines
1.7 KiB
ReStructuredText
31 lines
1.7 KiB
ReStructuredText
============================================
|
|
Wagtail 0.8.2 release notes - IN DEVELOPMENT
|
|
============================================
|
|
|
|
.. contents::
|
|
:local:
|
|
:depth: 1
|
|
|
|
|
|
What's new
|
|
==========
|
|
|
|
|
|
Bug fixes
|
|
~~~~~~~~~
|
|
|
|
* Added missing jQuery UI sprite files, causing collectstatic to throw errors (most reported on Heroku)
|
|
* Page system check for on_delete actions of ForeignKeys was throwing false positives when page class decends from an abstract class (Alejandro Giacometti)
|
|
* Page system check for on_delete actions of ForeignKeys now only raises warnings, not errors
|
|
* Fixed a regression where form builder submissions containing a number field would fail with a JSON serialisation error
|
|
* Resizing an image with a focal point equal to the image size would result in a divide-by-zero error
|
|
* Elasticsearch configuration now supports specifying HTTP authentication parameters as part of the URL, and defaults to ports 80 (HTTP) and 443 (HTTPS) if port number not specified
|
|
|
|
|
|
Upgrade considerations
|
|
======================
|
|
|
|
Port number must be specified when running Elasticsearch on port 9200
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
In previous versions, an Elasticsearch connection URL in ``WAGTAILSEARCH_BACKENDS`` without an explicit port number (e.g. ``http://localhost/``) would be treated as port 9200 (the Elasticsearch default) whereas the correct behaviour would be to use the default http/https port of 80/443. This behaviour has now been fixed, so sites running Elasticsearch on port 9200 must now specify this explicitly - e.g. ``http://localhost:9200``. (Projects using the default settings, or the settings given in the Wagtail documentation, are unaffected.)
|