From c3d3aeeafad1562ab82b250a55e09c2f513b0105 Mon Sep 17 00:00:00 2001 From: Taavi Teska Date: Mon, 10 Apr 2017 20:24:44 +0200 Subject: [1.11.x] Fixed #27947 -- Doc'd that model Field.error_messages often don't propagate to forms. Backport of 5dbf1c4b23cda915369f4895be293369575238d0 from master --- docs/ref/models/fields.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs') diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index b343aca6d9..b034a80dd7 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -254,6 +254,9 @@ Error message keys include ``null``, ``blank``, ``invalid``, ``invalid_choice``, ``unique``, and ``unique_for_date``. Additional error message keys are specified for each field in the `Field types`_ section below. +These error messages often don't propagate to forms. See +:ref:`considerations-regarding-model-errormessages`. + ``help_text`` ------------- -- cgit v1.3