--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/X7YEGB9KJNc/unsubscribe.
To unsubscribe from this group and all its topics, 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/6c8a91c7-dff6-461f-97fb-f63c98f0f1f4%40googlegroups.com.
Petr Dlouhý | vývojář | Auto*Mat, z.s.
Auto*Mat prosazuje lepší prostředí pro kvalitní život ve městě
tel.: (+420) 736 108 424
Bořivojova 108, Praha 3 | www.auto-mat.cz
Chcete lepší podmínky pro život v Praze? www.nakrmteautomat.cz
Přihlaste se k odběru novinek na www.auto-mat.cz/media/zpravodaj
Hi,
+1 for view permission and Petr's rationale
There's one use case where missing the view permission should even be considered a bug: when you have foreign key with the raw id widget, currently the user gets a 403 error in the popup if he doesn't have edit permission on the related model.
Best,
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/CAD4P_OuCj5s0SJgUoyBKpivwN7tdGf4mATpaOYan%3DzhRQG0psw%40mail.gmail.com.