missing feature, View permission for django admin

[Ander Ustarroz]

I am surprised this feature is not implemented yet, at the moment when we create a new model  three permissions are created automatically for the admin panel:

• add_permission
• change_permission
• delete_permission
  

We really missing the view_permission here, when we want staff to be able to see the content but not being able to modify it. Searching a bit,  you can find many different implementations to achieve this, but all of them are extending django.contrib.admin.ModelAdmin. Having so many people rewriting these methods in my opinion is a clear sign that this feature should be part of the core. 

Regards,

[Tim Graham]

This feature is tracked in https://code.djangoproject.com/ticket/8936. Feel free to review, contribute to, or test the patch if you want to help.

[Olivier Dalang]

Hi,

I worked a bit on this feature lately. I rebased PetrDlouhy's great work (PR 5297) onto master in a new PR 6734.

I think everyone agrees this is a very useful addition to the admin. If we also agree on the implementation; I suggest to merge as soon as possible so that we can benefit from as much testing as possible before release, and more importantly so that third parties have time to adapt their packages (grappelli...).

Please let me know if there's anything more I can do.

I'm really looking forward for this feature, and judging from the frequency this topic is raised on the ml, I'm not the only one ;)

Thanks a lot,

Olivier

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cfe9b399-2486-4dff-97e6-1c3f94b13f65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Graham]

Just to give you my perspective so you don't feel ignored, after the 1.10 release is a better for reviewing and merging larger features than right now.

[Olivier Dalang]

Hi,

As 1.10 is out now, I'd like to draw your attention again on this feature, still hoping to see it merged as soon as possible in the release process so that we get as much testing as possible.

Thanks for all the great work,

Olivier Dalang

To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscribe@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.

Visit this group at https://groups.google.com/group/django-developers.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4c529e2a-4cd3-4930-b532-c0d0a10c05cc%40googlegroups.com.

[Olivier Dalang]

Dear List,

In the meantime, there are two failing builds (default and windows) for the PR.

I can't see what the error is because the links to the build output is a 404 and I wasn't able to setup a working testing environnement yet. Any help would be greatly appreciated to fix the PR !!

I really hope we can have this merged in master soon, so that it can be tested a bit more before release. I'm using it locally (backported to 1.9) and it works well so far, but it's only for a small project with few users.

Thanks,

Olivier