Hello,
It's a false place. All what you need - one Model for Settings.
if SettingsModel.objects.get(code='guest_can_comment'):
can_post
else:
cant_post
You can wrap this in one decorator function.
Harro schrieb:
Because the authentication backend now allows for role based
permissions you might have a blog post which anonymous users are
allowed to comment on (create_comment) and another they can't.
Now you would have to have a guest_can_comment flag or something on
the blog post and check that before displaying the form.
Instead I want to use the permission system to see if the anonymous
user has create_comment permission on that specific blog item.
so that's why I think this would be a good addition.
It would also allow for temporary shutting down of certain publicly
accessible items by simply removing/disabling the permissions for
guest users.
On Jan 14, 3:17 pm, Juan Pablo Scaletti <juanpablo.scale...@gmail.com>
wrote:
If an AnonymousUser can do something then everybody can do that as well.
So why a regular unprotected view can't do the job?
On Thu, Jan 14, 2010 at 8:13 AM, Harro <hvdkl...@gmail.com> wrote:
I was having a look at the new 1.2 row level permission support that
got added and ran into the problem that the AnonymousUser does not
call the authentication backend functions.
The default backend doesn't need this, but with a custom backend I
might want to implement Guest permissions.
I think it will make the permission system even more powerful !
What do you guys think?
Ticket:http://code.djangoproject.com/ticket/12557
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com<django-developers%2Bunsubscr
i...@googlegroups.com>
.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
--
Juan Pablo Scaletti
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
