From 66b1b7db5aa940829c206f78aaac0e1e0d9d636f Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Wed, 12 Nov 2014 16:03:30 +0000 Subject: [PATCH] Release notes for #802 --- CHANGELOG.txt | 1 + docs/releases/0.8.2.rst | 10 ++++++++++ 2 files changed, 11 insertions(+) diff --git a/CHANGELOG.txt b/CHANGELOG.txt index 87ea725c26..6074c8fd48 100644 --- a/CHANGELOG.txt +++ b/CHANGELOG.txt @@ -8,6 +8,7 @@ Changelog * Fix: Page system check for on_delete actions of ForeignKeys was throwing false positives when page class decends from an abstract class (Alejandro Giacometti) * Fixed a regression where form builder submissions containing a number field would fail with a JSON serialisation error * Fix: Resizing an image with a focal point equal to the image size would result in a divide-by-zero error + * Fix: 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 0.8.1 (05.11.2014) diff --git a/docs/releases/0.8.2.rst b/docs/releases/0.8.2.rst index 7d043e5416..41f980ed5a 100644 --- a/docs/releases/0.8.2.rst +++ b/docs/releases/0.8.2.rst @@ -18,3 +18,13 @@ Bug fixes * Page system check for on_delete actions of ForeignKeys was throwing false positives when page class decends from an abstract class (Alejandro Giacometti) * 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.)