kopia lustrzana https://github.com/wagtail/wagtail
3.1 KiB
3.1 KiB
Wagtail 6.4 release notes - IN DEVELOPMENT
Unreleased
---
local:
depth: 1
---
What's new
Other features
- Add the ability to apply basic Page QuerySet optimizations to
specific()
sub-queries usingselect_related
&prefetch_related
, see (Andy Babic) - Increase
DATA_UPLOAD_MAX_NUMBER_FIELDS
in project template (Matt Westcott)
Bug fixes
- Improve handling of translations for bulk page action confirmation messages (Matt Westcott)
- Ensure custom rich text feature icons are correctly handled when provided as a list of SVG paths (Temidayo Azeez, Joel William, LB (Ben) Johnston)
- Ensure manual edits to
StreamField
values do not throw an error (Stefan Hammer)
Documentation
- Move the model reference page from reference/pages to the references section as it covers all Wagtail core models (Srishti Jaiswal)
- Move the panels reference page from references/pages to the references section as panels are available for any model editing, merge panels API into this page (Srishti Jaiswal)
- Move the tags documentation to standalone advanced topic for tagging, instead of being inside the reference/pages section (Srishti Jaiswal)
- Refine the page so that common (page/non-page) class references are at the top and the full page only example has correct heading nesting (Alessandro Chitarrini)
- Add the
wagtail start
command to the management commands reference page (Damilola Oladele) - Refine the page sections and document common issues encountered when creating custom templates (Damilola Oladele)
- Refine titles, references and URLS to better align with the documentation style guide, including US spelling (Srishti Jaiswal)
- Recommend a larger
DATA_UPLOAD_MAX_NUMBER_FIELDS
when integrating Wagtail into Django (Matt Westcott) - Improve code highlighting and formatting for Python docstrings in core models (Srishti Jaiswal)
- Re-enable building offline formats in online documentation (Read the docs) for EPUB/PDF/HTML downloads (Joel William)
Maintenance
- Close open files when reading within utils/setup.py (Ataf Fazledin Ahamed)
- Avoid redundant
ALLOWED_HOSTS
check inSite.find_for_request
(Jake Howard)
Upgrade considerations - changes affecting all projects
DATA_UPLOAD_MAX_NUMBER_FIELDS
update
It's recommended that all projects set the DATA_UPLOAD_MAX_NUMBER_FIELDS
setting to 10000 or higher.
This specifies the maximum number of fields allowed in a form submission, and it is recommended to increase this from Django's default of 1000, as particularly complex page models can exceed this limit within Wagtail's page editor:
# settings.py
DATA_UPLOAD_MAX_NUMBER_FIELDS = 10_000