一首诗 wrote:
> But how can I give some information to user that the delete is not
> allowed?
> By the codes above, the user just see that the delete was done!
This is exactly the case for using exceptions. Define your own exception
and raise it where user shouldn't delete an object. Then define a
middleware hook that will catch your exception and create some sensible
response for the user (403 Forbidden should fit).
All this may might look like this:
middleware:
-----------
class EForbidden(Exception):
pass
class ForbiddenMiddleware:
def process_exception(self, request, exception):
if not isinstance(exception, EForbidden):
return
from django.http import HttpResponseForbidden
from django.template import loader, RequestContext
try:
template = loader.get_template('403.html')
context = RequestContext(request, {'message': str(exception)})
return HttpResponseForbidden(template.render(context))
except:
pass # Let Django show the exception
models:
-------
from myproject.middleware import EForbidden
...
def delete(self):
if <condition>:
raise EForbidden('You can\'t delete it')
super(Model, self).delete()
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
