主要版本说明¶
- Upgrading Wagtail
- Wagtail 2.11 release notes - IN DEVELOPMENT
- Wagtail 2.10.2 release notes
- Wagtail 2.10.1 release notes
- Wagtail 2.10 release notes
- What’s new
- Upgrade considerations
- Removed support for Python 3.5
- Move to new configurable moderation system (workflow)
<div class="rich-text">
wrappers removed from rich text- Prepopulating data for site history report
clean_name
field added to form builder form field models- New
next_url
keyword argument onregister_page_listing_buttons
andregister_page_listing_more_buttons
hooks
- Wagtail 2.9.3 release notes
- Wagtail 2.9.2 release notes
- Wagtail 2.9.1 release notes
- Wagtail 2.9 release notes
- Wagtail 2.8.2 release notes
- Wagtail 2.8.1 release notes
- Wagtail 2.8 release notes
- Wagtail 2.7.4 release notes
- Wagtail 2.7.3 release notes
- Wagtail 2.7.2 release notes
- Wagtail 2.7.1 release notes
- Wagtail 2.7 release notes
- Wagtail 2.6.3 release notes
- Wagtail 2.6.2 release notes
- Wagtail 2.6.1 release notes
- Wagtail 2.6 release notes
- Wagtail 2.5.2 release notes
- Wagtail 2.5.1 release notes
- Wagtail 2.5 release notes
- Wagtail 2.4 release notes
- Wagtail 2.3 release notes
- Wagtail 2.2.2 release notes
- Wagtail 2.2.1 release notes
- Wagtail 2.2 release notes
- Wagtail 2.1.3 release notes
- Wagtail 2.1.2 release notes
- Wagtail 2.1.1 release notes
- Wagtail 2.1 release notes
- Wagtail 2.0.2 release notes
- Wagtail 2.0.1 release notes
- Wagtail 2.0 release notes
- What’s new
- Upgrade considerations
- Removed support for Python 2.7, Django 1.8 and Django 1.10
- Added support for Django 2.0
- Wagtail module path updates
- Hallo.js customisations are unavailable on the Draftail rich text editor
- Data format for rich text fields in
assertCanCreate
tests has been updated - Removed support for Elasticsearch 1.x
- Removed version 1 of the Wagtail API
construct_whitelister_element_rules
hook is deprecatedwagtail.images.views.serve.generate_signature
now returns a string- Deprecated search view
- New Hallo editor extension points
- Wagtail 1.13.4 release notes
- Wagtail 1.13.3 release notes
- Wagtail 1.13.2 release notes
- Wagtail 1.13.1 release notes
- Wagtail 1.13 release notes
- Wagtail 1.12.6 release notes
- Wagtail 1.12.5 release notes
- Wagtail 1.12.4 release notes
- Wagtail 1.12.3 release notes
- Wagtail 1.12.2 release notes
- Wagtail 1.12.1 release notes
- Wagtail 1.12 release notes
- What’s new
- Upgrade considerations
- StreamField now defaults to
blank=False
- Old configuration settings for embeds are deprecated
- Registering custom hallo.js plugins directly is deprecated
- Custom
get_admin_display_title
methods should usedraft_title
- Fixtures for loading pages should include
draft_title
RoutablePageMixin
now has a default index route
- StreamField now defaults to
- Wagtail 1.11.1 release notes
- Wagtail 1.11 release notes
- Wagtail 1.10.1 release notes
- Wagtail 1.10 release notes
- What’s new
- Upgrade considerations
- Django 1.9 and Python 3.3 support dropped
- Dropped support for generating static sites using
django-medusa
- Signals on custom
Image
andRendition
models connected automatically - Adding / editing users through Wagtail admin no longer sets
is_staff
flag - Specifying the full file name in documents URL is mandatory
- Wagtail 1.9.1 release notes
- Wagtail 1.9 release notes
- Wagtail 1.8.2 release notes
- Wagtail 1.8.1 release notes
- Wagtail 1.8 release notes
- What’s new
- Upgrade considerations
unique_together
constraint on custom image rendition models needs updatingwagtail.wagtailimages.models.get_image_model
has moved- Non-administrators now need ‘bulk delete’ permission to delete pages with children
- Cloudflare cache module now requires a
ZONEID
setting - Extra options for the Elasticsearch constructor should be now defined with the new key
OPTIONS
of theWAGTAILSEARCH_BACKENDS
setting
- Wagtail 1.7 release notes
- Wagtail 1.6.3 release notes
- Wagtail 1.6.2 release notes
- Wagtail 1.6.1 release notes
- Wagtail 1.6 release notes
- Wagtail 1.5.3 release notes
- Wagtail 1.5.2 release notes
- Wagtail 1.5.1 release notes
- Wagtail 1.5 release notes
- Wagtail 1.4.6 release notes
- Wagtail 1.4.5 release notes
- Wagtail 1.4.4 release notes
- Wagtail 1.4.3 release notes
- Wagtail 1.4.2 release notes
- Wagtail 1.4.1 release notes
- Wagtail 1.4 release notes
- Wagtail 1.3.1 release notes
- Wagtail 1.3 release notes
- Wagtail 1.2 release notes
- What’s new
- Upgrade considerations
PageManager.sibling_of(page)
andPageManager.not_sibling_of(page)
have changed behaviourImage.search
andDocument.search
methods are deprecated- Wagtail API requires adding
rest_framework
to INSTALLED_APPS Page.get_latest_revision_as_page()
now returns live page object when there are no draft changes
- Wagtail 1.1 release notes
- Wagtail 1.0 release notes
- What’s changed
- Upgrade considerations
- Support for older Django/Python/Elasticsearch versions dropped
- Wagtail version upgrade notifications are enabled by default
InlinePanel
definitions no longer need to specify the base model- You no longer need
LOGIN_URL
andLOGIN_REDIRECT_URL
to point to Wagtail admin. RoutablePage
now uses decorator syntax for defining views- Upgrading from the external
wagtailapi
module. - Celery no longer automatically used for sending notification emails
- Login/Password reset views renamed
- JavaScript includes in admin backend have been moved
- EditHandler internal API has changed
- chooser_panel templates are obsolete
document_served
signal arguments have changed- Custom image models must specify an
admin_form_fields
list construct_wagtail_edit_bird
hook has been renamedIMAGE_COMPRESSION_QUALITY
setting has been renamed
- Wagtail 0.8.10 release notes
- Wagtail 0.8.8 release notes
- Wagtail 0.8.7 release notes
- Wagtail 0.8.6 release notes
- Wagtail 0.8.5 release notes
- Wagtail 0.8.4 release notes
- Wagtail 0.8.3 release notes
- Wagtail 0.8.1 release notes
- Wagtail 0.8 release notes
- Wagtail 0.7 release notes
- Wagtail 0.6 release notes
- Wagtail 0.5 release notes
- Wagtail 0.4.1 release notes
- Wagtail 0.4 release notes