0.8.3.rst 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. ===========================
  2. Wagtail 0.8.3 release notes
  3. ===========================
  4. .. contents::
  5. :local:
  6. :depth: 1
  7. What's new
  8. ==========
  9. Bug fixes
  10. ~~~~~~~~~
  11. * Added missing jQuery UI sprite files, causing collectstatic to throw errors (most reported on Heroku)
  12. * Page system check for on_delete actions of ForeignKeys was throwing false positives when page class descends from an abstract class (Alejandro Giacometti)
  13. * Page system check for on_delete actions of ForeignKeys now only raises warnings, not errors
  14. * Fixed a regression where form builder submissions containing a number field would fail with a JSON serialisation error
  15. * Resizing an image with a focal point equal to the image size would result in a divide-by-zero error
  16. * Focal point indicator would sometimes be positioned incorrectly for small or thin images
  17. * Fix: Focal point chooser background colour changed to grey to make working with transparent images easier
  18. * 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
  19. * Fixed a TypeError when previewing pages that use RoutablePageMixin
  20. * Rendering image with missing file in rich text no longer crashes the entire page
  21. * IOErrors thrown by underlying image libraries that are not reporting a missing image file are no longer caught
  22. * Fix: Minimum Pillow version bumped to 2.6.1 to work around a crash when using images with transparency
  23. * Fix: Images with transparency are now handled better when being used in feature detection
  24. Upgrade considerations
  25. ======================
  26. Port number must be specified when running Elasticsearch on port 9200
  27. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  28. 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.)