add inlines into fieldsets

[tangc]

'ModelAdmin has fieldsets and inlines. e.g.
Ref: ​http://docs.djangoproject.com/en/dev/intro/tutorial02/,

fieldsets = [
        (None,               {'fields': ['question']}),
        ('Date information', {'fields': ['pub_date']}),
    ]

inlines = [ChoiceInline]

If can put the inlines into the fieldsets, it would be great. such as:

fieldsets = [
        (None,               {'fields': ['question']}),
        ('inlines sample',   {inlines : [ChoiceInline]}),
        ('Date information', {'fields': ['pub_date']}),
        ('inlines sample 2', {inlines : [SomeOtherChoiceInline]}),
    ]

[tangc]

Or such as:

fieldsets = [
        (None,               {'fields': ['question']}),
        ('inlines sample',   {inlines : [ChoiceInline]}),
        ('Date information', {'fields': ['pub_date']}),
        ('inlines sample 2', {inlines : [SomeOtherChoiceInline]}),
        ('inlines sample 3', {inlines : ['fieldA', 'fieldB', ]}),
    ]

[gmorehoudh]

Bump -- I finally managed to find this bug and find that there is apparently no way to accomplish this. It's surprising. This feature would be quite useful.

[Russell Keith-Magee]

I'm not sure I agree that this would be an improvement. Feel free to open a discussion on django-dev if you disagree.

[Stephen Burrows]

Reopened as per ​discussion on django developers. Since inlines already have a label (in the form of verbose_name) and can control their fields etc., perhaps the following syntax would make more sense:

fieldsets = (
    (None, {'fields': 'field1', 'field2'}),
    SomeInline,
    ("Remaining Fields", {'fields': 'field3', 'field4', 'field5'})
)

[Julien Phalip]

See also #4848, which suggests supporting inlines declaration via ModelAdmin.fields. #16089 might also be of interest, as it discusses adding the ability to dynamically add and remove inlines on a per-request basis.

[stormlifter]

Part of the issue I see is that if you are overriding another app's forms then it would be nice to be able to use an inline and add that into the fieldset so that you don't have to redo everything. For example...

class UserProfileInline(admin.TabularInline):
	model = UserProfile

class UserAdmin(UserAdmin):
	inlines = [UserProfileInline]

The sytax that melinath suggest isn't bad. Another idea would be to call a special method that allows you to insert the Inline at a specified index. So you could say in the example of melinath "fieldsets.inject(1,SomeInline)" which would put the fieldsets from SomeInline into the fieldsets of the parent at that location.

The issue I am getting is that since the fieldsets are unable to include any inline fields that the fields from the inline model are always forced to the bottom, of course I could use JS to move them to the top, but that's just boring. I could also override the form and make it save that added field to the appropriate model, but that's just sloppy.

[gezuru@…]

With the syntax proposition by melinath this ticket has become a duplicate of #4848.

[Aymeric Augustin]

Please don't reopen tickets anonymously without providing an explanation. You may have a good reason for reopening this ticket; if so, say it!

[Simon Charette]

Please don't reopen tickets anonymously without providing an explanation. You may have a good reason for reopening this ticket; if so, say it!