InlinePanel message does not take max_num into account
See original GitHub issueIssue Summary
The InlinePanel
default message when using min_num
does not take max_num
into account.
Steps to Reproduce
I’m using this inlinepanel:
InlinePanel(
'featured_pages',
label='Featured',
help_text='Choose two blog pages to feature',
min_num=2,
max_num=2,
)
And after removing the stubbed empty fields on the CMS page, it reports this:
That should probably read Please submit X forms
when min_num
and max_num
are the same value.
Technical details
- Wagtail version: 2.8.2
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Adding an InlineField to a ClusterableModel does not work
I have a Page class called EventDetail which in ...
Read more >Panel types — Wagtail Documentation 4.1.1 documentation
Just define that field the normal Django way and pass the field name into FieldPanel when defining your panels. Wagtail will take care...
Read more >Release 2.6a0 Torchbox - Wagtail Documentation
from wagtail.admin.edit_handlers import FieldPanel, InlinePanel ... StreamFields or rich text fields will not be taken into account.
Read more >Transforming a Course for Online Learning
Uploading to Ensemble (you need a user account first) . ... It doesn't really matter whether you choose to use folders versus using...
Read more >OPERA Cloud - Oracle Help Center
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have raised a ticket on Django ticket tracker for this issue and submitted a PR to resolve it as well
Once it gets accepted/reviewed this issue will be resolved ✨
Update - The PR is merged with Django ✨