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/topics/forms/modelforms.txt | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index bd312562cb..a55e7a5ced 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -430,13 +430,11 @@ In addition, Django applies the following rule: if you set ``editable=False`` on the model field, *any* form created from the model via ``ModelForm`` will not include that field. -.. versionchanged:: 1.6 - - Before version 1.6, the ``'__all__'`` shortcut did not exist, but omitting - the ``fields`` attribute had the same effect. Omitting both ``fields`` and - ``exclude`` is now deprecated, but will continue to work as before until - version 1.8 +.. versionchanged:: 1.8 + In older versions, omitting both ``fields`` and ``exclude`` resulted in + a form with all the model's fields. Doing this now raises an + :exc:`~django.core.exceptions.ImproperlyConfigured` exception. .. note:: -- cgit v1.3