On SQLite, not all moderators would receive a notification.
On Postgres, a “more than one row returned by a subquery used as an
expression” error was thrown.
This will hopefully avoid the persistent issues with this query having to
be rewritten for different DB engines and versions (#827, #1692, #2105...)
Fixes#2105
I think the words "Wagtail site" implies that Wagtail sites are a thing when they are in fact just Django projects with Wagtail installed.
So I think "Using Wagtail" is less likely to cause confusion.
Defining ForeignKeys/OneToOneFields without an on_delete action is deprecated in Django 1.9.
This commit adds on_delete=CASCADE to every ForeignKey that doesn't yet have an on_delete action.
The .start() method now returns an ElasticSearchIndex object that you should perform CRUD operations against instead
This commit removes a nice test that will be reintroduced later
This class represents an individual index in Elasticsearch.
This commit also refactors duplicated implementations of the CRUD methods for updating documents and mappings in the database. These now all live in the new index class.
tagit was initialized from both the AdminTagWidget, and from the `done`
method in the image uploader. Initializing it twice led to strange
errors and ultimately the tags not being saved on the image model.
As the tag widget now contains its own initialisation <script>, tag
inputs do not need to be specially handled by AJAX code any more, so
this can simply be removed.
Fixes#2142
Page EditHandlers must return a subclass of WagtailAdminPageForm to work
correctly. A check has been added to ensure this is the case, raising an
error on startup otherwise.
EditHandlers that can produce forms can now specify which base form
class to use. This defaults to WagtailAdminModelForm, which was the hard
coded base class previously.
Only TabbedInterface and ObjectList EditHandlers now support generating
a form. Other EditHandlers generating forms was not used anywhere except
in the tests.