From 5dbf1c4b23cda915369f4895be293369575238d0 Mon Sep 17 00:00:00 2001
From: Taavi Teska <taaviteska@users.noreply.github.com>
Date: Mon, 10 Apr 2017 20:24:44 +0200
Subject: [PATCH] Fixed #27947 -- Doc'd that model Field.error_messages often
 don't propagate to forms.

---
 AUTHORS                    | 1 +
 docs/ref/models/fields.txt | 3 +++
 2 files changed, 4 insertions(+)

diff --git a/AUTHORS b/AUTHORS
index 1817ebafa7..35d80ec85c 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -737,6 +737,7 @@ answer newbie questions, and generally made Django that much better:
     Sutrisno Efendi <kangfend@gmail.com>
     Swaroop C H <http://www.swaroopch.info>
     Szilveszter Farkas <szilveszter.farkas@gmail.com>
+    Taavi Teska <taaviteska@gmail.com>
     Tai Lee <real.human@mrmachine.net>
     Takashi Matsuo <matsuo.takashi@gmail.com>
     Tareque Hossain <http://www.codexn.com>
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 439bf4283c..36b553f92c 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``
 -------------