Either of block_errors or non_block_errors can be omitted; non_block_errors can be passed as a plain list rather than an ErrorList; and the values in block_errors can be ValidationError instances or singleton lists, not just singleton ErrorLists.
Refactor it to allow either of block_errors or non_block_errors to be omitted; allow non_block_errors to be passed as a plain list rather than an ErrorList; and allow the items of block_errors to be ValidationError instances or singleton lists rather than just singleton ErrorLists.
This allows us to use the function in modules that are imported by wagtailadmin_tags (either directly or indirectly) without triggering a circular import.
- The status tag styles did not actually change when the permissions changed
- Instead of trying to treat the status tag as a button, use an actual button styling as this pattern is not used anywhere else in Wagtail
- Fixes #10128
* Adding missing return statement to FormPage.process_form_submission in the "Custom form submission model" example to make it available to FormPage.render_landing_page, among other methods.
All setError methods now accept an instance of the error dict returned by get_error_json_data. Since this is consistent across all ValidationError subclasses, there is no longer any need for the exception type to match the block type (unless you care about propagating child block errors).
Fixes #5663
The audit log report currently raises an unhandled exception if it
tries to display log entries for model instances where the model was
deleted after the log entry was made. This commit fixes that bug.
If the model was deleted via a migration but the content type still
exists in the database (a "stale content type" in Django parlance),
the report will now display a capitalized version of the content type's
"name" field, for example "Homepage" for the HomePage model.
If the content type has also been deleted (likely via Django's
remove_stale_contenttypes management command), the report will now
display the phrase "Unknown content type".
Fixes issue 8699.
* Style guide updated tests added
* Added story for status tag and put pageurl tag in use for page_status_tag
* Allow for url/non-url variant & attrs to be passed through to root element
* Closes #8656
- Permissions/commenting links no longer exist in the documentation and have moved to the user guide
- As these are quite old releases now, remove the references to avoid build errors in docs
Since Wagtail 4.1 the Settings Tab and the corresponding scheduling of pages has been moved to the Status side panels. As mentioned in the release notes of Wagtail 4.1: [See here](https://docs.wagtail.org/en/stable/releases/4.1.html#new-ui-for-scheduled-publishing).
In the documentation section for customising the edit interface, this snippet is still available. When implemented, there is no effect and no error is shown.
Therefore this line is obsolete and only the two tabs 'Content' and 'Promote' should be available.
Co-authored-by: Julian Bigler <disperate@users.noreply.github.com>
