How would you handle multiple checkers? I'm designing RLP to work on
top of model level checking. Would it be:
checker = (RowLevel, ModelLevel,)
How is the order of permissions checking done if it is multiple? Is it
the order they are specified as?
One thing that will need to be done if it is
> I actually hadn't thought of that. I thought there would be one and
> only one type of checking for each model. I can't think of a use case
> for multiple checkers, but then again it's Friday and my brain is a
> little fried :)
No worries about the fried brain, I can understand that. It's been
Hi,
I'm the SoC student working on row level permissions. Just a few
questions about generic authorization for Joseph, and any one else who
has input.
1) Will there be any support for the previous method of checking
permissions? (e.g. will users.has_permission work?)
2) How are the two of us go
I'll try to be on tonight between 7 and 11 MT, I just finished off a 4
hour meeting and need to finish off some work then head home. I might
be too tired to make it on tonight, but I'll certainly try.
If not, I'll be around tomorrow from 9am to 3:00pm EST (7am to 1pm MT),
or on Sat any time past
As an aside, if anyone is interested in this conversation, please let
us know when you are available (on this topic) and we'll try working
out a time for everyone. Otherwise, we'll post a log/summary of our
conversation and decisions to keep everyone up to date.
Chris
--~--~-~--~~--
Hi,
Joseph and I had a discussion today about how to work our two projects
together. Here is what we decided upon.
Because Joseph is currently implementing default_has_permission by
using user.has_perm. I will be adding row level permissions to the
user.has_perm method. To allow for this, user.h
Hi,
I'm the developer working on the branch.
A few things, hopefully to answer your concerns.
1) The HTML and JS is written that the AJAX can be turned off very
easily(currently it works better with JS disabled then enabled). And I
plan on implementing a method of selecting if you wish to use t
The main reason why I switched was more timing then anything else. I
wanted to try a few different toolkits to practice with them and find
out the differences. I have never touched AJAX before this summer.
I tried Dojo first and did like it, and wrote some working code, which
I should be able to
Hi,
Joseph and I were talking earlier this evening about how to replace the
permission wrapper context to allow for his generic auth and my row
level permission. We could not determine a way to expand the current
context processor to allow an object to be passed (if you have any
ideas, please let
Hi,
I'm the GSoCer working on row level permissions.
Row level permissions are now implemented and, in my test cases, are
working.
I wanted to find out if anyone has had an opportunity to try the row
level permissions (per-object-permission) branch or read my wiki pages
on it. Are there any com
r = (('edit'),('delete'),)
>
> This way we can specify what permissions the creator of an object has
> on objects he or she creates through the Django administration
> interface.
>
> Chris Long wrote:
> > Hi,
> >
> > I'm the GSoCer worki
It's determined by the settings under the admin options. By default
both are set to false, so no permissions will be creation. To do what
you want:
...
class Admin:
grant_change_row_level_perm = True
...
That should just set the change row levle permission and not set any
delete row level per
My pleasure :D
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
Hi Mart,
I'm the per-obect-perm developher.
Depends on what magic you are looking for it to do. The
row_level_permissions option in the meta class does two things that can
be rewritten in a way that doesn't need to involve the db.options (meta
class).
The first thing the option does is create a
Hi,
With the select list, I am hoping for some general public opinion on
how to handle this.
If the user does not have change permissions on this, does this mean
they can not see the object in the select list? I'm not sure if that
would be a workable solution.
A proposal: Create an additional "
It would work, but there it's not very flexible. The current
show_all_rows setting uses the change permission to determine if the
object should be shown on the change list. Which makes sense, since the
objects listed on the change list are those the user is able to edit.
For a related object in a
Joseph Kocherhans wrote:
> So I should probably get started on the generic-auth and
> per-object-permissions (hereafter pop) integration soon. I've had
> problems trying to merge changes from the trunk into the generic-auth
> branch, so I'd just assume call that branch dead. The actual
> generic-
Already had a few people point out some bugs and some features they
want. Community involvement is key to get this moving ahead as quickly
as possible.
Chris
Joseph Kocherhans wrote:
> On 9/1/06, Linicks <[EMAIL PROTECTED]> wrote:
> >
> > Once (gen-auth/pop) are merged, what are the major barrie
Sometime over the next few days when I feel a bit more organized I'll
merge it to trunk. Moving into a new house so everything has been a bit
chaotic.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django d
The generic auth branch should allow you to create your own custom
permission checking system easily.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send ema
I'll take a look at it today.
Chris
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this group,
Nope, not a correct assumption.
Fixed in the latest version, I did try it with the model you have given
and it does work, but the test was not as indepth (lack of time this
week). So please give it a try and see if it fixes this problem.
Chris
--~--~-~--~~~---~--~--
Latest changeset should fix it.
Chris
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from this grou
Fixed in the latest revision.
Thanks,
Chris
--~--~-~--~~~---~--~~
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@googlegroups.com
To unsubscribe from th
> I'm going to keep lobbing them at you, until it all works :)
Perfect, keep them coming. :)
Appears to be something related specifically to MySQL. Have it fixed by
Monday.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Hey,
Latest release should fix both. The user_id problem is related to the
generic relations used in the POP branch, I've written up a ticket
#2749 about it, but it has been fixed in my branch.
Let me know how it goes.
Chris
--~--~-~--~~~---~--~~
You received t
The problem appears to be related to the same stuff we've been dealing
w/ earlier. This line(django.contrib.admin.main.ChangeList line 695):
qs =
self.manager.filter(id__in=RowLevelPermission.objects.get_model_list(self.user,
self.model,
self.opts.get_ch
I'll take a look at it and (if all goes well) fix it.
Cheers,
Chris
--~--~-~--~~~---~--~~
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@googlegroups.co
Fixed in latest revision.
Chris
schotm wrote:
> Hi i just started with django yesterday and was testing RLP today.
>
> In the order it says this in the documentation:
> The order of checking permissions will work in the following order:
> User Row Level Permission -> Group Row Level Permission -
Fixed, though not exactly sure how that error was introduced. The file
where the bug was, I haven't touched in a while. Strange and
random...but it is fixed now.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hey Everyone,
I know I've gone missing the past few months, been busy finishing off
my last semester at school and recovering from some surgeries.
I hope to start working on the RLP branch once again, I've merged the
RLP branch to the latest trunk. I've gone through and fixed up some
stuff (gene
31 matches
Mail list logo
