Django

Code

Changeset 3435

Show
Ignore:
Timestamp:
07/23/06 21:28:09 (2 years ago)
Author:
adrian
Message:

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

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • django/trunk/docs/faq.txt

    r3434 r3435  
    547547----------------------------------------------------------------------------------------------- 
    548548 
    549 At this point, you can't do this. But it's an oft-requested feature, so we're 
    550 discussing how it can be implemented. The problem is we don't want to couple 
    551 the model layer with the admin layer with the request layer (to get the current 
    552 user). It's a tricky problem. 
     549At this point, Django doesn't have an official way to do this. But it's an oft-requested 
     550feature, so we're discussing how it can be implemented. The problem is we don't want to couple 
     551the model layer with the admin layer with the request layer (to get the current user). It's a 
     552tricky problem. 
     553 
     554One person hacked up a `solution that doesn't require patching Django`_, but note that it's an 
     555unofficial solution, and there's no guarantee it won't break at some point. 
     556 
     557.. _solution that doesn't require patching Django: http://lukeplant.me.uk/blog.php?id=1107301634 
    553558 
    554559How do I limit admin access so that objects can only be edited by the users who created them?