mirror of
https://github.com/Hopiu/wagtail.git
synced 2026-05-25 07:13:46 +00:00
edc236cb06
Making developers opt out of extra security is better than making them opt in, especially when they may not be aware of the security they are missing out on.
93 lines
3.1 KiB
ReStructuredText
93 lines
3.1 KiB
ReStructuredText
==========================================
|
|
Wagtail 1.5 release notes - IN DEVELOPMENT
|
|
==========================================
|
|
|
|
.. contents::
|
|
:local:
|
|
:depth: 1
|
|
|
|
|
|
What's new
|
|
==========
|
|
|
|
Minor features
|
|
~~~~~~~~~~~~~~
|
|
|
|
* Moved lesser-user actions in the page explorer into a 'More' dropdown
|
|
* Added a hook :ref:`register_page_listing_buttons` for adding action buttons to the page explorer
|
|
* Added a hook :ref:`insert_global_admin_js` for inserting custom JavaScript throughout the admin backend (Tom Dyson)
|
|
* The type of the ``search_fields`` attribute on ``Page`` models (and other searchable models) has changed from a tuple to a list (see upgrade consideration below) (Tim Heap)
|
|
* Use `PasswordChangeForm` when user changes their password, requiring the user to enter their current password (Matthijs Melissen)
|
|
* Highlight current day in date picker (Jonas Lergell)
|
|
|
|
Bug fixes
|
|
~~~~~~~~~
|
|
|
|
* The currently selected day is now highlighted only in the correct month in date pickers (Jonas Lergell)
|
|
|
|
|
|
Upgrade considerations
|
|
======================
|
|
|
|
The ``search_fields`` attribute on models should now be set to a list
|
|
=====================================================================
|
|
|
|
On searchable models (eg, ``Page`` or custom ``Image`` models) the ``search_fields`` attribute should now be a list instead of a tuple.
|
|
|
|
For example, the following ``Page`` model:
|
|
|
|
.. code-block:: python
|
|
|
|
class MyPage(Page):
|
|
...
|
|
|
|
search_fields = Page.search_fields + (
|
|
indexed.SearchField('body'),
|
|
)
|
|
|
|
Should be changed to:
|
|
|
|
.. code-block:: python
|
|
|
|
class MyPage(Page):
|
|
...
|
|
|
|
search_fields = Page.search_fields + [
|
|
indexed.SearchField('body'),
|
|
]
|
|
|
|
To ease the burden on third-party modules, adding tuples to ``Page.search_fields`` will still work. But this backwards-compatibility fix will be removed in Wagtail 1.7.
|
|
|
|
Elasticsearch backend now defaults to verifying SSL certs
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Previously, if you used the Elasticsearch backend, configured with the URLS property like:
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
WAGTAILSEARCH_BACKENDS = {
|
|
'default': {
|
|
'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
|
|
'URLS': ['https://example.com/'],
|
|
}
|
|
}
|
|
|
|
Elasticsearch would not be configured to verify SSL certificates for HTTPS URLs. This has been changed so that SSL certificates are verified for HTTPS connections by default.
|
|
|
|
If you need the old behaviour back, where SSL certificates are not verified for your HTTPS connection, you can configure the Elasticsearch backend with the ``HOSTS`` option, like so:
|
|
|
|
.. code-block:: python
|
|
|
|
WAGTAILSEARCH_BACKENDS = {
|
|
'default': {
|
|
'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
|
|
'HOSTS': [{
|
|
'host': 'example.com'
|
|
'use_ssl': True,
|
|
'verify_certs': False,
|
|
}],
|
|
}
|
|
}
|
|
|
|
See the `Elasticsearch-py documentation <http://elasticsearch-py.readthedocs.org/en/stable/#ssl-and-authentication>`_ for more configuration options.
|