From ee4edb1eda2ac8f09eb298929282b44776930c89 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 21 Mar 2014 20:44:34 -0400 Subject: Made ModelForms raise ImproperlyConfigured if the list of fields is not specified. Also applies to modelform(set)_factory and generic model views. refs #19733. --- docs/ref/class-based-views/mixins-editing.txt | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'docs/ref/class-based-views') diff --git a/docs/ref/class-based-views/mixins-editing.txt b/docs/ref/class-based-views/mixins-editing.txt index dbe1c91547..cfa343c937 100644 --- a/docs/ref/class-based-views/mixins-editing.txt +++ b/docs/ref/class-based-views/mixins-editing.txt @@ -129,15 +129,18 @@ ModelFormMixin .. attribute:: fields - .. versionadded:: 1.6 - A list of names of fields. This is interpreted the same way as the ``Meta.fields`` attribute of :class:`~django.forms.ModelForm`. This is a required attribute if you are generating the form class automatically (e.g. using ``model``). Omitting this attribute will - result in all fields being used, but this behavior is deprecated - and will be removed in Django 1.8. + result in an :exc:`~django.core.exceptions.ImproperlyConfigured` + exception. + + .. versionchanged:: 1.8 + + Previously, omitting this attribute was allowed and resulted in + a form with all fields of the model. .. attribute:: success_url -- cgit v1.3