blocks|key|513859|text|问题不是因为有内联，而是ModelForm的工作方式。它们只为模型上的实际字段构建表单域，而不是相关的管理器属性。但是，您可以将此功能添加到表单中：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|513860|from+django.contrib.admin.widgets+import+FilteredSelectMultiple

class+ProjectAdminForm(forms.ModelForm):
++++class+Meta:
++++++++model+=+Project

++++userprofiles+=+forms.ModelMultipleChoiceField(
++++++++queryset=UserProfile.objects.all(),
++++++++required=False,
++++++++widget=FilteredSelectMultiple(
++++++++++++verbose_name='User+Profiles',
++++++++++++is_stacked=False
++++++++)
++++)

++++def+__init__(self,+*args,+**kwargs):
++++++++super(ProjectAdminForm,+self).__init__(*args,+**kwargs)
++++++++++++if+self.instance.pk:
++++++++++++++++self.fields['userprofiles'].initial+=+self.instance.userprofile_set.all()

++++def+save(self,+commit=True):
++++++++project+=+super(ProjectAdminForm,+self).save(commit=False)++
++++++++if+commit:
++++++++++++project.save()

++++++++if+project.pk:
++++++++++++project.userprofile_set+=+self.cleaned_data['userprofiles']
++++++++++++self.save_m2m()

++++++++return+project

class+ProjectAdmin(admin.ModelAdmin):
++++form+=+ProjectAdminForm
++++...|code-block|syntax|javascript|513861|做一个简单的演练可能是合适的。首先，我们定义一个userprofiles表单域。它将使用ModelMultipleChoiceField，这在默认情况下将导致多选框。由于这不是模型上的实际字段，因此我们不能只将其添加到filter_horizontal中，因此我们告诉它只需使用相同的小部件FilteredSelectMultiple，如果它在filter_horizontal中列出，它将使用该小部件。|513862|我们最初将查询集设置为整个UserProfile集，但您不能在这里过滤它，因为在类定义的这个阶段，表单还没有被实例化，因此还没有它的instance集。因此，我们覆盖了__init__，这样我们就可以将过滤后的查询集设置为字段的初始值。|513863|最后，覆盖save方法，以便可以将相关管理器的内容设置为与表单的POST数据中的内容相同的内容，这样就完成了。|513864|entityMap^0|C|9|0|0|O|C|18|O|31|H|41|M|4S|H|0|D|B|1U|8|2C|8|0|5|4|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|R|$]]

The problem isn't from having inlines; it's from the way <code>ModelForm</code>s work, in general. They only build form fields for actual fields on the model, not related manager attributes. However, you can add this functionality to the form:

<pre><code>from django.contrib.admin.widgets import FilteredSelectMultiple

class ProjectAdminForm(forms.ModelForm):
 class Meta:
 model = Project

 userprofiles = forms.ModelMultipleChoiceField(
 queryset=UserProfile.objects.all(),
 required=False,
 widget=FilteredSelectMultiple(
 verbose_name='User Profiles',
 is_stacked=False
 )
 )

 def __init__(self, *args, **kwargs):
 super(ProjectAdminForm, self).__init__(*args, **kwargs)
 if self.instance.pk:
 self.fields['userprofiles'].initial = self.instance.userprofile_set.all()

 def save(self, commit=True):
 project = super(ProjectAdminForm, self).save(commit=False) 
 if commit:
 project.save()

 if project.pk:
 project.userprofile_set = self.cleaned_data['userprofiles']
 self.save_m2m()

 return project

class ProjectAdmin(admin.ModelAdmin):
 form = ProjectAdminForm
 ...
</code></pre>

A little walkthrough is probably in order. First, we define a <code>userprofiles</code> form field. It will use a <code>ModelMultipleChoiceField</code>, which by default will result in a multiple select box. Since this isn't an actual field on the model, we can't just add it to <code>filter_horizontal</code>, so we instead tell it to simply use the same widget, <code>FilteredSelectMultiple</code>, that it would use if it were listed in <code>filter_horizontal</code>.

We initially set the queryset as the entire <code>UserProfile</code> set, you can't filter it here, yet, because at this stage of the class definition, the form hasn't been instantiated and thus doesn't have it's <code>instance</code> set yet. As a result, we override <code>__init__</code> so that we can set the filtered queryset as the field's initial value.

Finally, we override the <code>save</code> method, so that we can set the related manager's contents to the same as what was in the form's POST data, and you're done.

