- Removed capfirst() when initializing the label from the related
model's verbose name, so it can be used for both the add-button and
the child panel's header. Further used capfirst in the template when
rendering the child panel's header and removed lower filter from the
add-button's label.
- Tests:
- changed labels and verbose names related to the InlinePanel to
the correct singular and lowercased form
- removed unnecessary heading kwargs, where the default heading
already equals that definition
- Docs: Removed unnecessary and verbose label and header definitions
from the documentation
Fixes#13221
This change alters the behavior of the sidebar "Snippets" menu such that
the snippet index view doesn't include snippet models that have been
configured with their own menu item.
Currently, the "Snippets" menu doesn't appear if all snippet models have
their own menu items; however, if some models do and some don't, the
snippets index view lists all of them, causing some duplication in the
UI which could be confusing for editors.
This commit changes this behavior so that "Snippets" is only used to
edit those snippet models that aren't editable elsewhere.
A new setting (WAGTAILSNIPPETS_MENU_SHOW_ALL) has been added to always
show the snippets menu and all snippets models. This setting will allow
for continuation of the current behavior for those users that desire it.
Closes issue 11340.
- Fix a few small typos & formatting issues
- Ensure the form builder changes are better documented
- Add links to other docs pages where possible
- Improve consistency with usage of `code` backticks on modules
- Add docs reference for StreamField `get_template` docs
Had to remove the <details> element for the section linking example in
the "Reference links" section.
This is because Sphinx/MyST renders a <section> element for each heading
and closes it when the next heading starts. If we create a heading
inside a <details> element, the <section> element will not be closed
until the next heading starts, which generates invalid HTML.
- Move model reference to directly under the references section, not the reference/pages section
- Move panel reference to directly under the references section, not the reference/pages section
- Merge panel API with panels reference pages
- Fix confusing heading levels in the page model recipes page
- Fix title in model reference to align with docs style guide
- Adopt US spelling for customize (panels) reference key
This text existed since Wagtail 1.x and is referring to the original database backend that just did substring matches (which is now the fallback backend), before we supported database-backed full-text search.
Chiemezuo