summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLuke Plant <L.Plant.98@cantab.net>2011-01-28 15:48:35 +0000
committerLuke Plant <L.Plant.98@cantab.net>2011-01-28 15:48:35 +0000
commita138e3be0e7a72ec7ae6cf89ab40ed0b75b6ff42 (patch)
treeac5a1e48cf38c40cd8f90bb0ce8a23ef447ce5dd /docs
parentb3ad41bfd51562e5d18350b18650ad4638ed0869 (diff)
[1.2.X] Added note to 1.2.5 release notes about ModelAdmin.lookup_allowed change
Backport of [15352] from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15353 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.2.5.txt11
1 files changed, 11 insertions, 0 deletions
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.