-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird behavior with max_num
and nested inlines
#230
Comments
Oh, I see the bug here. I'll try to get a fix out this week, though it may not happen until next week. Thanks for the report! |
fdintino
added a commit
that referenced
this issue
Nov 12, 2022
fdintino
added a commit
that referenced
this issue
Nov 12, 2022
fdintino
added a commit
that referenced
this issue
Nov 12, 2022
fdintino
added a commit
that referenced
this issue
Nov 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using
django-nested-admin
in order to recursively create relations with the same model (like a parent/child relationship).So I have three levels of nested inlines:
Level1
,Level2
andLevel3
Level2
andLevel3
have is not limited with themax_num
option butLevel1
is limited with 2 as itsmax_num
's value.It means that I can have as many
Level3
nested in aLevel2
andLevel2
in aLevel1
as I want.But when I reach the maximum number of
Level1
, all the links to add a nested objects are hidden, included the one permitting to addLevel2
orLevel3
objects. Thus even if I can add a second Level1, I can add nested objects in itself or even in other Level objects that were already existing.Image 1 is before reaching the maximum number
Image 2 is when the maximum number is reached
I am using:
Could you help me on that please ?
Did I miss something or is it an issue ?
The text was updated successfully, but these errors were encountered: