And again about permission to view

I understand that the topic was raised repeatedly. It's hard for me to read all the comments, because I badly know English. And I'm not going to talk about permission to view in the admin. I wrote the ticket , and Tim Graham forwarded me to this mail

Re: And again about permission to view

On Tuesday, July 7, 2015 at 1:30:26 PM UTC+2, Григорий Крамаренко wrote: > > In fact, in versions 1.8 and 1.9 it is enough to simply add this > functionality without prejudice to existing and new projects. Simple patch >

Re: And again about permission to view

Since the existing permissions are used in the admin, I don't think adding a view permission that has no effect there would be very intuitive. For projects that do want another permission such as "view" on all its models, I guess an easy way to do that could be useful. On Tuesday, July 7, 2015

Django 1.9 - JSONField

Hi all, I'd like to know why this feature will be only available on postgres and not as a Field for any database, like this product? This Field would be very usefull for many users I think. https://github.com/bradjasper/django-jsonfield https://docs.djangoproject.com/en/dev/releases/1.9/#djan

Re: Django 1.9 - JSONField

The django-contrib-postgres JSONField takes advantage of JSON being a native type that allows it's data fields to be used by the ORM, instead of just a text field that wraps json.dumps() and json.loads(). All of the core supported backends seem to have some flavor of native JSON support (MS SQL is

Re: And again about permission to view

Let's get into the admin to check only three permissions in has_module_permissions. вторник, 7 июля 2015 г., 23:23:12 UTC+10 пользователь Tim Graham написал: > > Since the existing permissions are used in the admin, I don't think adding > a view permission that has no effect there would be very

Re: And again about permission to view

I look in the code admin.options.BaseModelAdmin.has_module_permission, who regulates access to the admin. Now any custom permission automatically makes read access to the admin area. So? среда, 8 июля 2015 г., 0:48:00 UTC+10 пользователь Григорий Крамаренко написал: > > Let's get into the admin

Re: And again about permission to view

I'm specifically tested with the admin panel. 1. while not included is_staff the user cannot log in admin panel 2. even if you include is_staff and all permissions to view, he still doesn't see anything until he does not has one from next permissions: add/change/delete. So, as I said at the begi

Re: Django 1.9 - JSONField

Agreed, as other databases catch up with the feature set offered in contrib.postgres I think moving this field into core is likely - it's a field that a number of databases are working on adding. It's worth noting that the PG implementation is 9.4+ only, the 9.2/9.3 implementation of json should no

Re: And again about permission to view

On Tuesday, July 7, 2015 at 5:25:38 PM UTC+2, Григорий Крамаренко wrote: > > So, as I said at the beginning - this change does not affect the admin > panel. > It absolutely does, cause if you assign the "view" permission to a user he should be able to see the changelist, which wouldn't be the

Allauth user fields and userProfile fields save in one registrationform

Hi All Can someone point me in the right direction. On registration I would like to fill in the UserFields(Username-password etc) and the ProfileFields (City, phonenumber etc) and save theme both in the models User and UserProfile Need i to expaned the sigupform or put two form on one page a

Re: And again about permission to view

Whether I don't understand you, or you me. Permissions in the admin work on the principle of: access = is_stuff and True in (add_perm, change_perm, delete_perm) "view" absolutly not affect to the admin panel, just as do not affect to it other custom permissions. Take a look at this permission a

Re: And again about permission to view

A general can_view permission not respected by the admin is not a good idea. However an easy way to add a general permission to every model in the system in one go would be interesting - a hook into https://github.com/django/django/blob/7da3923ba0c569aa23d0ab0a47a124af60a18f5b/django/contrib/auth/