ok this is my last message, i swear!
i've created a new options.py file and a .diff, and i've attached it
to the ticket you send to me.
i've tested it and it works, it's pretty basic and there is more work
to do.
what i've done is to add a method has_view_permission, and check a
view permi
fine i'll keep in mind.
On 16 Nov, 22:17, Aymeric Augustin
wrote:
> Hi Ric,
>
> I've noticed that you're posting a lot on this mailing list. Please remember
> that each email sent here is broadcasted to around 7000 people, each of whom
> will need a few seconds to decide if it's interesting.
>
Hi Ric,
I've noticed that you're posting a lot on this mailing list. Please remember
that each email sent here is broadcasted to around 7000 people, each of whom
will need a few seconds to decide if it's interesting.
You're expected to do some research and to structure your thoughts and
questi
at a first look, the big file to patch is django.contrib.admin.options
i need also to add a method to django.db.models.options
def get_view_permission(self):
return 'view_%s' % self.object_name.lower()
so maybe it's better to work only on options.py and make a .diff,
right?
On 16 Nov, 20:43
ok i can give a try...
maybe it's difficult, not to much. i have to see inline models, and
give the right behavior
so from github i can fork django 1.3.1, but actually i'm working with
the latest version.
should i fork the lastest?
On 16 Nov, 20:21, Aymeric Augustin
wrote:
> Hi Ric,
>
> Th
Hi Ric,
This feature request is quite common, and it's tracked here:
https://code.djangoproject.com/ticket/8936
A few people talked to me since I wrote the GSoC project description linked in
comment #5, but I don't think anyone is actively working on this.
Since we deprecated databrowse, the p
yes i would use it too, because i've got a lot of models with a view
permission to the final user but with no change permission.
it could be archived with backward compatibility, because by default a
user has got no view permission
view permission can be added with a syncdb, and user must add them
I would benefit from this. With administration systems I build with Django I
generally have to add my own 'view_foo' permission to each model. +1
On 17/11/2011, at 2:47 AM, Ric wrote:
> i've been thinking about a new django admin feature, that could be
> backward implemented
>
> it's about addi
i've been thinking about a new django admin feature, that could be
backward implemented
it's about adding a view permission for models
so we can have
1.change_permission
2.delete_permission
3.add_permission
and
4.view_permission
in the changelist_view view_permission allow user to see the
chang