blocks|key|513972|text|在处理与自身的多对多关系时，这是一个次要的附加。一个人可能想把自己排除在选择之外：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|513973|if+self.instance.pk:
++++++++self.fields['field_being_added'].queryset+=+self.fields['field_being_added'].queryset.exclude(pk=self.instance.pk)
++++++++self.fields['field_being_added'].initial+=+"""Corresponding+result+queryset"""|code-block|syntax|javascript|513974|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

A minor addition when dealing with a many to many relationship with itself. One might want to exclude itself from the choices:

<pre><code>if self.instance.pk:
 self.fields['field_being_added'].queryset = self.fields['field_being_added'].queryset.exclude(pk=self.instance.pk)
 self.fields['field_being_added'].initial = """Corresponding result queryset"""
</code></pre>

blocks|key|297535|text|有一个更简单的解决方案，只需添加filter_horizontal，如here所解释的那样|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|297536|class+YourAdmin(ModelAdmin)
++++filter_horizontal+=+('your_many_to_many_field',)|code-block|syntax|javascript|297537|之前：|297538|📷|atomic|297539|​|297540|之后：|297541|297542|297543|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/8043918/4191904|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/08b35a714ace888e8e180388c79847f1.png|imageAlt|2|https://ask.qcloudimg.com/http-save/yehe-900000/44f4c290486bdcc0f840435037734b3d.png^0|G|H|Z|4|0|0|0|0|0|1|1|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|F|3|G|5|H|7|1H|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1I|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1J|8|@]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|P|3|Q|5|6|7|1N|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1O|8|@]|D|@]|E|$]]|$1|T|3|N|5|O|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|U|3|Q|5|6|7|1T|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]|13|$5|14|Z|15|E|$16|17|18|-4]]|19|$5|14|Z|15|E|$16|1A|18|-4]]]]

There is an easier solution, just add <code>filter_horizontal</code>, as explained <a href="https://stackoverflow.com/a/8043918/4191904">here</a>:
<pre><code>class YourAdmin(ModelAdmin)
 filter_horizontal = ('your_many_to_many_field',)

</code></pre>
Before:<a href="https://i.stack.imgur.com/8zu6F.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8zu6F.png" alt="enter image description here" /></a>
After:<a href="https://i.stack.imgur.com/WyhBg.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WyhBg.png" alt="enter image description here" /></a>

I have a Django model field that I'd like to inline. The field is a many-to-many relationship. So there are "Projects" and "User profiles". Each user profile can select any number of projects.

Currently, I've got the "tabular" inline view working. Is there a way to have a "horizontal filter" so that I can easily add and remove projects from a user profile?

Please see the attached picture for an example.<img src="https://i.stack.imgur.com/v9bQE.png" alt="enter image description here">

Here's the model code for the User Profile:

<pre><code>class UserProfile(models.Model):
 user = models.OneToOneField(User, unique=True)
 projects = models.ManyToManyField(Project, blank=True, help_text="Select the projects that this user is currently working on.")
</code></pre>

And the model code for a Project:

<pre><code>class Project(models.Model):
 name = models.CharField(max_length=100, unique=True)
 application_identifier = models.CharField(max_length=100)
 type = models.IntegerField(choices=ProjectType)
 account = models.ForeignKey(Account)
 principle_investigator = models.ForeignKey(User)
 active = models.BooleanField()
</code></pre>

And the admin code for the view:

<pre><code>class UserProfileInline(admin.TabularInline):
 model = UserProfile.projects.through
 extra = 0
 verbose_name = 'user'
 verbose_name_plural = 'users'

class ProjectAdmin(admin.ModelAdmin):
 list_display = ('name', 'application_identifier', 'type', 'account', 'active')
 search_fields = ('name', 'application_identifier', 'account__name')
 list_filter = ('type', 'active')
 inlines = [UserProfileInline,]
admin.site.register(Project, ProjectAdmin)
</code></pre>

Django admin interface: using horizontal_filter with inline ManyToMany field

Django

我有一个要内联的Django模型字段。该字段是多对多关系。所以有“项目”和“用户档案”。每个用户配置文件可以选择任意数量的项目。目前，我已经实现了“表格”内联视图。有没有一种方法可以让我有一个“水平过滤器”，这样我就可以很容易地在用户配置文件中添加和删除项目？请看附件中的图片作为例子。​以下是用户配置文件的模型代码：c...

问Django管理界面:对内联ManyToMany字段使用horizontal_filter
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django管理界面:对内联ManyToMany字段使用horizontal_filterEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django管理界面:对内联ManyToMany字段使用horizontal_filter
EN