Page.context_object_name can be used to define a more meaningful name
for the page variable in the template.
If defined, the default `page` and `self` are still available for use in
shared templates.
Resolves #5213
* Rewrite AbstractEmailForm render to use cleaned_data
* Add date time formatting to AbstractEmailForm's render method according to Django settings SHORT_DATE_FORMAT and
SHORT_DATETIME_FORMAT
* Previously it was iterating over `form` which left no place to remove
data from the submission without removing the field from the form (which
is inadvisable, as discussed on #4313)
* Preserve order of fields in form emails using cleaned data
* Add a test for consistent date rendering in email forms
* update form customisation examples and add note about date / time formatting in email form usage (docs)
* resolves #3733
* resolves #4313
* adds users view to group view (users filtered by that group)
* adds the ability to go to the users list for the group currently being edited (via header link)
* fix issue where the link to add a new user (when no users found) was broken
* resolves #5801
* Improve Dockerfile in project template
This reorganises Dockerfile to make it adhere to more common-sense rules,
while not being too opinionated on the deployment process.
* Add dockerignore file
* Make Dockerfile comments nicer
* Delete dockerignore created in a wrong path
* Add the right dockerignore files
* Use slim buster Docker image
* Add sqlite3 files to dockerignore
* Fix Docker image name
Ref: https://github.com/wagtail/wagtail/issues/5670#issuecomment-615836390
Add an `is_previewable` method to Page (which accounts for being called either on the base Page model or the specific subclass, as either may be in use on listing pages that display these buttons), and check this when rendering buttons.
Additionally, fix the 'pages for moderation' panel to check that revision.user is defined before trying to output a username - this field is intentionally nullable to allow for scripted processes. Without this check, under normal template-rendering rules the whole panel is liable to be silently dropped.
Ref #5528; fixes #5352. As of Chrome 81, autocomplete="off" seems to be a better bet for preventing unwanted autocompletion dropdowns, rather than autocomplete="some-unrecognised-string".
- Fixes #5358
- Make classes on the nav submenu adhere to BEM a little better
- Make nav submenu footer match the styles of the things around it a little better (other submenu items on mobile, and the other menu footer on larger screens)
If validation rules prevent the multiple image upload view from
creating Image objects from just the image file, an UploadedImage object is
created instead, and turned into an image once the form is filled in.
* Fixes #847
* Add UploadedImage model and related views
* Update custom image model docs
According to the ARIA spec:
> A region that contains mostly site-oriented content, rather than page-specific content.
> Site-oriented content typically includes things such as the logo or identity of the site sponsor, and a site-specific search tool. A banner usually appears at the top of the page and typically spans the full width.
Where the `banner` role was applied was more page-specific than
site-specific. In addition, tags with `banner` roles should not live
under another landmark. To rectify, removed the misused banner roles.
Remove inappropriate contentinfo landmarks
According to ARIA spec 1.1
> A large perceivable region that contains information about the parent document.
> Examples of information included in this region of the page are copyrights and links to privacy statements.
They don't apply to the action buttons on where this was applied to.
Add main landmark to 404 page
