Re: Allauth user fields and userProfile fields save in one registrationform

Usually you would have separated ModelForm child for your User and Profiles: class UserForm(forms.ModelForm): > password = forms.CharField(widget=forms.PasswordInput()) > class Meta: > model = User > fields = ('username', 'email', 'password') > class UserProfileForm(forms.M

Re: Django 1.9 - JSONField

Postgres' jsonb has some pretty unique features that I'm not sure any other databases are going to implement anytime soon, and even if they did, it would probably be in a fairly incompatible way, yeah? It would be nice to get this included into Django itself, and have it noted as a Postgres-only f

[ANNOUNCE] Django security releases issued (1.4.21, 1.7.9, and 1.8.3)

Today the Django team issued multiple releases -- Django 1.4.21, 1.7.9, and 1.8.3 -- as part of our security process. These releases address a couple security issues, and we encourage all users to upgrade as soon as possible. More details can be found on our blog: https://www.djangoproject.com/

Re: Allauth user fields and userProfile fields save in one registrationform

This is a list for discussion of the development _of_ Django, not development _with_ Django. This question is better suited to the django-users list. In general, if you need to edit two models in one form submission, you use two ModelForms... I have a blog post on this topic: http://musings.tinbr

Re: Django 1.9 - JSONField

Sounds good to me, though I think we should wait until there's actually native JSON support in one of the other databases. MariaDB has "dynamic columns" which I think is more similar to Postgres's hstore. On Wednesday, July 8, 2015 at 4:38:42 AM UTC-4, Григорий Крамаренко wrote: > > +1 > I'm wai

Re: Django 1.9 - JSONField

+1 I'm waiting too and hope for a positive decision. вторник, 7 июля 2015 г., 23:57:37 UTC+10 пользователь lza...@ucs.br написал: > > > 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 >

Re: And again about permission to view

I thought of something better: # Add to conf.global_settings.py ... CUSTOM_DEFAULT_PERMISSIONS = () ... # And add in db.models.options.py def get_full_default_permissions():

Re: And again about permission to view

Another variant: # Add to conf.global_settings.py ... AUTH_DEFAULT_PERMISSIONS = ('add', 'change', 'delete') ... # And in db.models.options.py @python_2_unicode_compatible class Options(object): ... def __init__(self, meta, app_label=None): ... self.default_permissions

Re: And again about permission to view

On Wednesday, July 8, 2015 at 6:37:39 AM UTC+2, Григорий Крамаренко wrote: > > "view" absolutly not affect to the admin panel, just as do not affect to > it other custom permissions. > Yes it does and you are completely ignoring the link I sent -- this would be the first one where not having a