On Thu, Aug 5, 2010 at 3:32 AM, lukaszb wrote:
> Thanks for the comment! I really do think that this "backends ready &&
> included" parts of Django are extremely useful (and fun to extend if
> needed).
>
> About the admin, I haven't really get into admin integration yet as I
> cannot answer this:
new
> "grouping models" - I often use intermediate models for this (i.e.
> Team model with fk to Group among other fields). Let me know if you
> have different experience.
>
> On 4 Sie, 15:26, derek wrote:
>
> > On Aug 4, 1:20 am, lukaszb wrote:
>
>
01:34, Russell Keith-Magee wrote:
> On Wed, Aug 4, 2010 at 7:20 AM, lukaszb wrote:
> > Hi all,
>
> > I'd like to announce django-guardian - very basic yet usable per
> > object permissions
> > implementation for Django 1.2, using new authorization backend
>
(i.e.
Team model with fk to Group among other fields). Let me know if you
have different experience.
On 4 Sie, 15:26, derek wrote:
> On Aug 4, 1:20 am, lukaszb wrote:
>
>
>
>
>
> > Hi all,
>
> > I'd like to announce django-guardian - very basic yet usable per
>
On Aug 4, 1:20 am, lukaszb wrote:
> Hi all,
>
> I'd like to announce django-guardian - very basic yet usable per
> object permissions
> implementation for Django 1.2, using new authorization backend
> facilities.
>
> It was created during 2 days sprint, code have bee
On Wed, Aug 4, 2010 at 7:20 AM, lukaszb wrote:
> Hi all,
>
> I'd like to announce django-guardian - very basic yet usable per
> object permissions
> implementation for Django 1.2, using new authorization backend
> facilities.
>
> It was created during 2 days sprint
Hi all,
I'd like to announce django-guardian - very basic yet usable per
object permissions
implementation for Django 1.2, using new authorization backend
facilities.
It was created during 2 days sprint, code have been released and may
be found at http://github.com/lukaszb/django-gua
n Tue, Nov 24, 2009 at 11:16 PM, rebus_ wrote:
> >> >> 2009/11/24 nek4life :
> >> >>> You should look into django-authority. I'm pretty sure that has per-
> >> >>> object-permissions.
>
> >> >>>http://packages.python.org/djang
>>> You should look into django-authority. I'm pretty sure that has per-
>> >>> object-permissions.
>> >>>
>> >>> http://packages.python.org/django-authority/index.html
>> >>>
>> >>> On Nov 24, 7:00 am, gamliel
have the admin site up and running but I need to create a group of
> users,
> >>>> such that each of the users will be able to edit objects that are only
> >>>> relevant to them (e.g Project objects that the user is also the
> >>>> ProjectManager).
2009/11/25 Russell Keith-Magee :
> On Tue, Nov 24, 2009 at 11:16 PM, rebus_ wrote:
>> 2009/11/24 nek4life :
>>> You should look into django-authority. I'm pretty sure that has per-
>>> object-permissions.
>>>
>>> http://packages.python.org/djan
On Tue, Nov 24, 2009 at 11:16 PM, rebus_ wrote:
> 2009/11/24 nek4life :
>> You should look into django-authority. I'm pretty sure that has per-
>> object-permissions.
>>
>> http://packages.python.org/django-authority/index.html
>>
>> On Nov 24
> I know that in the past Django had a Per-object permissions branch, which is
> now abandoned.
>
> Should I peruse this direction and try to incorporate this branch to my
> current code? is it documented and running properly?
>
> Any other ideas/suggestions/resources regarding
2009/11/24 nek4life :
> You should look into django-authority. I'm pretty sure that has per-
> object-permissions.
>
> http://packages.python.org/django-authority/index.html
>
> On Nov 24, 7:00 am, gamliel roi wrote:
>> Hello all,
>>
>> I have the admin s
You should look into django-authority. I'm pretty sure that has per-
object-permissions.
http://packages.python.org/django-authority/index.html
On Nov 24, 7:00 am, gamliel roi wrote:
> Hello all,
>
> I have the admin site up and running but I need to create a group of users,
&g
cts that the user is also
> the ProjectManager).
>
> I know that in the past Django had a Per-object permissions branch,
> which is now abandoned.
>
> Should I peruse this direction and try to incorporate this branch to
> my current code? is it documented and running properly?
Hello all,
I have the admin site up and running but I need to create a group of users,
such that each of the users will be able to edit objects that are only
relevant to them (e.g Project objects that the user is also the
ProjectManager).
I know that in the past Django had a Per-object
hello all,
For freesound.org I really need per-object permissions and caching.
I would also love to use the {% cache %} template tag as much as
possible because it's so easy and transparent!
Now, say for example I have a sound, and a user can either edit it or
not, or vote for it or not.
Hello,
On Fri, Jul 25, 2008 at 4:55 PM, Hanne Moa <[EMAIL PROTECTED]> wrote:
>
> AFAIK is_authenticated doesn't enter into it at all.
I think I might not have explained very well...
Newforms-admin ( i.e. "admin" now :) ) has per-object permissions.
These are mor
On Fri, Jul 25, 2008 at 11:39 AM, Bram de Jong <[EMAIL PROTECTED]> wrote:
> For freesound.org I really need per-object permissions and caching.
> I would also love to use the {% cache %} template tag as much as
> possible because it's so easy and transparent!
> Now, say for
On 3/23/07, Scanner <[EMAIL PROTECTED]> wrote:
>
> On Mar 22, 5:50 pm, "Matthew Flanagan" <[EMAIL PROTECTED]> wrote:
> > I'm definitely interested in the results. Why don't you apply to get
> > check-in permissions on the per-object-permission
On Mar 22, 5:50 pm, "Matthew Flanagan" <[EMAIL PROTECTED]> wrote:
> I'm definitely interested in the results. Why don't you apply to get
> check-in permissions on the per-object-permissions branch? That way it
> can be accessible to the whole django community.
scussion.
>
> I have been working on a set of apps that absolutely require row level
> permissions. They simply can not meet their intended need without
> this. I could hack something up but instead I am using the per-object-
> permissions branch of django. Because I also want to ke
that should make per-obj-perms
> *much* simpler.
Note: Posting here because it seemed the most appropriate instead of
starting a new discussion.
I have been working on a set of apps that absolutely require row level
permissions. They simply can not meet their intended need without
this. I coul
On 2/8/07, Ramdas S <[EMAIL PROTECTED]> wrote:
> I think Adrian is keeping the trunk upto date. I am using thie updates trunk
> right nowand everything seems to be OK
Except that the per-object permissions branch hasn't had a trunk merge
for over a month. I'd *guess* Adria
I think Adrian is keeping the trunk upto date. I am using thie updates trunk
right nowand everything seems to be OK
Ramdas S
On 2/9/07, Scanner <[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Feb 7, 8:36 pm, "Jay Parlar" <[EMAIL PROTECTED]> wrote:
> > Chris Long was the original maintainer, and he kept
On Feb 7, 8:36 pm, "Jay Parlar" <[EMAIL PROTECTED]> wrote:
> Chris Long was the original maintainer, and he kept doing merges for
> awhile. At this point though, I haven't seen him around these parts in
> months.
>
> Adrian was doing it for awhile after that, but seems to have stopped.
>
> I've
On 2/7/07, Scanner <[EMAIL PROTECTED]> wrote:
> Is someone actively merging in stuff from mainline?
> I emailed the address listed on the wiki page at djangoproject.com
> for the project but either my spam filter ate the response or I have
> not gotten any response.
Chris Long was the original ma
On Feb 7, 2:36 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> I, for one, am keen to see per-object permissions merged into trunk.
> In terms of timelines, it probably won't happen before v1.0, but it is
> definitely on the list of things to do.
>
>
On 2/7/07, Edward Muller <[EMAIL PROTECTED]> wrote:
>
> What happened to the per object permission branches? Are they going
> to be integrated into django?
I, for one, am keen to see per-object permissions merged into trunk.
In terms of timelines, it probably won't happen be
I would like to see these branches merged with the trunk too but lack
sufficient experience with working with trunk/branches.
What are the steps needed to merge the last change from the trunk into
the branches to keep the branches up to date ?
How would you do it ? Start with the patch committed
rovide object level
> > permissions or column level permissions at least.
> >
> > There are two branches which I see being **inactively**. being
> > developed. 1) Per-object-permissions which I feel is stable enough
> > though I have not tried nothing really significa
branches which I see being **inactively**. being
> developed. 1) Per-object-permissions which I feel is stable enough
> though I have not tried nothing really significant on that 2)
> Generic Authorization.
>
> Can someone advise the future of these two branches? Will they be
What happened to the per object permission branches? Are they going
to be integrated into django?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us
Hi,
I am working on something where I need to provide object level permissions
or column level permissions at least.
There are two branches which I see being **inactively**. being developed. 1)
Per-object-permissions which I feel is stable enough though I have not tried
nothing really
35 matches
Mail list logo
