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
This commit is contained in:
parent
655d5afea9
commit
a0585e99bf
|
@ -61,3 +61,14 @@ process. If you require data to exist during test conditions, you
|
||||||
should either insert it using :ref:`test fixtures
|
should either insert it using :ref:`test fixtures
|
||||||
<topics-testing-fixtures>`, or using the ``setUp()`` method of your
|
<topics-testing-fixtures>`, or using the ``setUp()`` method of your
|
||||||
test case.
|
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.
|
||||||
|
|
Loading…
Reference in New Issue