Added link to Luke Plant's current-user hack from docs/faq.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3435 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 9 insertions, 4 deletions

diff --git a/docs/faq.txt b/docs/faq.txt
index a77f45852c..1f4f7bcce3 100644
--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -546,10 +546,15 @@ Set the ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting to ``True``. See the
 How do I automatically set a field's value to the user who last edited the object in the admin?
 -----------------------------------------------------------------------------------------------
 
-At this point, you can't do this. But it's an oft-requested feature, so we're
-discussing how it can be implemented. The problem is we don't want to couple
-the model layer with the admin layer with the request layer (to get the current
-user). It's a tricky problem.
+At this point, Django doesn't have an official way to do this. But it's an oft-requested
+feature, so we're discussing how it can be implemented. The problem is we don't want to couple
+the model layer with the admin layer with the request layer (to get the current user). It's a
+tricky problem.
+
+One person hacked up a `solution that doesn't require patching Django`_, but note that it's an
+unofficial solution, and there's no guarantee it won't break at some point.
+
+.. _solution that doesn't require patching Django: http://lukeplant.me.uk/blog.php?id=1107301634
 
 How do I limit admin access so that objects can only be edited by the users who created them?
 ---------------------------------------------------------------------------------------------