On Tue, Apr 17, 2012 at 12:42 PM, Mike wrote:
> One problem I see is that if User 1 somehow obtains a url to a view that
> displays an object owned by User 2. User 1 will be able to view User 2's
> object. I'll have to write code in every view function that displays
> user-owned data to make sur
in
> my
> > model by setting a ForeignKey to the user that owns the object:
> >
> > owner = models.ForeignKey(User)
> >
> > Is this a bad idea?
>
> Seems quite sensible for the use case you describe.
>
> > Can someone explain under what c
ey(User)
>
> Is this a bad idea?
Seems quite sensible for the use case you describe.
> Can someone explain under what circumstances I would
> need to use a row level permissions app?
Row level permissions are useful when you have a more complex (and
possibly dynamic) scheme - a co
under what circumstances I would
need to use a row level permissions app?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/7JBlHmcJvkUJ.
To post to t
Isn't this possible with a custom UserProfile and overriding the
queryset() & has_change_permission() methods of each ModelAdmin?
--
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
hi,
I have an app with a model called Project. A project can have several
areas, and each area many children. The fk relationship is child -> area
-> project. Now for user rights:
some users should only have access to the children under a specific
area, others only to children and areas under a s
Row Level Permissions work perfectly:
http://code.djangoproject.com/wiki/RowLevelPermissions
On Thu, Mar 11, 2010 at 14:21, Rodrigo Cea wrote:
> What's the current state of the art for Row Level Permissions?
>
> I need to set permissions for users on a MPTT-based page tree, whe
What's the current state of the art for Row Level Permissions?
I need to set permissions for users on a MPTT-based page tree, where
each user will be allowed to edit only a specific branch, using the
admin.
I found this: http://www.djangosnippets.org/snippets/1054/, which
might work, but w
is not filled in, but
because owner is not on the form there is nowhere to display it!
Mystery solved.
So now trying to work out how to pass the owner info to the admin
form. Tried hidden_fields, but this not available in version 1.0 of
Django.
On May 9, 9:18 am, phoebebright wrote:
>
#x27;inline_admin_formsets': [],
'is_popup': False,
'media': '\n\n\n\n\n\n',
'object_id': u'86',
'opts': ,
'ordered_objects': [],
'original': ,
'root_path': u'/admin/',
'save_as': False,
's
I have almost implemented a row level permissions facilitiy for a
model in my app.
I can change the owner of the record
Display only their records in admin
But when logged in as the owner and click Save on the edit screen I
get the error "Please correct the error below." but no ind
Hi,
I need to use row level permissions on a project I'm developing.
I've found several solutions:
http://code.djangoproject.com/wiki/RowLevelPermissions
http://code.google.com/p/django-granular-permissions/
http://www.technobabble.dk/2008/jan/06/filtering-foreign-key-choices-newf
t;[EMAIL PROTECTED]> wrote:
> What's the state of the art for row-level permissions in Django?
> I'm working on an application where I need to allow users to edit
> their own personal info but nobody else's. What app, hack, patch or
> branch should I use in order to
On Wed, 2008-05-14 at 01:39 -0700, Nick Day wrote:
> I've just seen this thread and I'll be requiring row-level permissions
> for an upcoming project in the next couple of months. I'm using Django
> for a project at the moment and would love to use it again, but this
&g
I've just seen this thread and I'll be requiring row-level permissions
for an upcoming project in the next couple of months. I'm using Django
for a project at the moment and would love to use it again, but this
feature will essentially make or break the decision.
Is there a rou
On 5/6/08, Rodrigo Culagovski <[EMAIL PROTECTED]> wrote:
>
> What's the state of the art for row-level permissions in Django?
> I'm working on an application where I need to allow users to edit
> their own personal info but nobody else's. What app, hack, p
What's the state of the art for row-level permissions in Django?
I'm working on an application where I need to allow users to edit
their own personal info but nobody else's. What app, hack, patch or
branch should I use in order to be able to do this via the admin site?
T
Joesph,
Thanks a lot. I am working on having some sort of ACL for Django, and
thought Generic Authorization and RLP would solve that problem, and I
think they would have. Pity.
Arvind
On Oct 11, 4:15 pm, "Joseph Kocherhans" <[EMAIL PROTECTED]> wrote:
> On 10/11/07, arv43 <[EMAIL PROTECTED]> wrot
On 10/11/07, arv43 <[EMAIL PROTECTED]> wrote:
>
> Does anyone know how and if Generic Authorization and RLP are going to
> fit together? It says on the RLP page to look at Generic Authorization
> to know how they do, but I am not sure how they do. Maybe am missing
> something.
> Are they both goin
Does anyone know how and if Generic Authorization and RLP are going to
fit together? It says on the RLP page to look at Generic Authorization
to know how they do, but I am not sure how they do. Maybe am missing
something.
Are they both going to be rolled into the trunk sometime? or is it one
vs th
On Thu, 2007-10-04 at 12:45 +, RKnobelspies wrote:
> We are also working on projects that require some form of RLP-
> functionality but at the same time we need to work with the actual
> trunk-version of django to take advantage of the recent improvements
> with forms.
>
> There was a convers
We are also working on projects that require some form of RLP-
functionality but at the same time we need to work with the actual
trunk-version of django to take advantage of the recent improvements
with forms.
There was a conversation on the django-sprint IRC between Malcolm and
a person, who of
On 9/10/07, djworth <[EMAIL PROTECTED]> wrote:
>
> I have been trying to figure out what the current status is of the RLP
> branch. Does anyone know? It seems dead or have I missed something?
No, no, he's not dead, he's, he's restin'! Remarkable bird, the RLP
Branch, idn'it, ay? Beautiful pluma
Aryko,
I didn't need row-level permissions so much as I needed role-based
permissions, sort of the same thing but not exactly. I rolled my own. I do
not believe the rlp branch is being actively maintained, but cannot say for
sure as I have not looked into it in a while.
Essentially I asso
Hey,
I also need to use RLP for my project and I'd like to know if there's
any update to expect for this branch or any way to include RLP to the
trunk.
Thanks.
On Sep 10, 3:22 am, djworth <[EMAIL PROTECTED]> wrote:
> I have been trying to figure out what the current status is of the RLP
> branc
I have been trying to figure out what the current status is of the RLP
branch. Does anyone know? It seems dead or have I missed something?
I'm going to need RLP in my project but I'm not sure if I need to
implement it or if it's already done/almost done.
What is everyone else doing about RLP?
Hi. I already posted about a realted issue but I thought I'd rephrase
the question in the hope that someone could help.
I beleive newforms-admin will allow you to restrict access of certain
records to certain users by the use of hooks. I am hoping that this
will allow me to use the admin interfac
Hi,
I'm the developer working on that branch.
I've had some personal issues come up that haev delayed me from
committing the latest code for row level permissions. Which is required
to work with the wiki article.
One thing to note, is that they don't do anything at this current
I got it. Thanks.
--~--~-~--~~~---~--~~
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 PROTECT
On 7/23/06, mahakala <[EMAIL PROTECTED]> wrote:
> Would anybody kindly tell me what's wrong? Thanks.
Probably it's a bug in the branch.
The various side branches of Django are there to give people a place
to develop new features without breaking the main trunk, and are
provided not because they'
Hi, everybdoy
I just download the row level permission branch, and try as the wiki
said, add row_level_permissions to class Meta:
class Poll(models.Model):
question = models.CharField(maxlength=200)
pub_date = models.DateTimeField('date published')
class Admin:
pass
clas
31 matches
Mail list logo
