From a0585e99bf7d8644a5f56aba89c451bcefe20b53 Mon Sep 17 00:00:00 2001
From: Luke Plant <L.Plant.98@cantab.net>
Date: Fri, 28 Jan 2011 15:47:40 +0000
Subject: [PATCH] Added note to 1.2.5 release notes about
 ModelAdmin.lookup_allowed change

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15352 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/releases/1.2.5.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/releases/1.2.5.txt b/docs/releases/1.2.5.txt
index cfdaeaa94e..81b2e18d48 100644
--- a/docs/releases/1.2.5.txt
+++ b/docs/releases/1.2.5.txt
@@ -61,3 +61,14 @@ process. If you require data to exist during test conditions, you
 should either insert it using :ref:`test fixtures
 <topics-testing-fixtures>`, or using the ``setUp()`` method of your
 test case.
+
+ModelAdmin.lookup_allowed signature changed
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Django 1.2.4 introduced a method ``lookup_allowed`` on ``ModelAdmin``, to cope
+with a security issue (changeset `[15033]
+<http://code.djangoproject.com/changeset/15033>`_). Although this method was
+never documented, it seems some people have overridden ``lookup_allowed``,
+especially to cope with regressions introduced by that changeset. While the
+method is still undocumented and not marked as stable, it may be helpful to know
+that the signature of this function has changed.