Seems reasonable to me, the tool should try it's best to preserve the
behaviour as much as possible, wheter it's documented or not.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails fr
figured on project's
settings.
Best regards,
Enrico
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/TN4U4MJk_v0J.
To post to this gro
templates on a project
level basis.
More information on the ticket:
http://code.djangoproject.com/ticket/14140
Does this seen like a reasonable approach?
Is anyone else interested on this? Any alternative proposals?
Best regards,
Enrico
--
You received this message because you are subscribed
x27;s what I've done)
3. Give the user permission to edit "every" instance of a blog post?
If I give the user the permissions, he'll be able to edit other's
posts.
I can block this using custom permissions on ModelAdmin, but another
admin app
Please forgive if I'm not making myself clear.
Best regards,
Enrico
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googleg
I came across the situation described on the ticket #8146 [1], I've
changed the permissions for a model allowing the user to access only
certain instances of a model.
As I don't want to give the user access to all objects, I've extended
the `AdminSite`, changing the `index` view to ignore
`user.h
