Opened 17 years ago
Closed 17 years ago
#3394 closed (fixed)
min_num_in_admin is ignored for new parent objects
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | contrib.admin | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The documentation for min_num_in_admin states "However, no fewer than min_num_in_admin related objects will ever be displayed." This isn't true, though - when a new parent object is first created, there are always num_in_admin inline children even if this is fewer than the minimum. Attached (trivial) patch fixes this :)
Attachments (1)
Change History (3)
by , 17 years ago
| Attachment: | min_num_in_admin.diff added |
|---|
comment:1 by , 17 years ago
| Component: | Database wrapper → Admin interface |
|---|---|
| Triage Stage: | Unreviewed → Ready for checkin |
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [4500]) Fixed #3394 -- Made min_num_in_admin be respected on new object creation. Patch
from torne-django@….