Releases: wagtail/wagtail
Releases · wagtail/wagtail
1.0 beta 2
Changes since Beta 1:
- Added Wagtail API, a module for creating a RESTful API for your content
- Django 1.8 support
- Menu items of custom apps are now highlighted when being used (Josh Barr)
- Serving documents will now use django-sendfile if it's configured (Jordi Joan)
- Documents are now served with correct mime-type (Jordi Joan, Damian Moore)
- Support for If-Modified-Since HTTP header (Jordi Joan)
- Added hook
construct_homepage_summary_items
for customising the site summary panel on the admin homepage - No longer automatically tries to use Celery for sending notification emails
- Added "Add child page" button to admin userbar (Eric Drechsel)
- Renamed the
construct_wagtail_edit_bird
hook toconstruct_wagtail_userbar
- 'static' template tags are now used throughout the admin templates, in place of STATIC_URL
- Added a new decorator-based syntax for RoutablePage, compatible with Django 1.8
- Collapsible blocks stay open on any form error (Salvador Faria)
- Document upload modal no longer switches tabs on form errors (Salvador Faria)
- Fix: Formbuilder no longer raises TypeError when submitting unchecked boolean field (Arne Schauf)
- Fix: Image upload form no longer breaks when using i10n thousand separators (@signalkraft)
- Fix: Multiple image uploader now escapes HTML in filenames (Daniel Fabian from the Google Security Team)
- Fix: wagtailfrontendcache no longer tries to purge pages that are not in a site
- Fix: The contents of elements in the rich text editor were not being whitelisted
- Fix: Due to the above issue, embeds/images in a rich text field would sometimes be saved into the database in their editor representation
- Fix: RoutablePage now prevents subpage_urls from being defined as a property, which would cause a memory leak
- Fix: Prevent logout on changing password when SessionAuthenticationMiddleware is in use
- Fix: Work around a Python / Django issue that prevented documents with certain non-ASCII filenames from being served
0.8.7
- Fix: wagtailfrontendcache no longer tries to purge pages that are not in a site
- Fix: The contents of elements in the rich text editor were not being whitelisted
- Fix: Due to the above issue, embeds/images in a rich text field would sometimes be saved into the database in their editor representation
- Fix: RoutablePage now prevents subpage_urls from being defined as a property, which would cause a memory leak
- Fix: Added validation to prevent pages being created with only whitespace characters in their title fields (Frank Wiles)
- Fix: Prevent logout on changing password when SessionAuthenticationMiddleware is in use
- Fix: Work around a Python / Django issue that prevented documents with certain non-ASCII filenames from being served
1.0b1
- Added StreamField, a model field for freeform page content
- MySQL support
- Javascript includes in the admin backend have been moved to the HTML header, to accommodate form widgets that render inline scripts that depend on libraries such as jQuery
- Improvements to the layout of the admin menu footer.
- Added thousands separator for counters on dashboard
- Added contextual links to admin notification messages
- When copying pages, it is now possible to specify a place to copy to (Timo Rieber)
- FieldPanel now accepts an optional 'widget' parameter to override the field's default form widget (Alejandro Giacometti)
- Dropped Django 1.6 support
- Dropped Python 2.6 and 3.2 support
- Dropped Elasticsearch 0.90.x support
- Search view accepts "page" GET parameter in line with pagination
- Reversing
django.contrib.auth.admin.login
will no longer lead to Wagtails login view (making it easier to have front end views) - Removed dependency on
LOGIN_URL
andLOGIN_REDIRECT_URL
settings - Password reset view names namespaced to wagtailadmin
- Removed the need to add permission check on admin views (now automated)
- Added cache-control headers to all admin views
- Added validation to prevent pages being crated with only whitespace characters in their title fields (Frank Wiles)
- Page model fields without a FieldPanel are no longer displayed in the form
- No longer need to specify the base model on InlinePanel definitions
- The project template Vagrantfile now listens on port 8000
- The external link chooser in rich text areas now accepts URLs of the form '/some/local/path', to allow linking to non-Wagtail-controlled URLs within the local site (Eric Drechsel)
- SCSS files in wagtailadmin now use absolute imports, to permit overriding by user stylesheets (Martin Sanders)
- Bare text entered in rich text areas is now automatically wrapped in a paragraph element
- Added pagination to the snippets listing and chooser (Martin Sanders)
- Page / document / image / snippet choosers now include a link to edit the chosen item
- The
document_served
signal now correctly passes the Document class assender
and the document asinstance
- Image/Document edit page no longer throws OSError when the original image is missing
- Page classes can specify an edit_handler property to override the default Content / Promote / Settings tabbed interface
- The Page model now records the date/time that a page was first published, as the field
first_published_at
- Increased the maximum length of a page slug from 50 to 255 characters
- Plain text fields in the page editor now use auto-expanding text areas
- Date / time pickers now consistently use times without seconds, to prevent Javascript behaviour glitches when focusing / unfocusing fields
- Added hooks
register_rich_text_embed_handler
andregister_rich_text_link_handler
for customising link / embed handling within rich text fields
0.8.6
- Translations updated, including new translations for Czech, Italian and Japanese
- The "fixtree" command can now delete orphaned pages
- Fix: django-taggit library updated to 0.12.3, to fix a bug with migrations on SQLite on Django 1.7.2 and above (jazzband/django-taggit#285)
- Fix: Fixed a bug that caused children of a deleted page to not be deleted if they had a different type
0.8.5
- Fix: On adding a new page, the available page types are ordered by the displayed verbose name
- Fix: Active admin submenus were not properly closed when activating another
- Fix: get_sitemap_urls is now called on the specific page class so it can now be overridden (Jerel Unruh)
- Fix: (Firefox and IE) Fixed preview window hanging and not refocusing when "Preview" button is clicked again
- Fix: Storage backends that return raw ContentFile objects are now handled correctly when resizing images (@georgewhewell)
- Fix: Punctuation characters are no longer stripped when performing search queries
- Fix: When adding tags where there were none before, it is now possible to save a single tag with multiple words in it
- Fix: richtext template tag no longer raises TypeError if None is passed into it (Alejandro Varas)
- Fix: Serving documents now uses a streaming HTTP response and will no longer break Django's cache middleware
- Fix: User admin area no longer fails in the presence of negative user IDs (as used by django-guardian's default settings)
- Fix: Password reset emails now use the
BASE_URL
setting for the reset URL - Fix: BASE_URL is now included in the project template's default settings file
0.8.4
- Fix: It is no longer possible to have the explorer and settings menu open at the same time
- Fix: Page IDs in page revisions were not updated on page copy, causing subsequent edits to be committed to the original page instead
- Fix: Copying a page now creates a new page revision, ensuring that changes to the title/slug are correctly reflected in the editor (and also ensuring that the user performing the copy is logged)
- Fix: Prevent a race condition when creating Filter objects
v0.8.3
v0.8.2
- Added missing jQuery UI sprite files, causing collectstatic to throw errors (most reported on Heroku)
- Page system check for on_delete actions of ForeignKeys was throwing false positives when page class decends from an abstract class (Alejandro Giacometti)
- Page system check for on_delete actions of ForeignKeys now only raises warnings, not errors
- Fixed a regression where form builder submissions containing a number field would fail with a JSON serialisation error
- Resizing an image with a focal point equal to the image size would result in a divide-by-zero error
- Focal point indicator would sometimes be positioned incorrectly for small or thin images
- Fix: Focal point chooser background colour changed to grey to make working with transparent images easier
- 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
- Fixed a TypeError when previewing pages that use RoutablePageMixin
- Rendering image with missing file in rich text no longer crashes the entire page
- IOErrors thrown by underlying image libraries that are not reporting a missing image file are no longer caught
- Fix: Minimum Pillow version bumped to 2.6.1 to work around a crash when using images with transparency
- Fix: Images with transparency are now handled better when being used in feature detection
0.8.1
0.8
- Added logging for page operations
- The save button on the page edit page now redirects the user back to the edit page instead of the explorer
- Signal handlers for
wagtail.wagtailsearch
andwagtail.contrib.wagtailfrontendcache
are now automatically registered when using Django 1.7 or above. (Tim Heap) - Added a Django 1.7 system check to ensure that foreign keys from Page models are set to on_delete=SET_NULL, to prevent inadvertent (and tree-breaking) page deletions
- Improved error reporting on image upload, including ability to set a maximum file size via a new setting WAGTAILIMAGES_MAX_UPLOAD_SIZE
- The external image URL generator now keeps persistent image renditions, rather than regenerating them on each request, so it no longer requires a front-end cache
- Added Dutch translation
- Fix: Replaced references of .username with .get_username() on users for better custom user model support (John-Scott Atlakson)
- Fix: Unpinned dependency versions for six and requests to help prevent dependency conflicts
- Fix: Fixed TypeError when getting embed HTML with oembed on Python 3 (John-Scott Atlakson)
- Fix: Made HTML whitelisting in rich text fields more robust at catching disallowed URL schemes such as "jav\tascript:" (Tim Heap)
- Fix: created_at timestamps on page revisions were not being preserved on page copy, causing revisions to get out of sequence
- Fix: When copying pages recursively, revisions of sub-pages were being copied regardless of the copy_revisions flag
- Fix: Updated the migration dependencies within the project template to ensure that Wagtail's own migrations consistently apply first.
- Fix: The cache of site root paths is now cleared when a site is deleted.
- Fix: Search indexing now prevents pages from being indexed multiple times, as both the base Page model and the specific subclass
- Fix: Search indexing now avoids trying to index abstract models
- Fix: Fixed references to "username" in login form help text for better custom user model support (John-Scott Atlakson)
- Fix: Later items in a model's search_field list now consistently override earlier items, allowing subclasses to redefine rules from the parent
- Fix: Image uploader now accepts JPEG images that PIL reports as being in MPO format
- Fix: Multiple checkbox fields on form-builder forms did not correctly save multiple values
- Fix: Editing a page's slug and saving it without publishing could sometimes cause the URL paths of child pages to be corrupted
- Fix: 'latest_revision_created_at' was being cleared on page publish, causing the page to drop to the bottom of explorer listings
- Fix: Searches on partial_match fields were wrongly applying prefix analysis to the search query as well as the document (causing e.g. a query for "water" to match against "wagtail")