Any interest in a multi email field in django?
JJ Zolper
Lachlan Musicman
easily extensible - giving you or others the opportunity to extend it
as you see fit and to release it the world as fle has.
See here:
https://docs.djangoproject.com/en/1.7/topics/auth/customizing/#extending-the-existing-user-model
cheers
L.
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users...@googlegroups.com.
> To post to this group, send email to django...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/c206b3ed-c434-456d-b978-b7fe67c8d0bd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You have to be really clever to come up with a genuinely dangerous
thought. I am disheartened that people can be clever enough to do that
and not clever enough to do the obvious thing and KEEP THEIR IDIOT
MOUTHS SHUT about it, because it is much more important to sound
intelligent when talking to your friends.
This post was STUPID.
-----------------------------------------------------------------------------------------------------------
The Most Terrifying Thought Experiment of All Time
http://www.slate.com/articles/technology/bitwise/2014/07/roko_s_basilisk_the_most_terrifying_thought_experiment_of_all_time.html
Carl Meyer
best implementation. It is better to have a linked table of email
addresses with a ForeignKey to User (or perhaps an ArrayField, if you're
using Postgres, which will soon be built-in.)
Carl
JJ Zolper
# Athlete User
class Athlete(models.Model):
athleteuser = models.OneToOneField(User)
athleteavatar = models.ImageField("Profile Pic", upload_to="images/", blank=True, null=True, default='images/default/no-img.jpg')
athletebirthday = models.DateField(blank=True, null=True)
athleteurl = models.CharField(max_length=30, unique=True, blank=True) # Must limit to a-z && A-Z && and 0-9 chars, validators=[validate_slug]
athletelanguage = models.CharField(max_length=15, blank=True)
athletecommunities = models.ManyToManyField('communities.Community', blank=True, null=True)
athletecolleges = models.ManyToManyField('colleges.College', blank=True, null=True)
athletetwitterscreenname = models.CharField(max_length=30, blank=True)
isVerified = models.BooleanField(default=False)
User.profile = property(lambda u: Athlete.objects.get_or_create(athleteuser=u)[0])
Certainly because Django is so flexible a multi email field doesn't have to be native but I was more just getting a feel for any interest that others might have in having this capability available. To me it is a very standard use case, and again to me off the top of my head my opinion is that something that solves this use case could be a standard feature that is shipped, that's really all this is about.
For the time being I am trying basically your route and am doing things as an extension of what already exists.
Thanks a lot,
JJ
JJ Zolper
# Athlete Email
class AthleteEmail(models.Model):
athlete = models.ForeignKey(Athlete)
email = models.EmailField(unique=True)
verified = models.BooleanField(default=False)
This way basically any athlete which is the "profile" user extension wants to add an email they can in this way as this email object is FK'ed to their profile. Also, then once they verify an email the boolean there is flipped to true.
The next step to me at least is to then build a form from a modelform of the above and then render this in a view so the form:
class AthleteProfileEmailUpdateForm(ModelForm):
athleteemail = forms.EmailField(label=(u'Athlete Email Address:'))
class Meta:
model = AthleteEmail
exclude = ('athlete', 'verified',)
fields = ['email',]
At this point I'm not sure though, let me try to explain. For example on my profile module:
# Athlete User
class Athlete(models.Model):
athleteuser = models.OneToOneField(User)
athleteavatar = models.ImageField("Profile Pic", upload_to="images/", blank=True, null=True, default='images/default/no-img.jpg')
athletebirthday = models.DateField(blank=True, null=True)
athleteurl = models.CharField(max_length=30, unique=True, blank=True) # Must limit to a-z && A-Z && and 0-9 chars, validators=[validate_slug]
athletelanguage = models.CharField(max_length=15, blank=True)
athletecommunities = models.ManyToManyField('communities.Community', blank=True, null=True)
athletecolleges = models.ManyToManyField('colleges.College', blank=True, null=True)
athletetwitterscreenname = models.CharField(max_length=30, blank=True)
isVerified = models.BooleanField(default=False)
User.profile = property(lambda u: Athlete.objects.get_or_create(athleteuser=u)[0])
You can see this line: User.profile = property(lambda u: Athlete.objects.get_or_create(athleteuser=u)[0])
then the form:
# Athlete Update Profile Form
class AthleteProfileUpdateForm(ModelForm):
athleteavatar = forms.ImageField(label=(u'Athlete Avatar:'))
athletebirthday = forms.CharField(label=(u'Athlete Birthday:'))
athleteurl = forms.CharField(label=(u'Athlete Url:'))
#athletecommunities = forms.MultipleChoiceField(label=(u'Athlete Communities:'), widget=forms.CheckboxSelectMultiple, required=False, choices=ATHLETECOMMUNITIESCHOICES)
class Meta:
model = Athlete
exclude = ('athleteuser',)
fields = ['athleteavatar', 'athletebirthday', 'athleteurl', 'athletecommunities']
which then allows me in a view to:
athleteprofile = AthleteProfileUpdateForm(instance = profile)
thereby displaying a form with the already submitted contents in the form. However, I'm not sure how to do this with my current situation. I would assume a similar approach so basically collecting all the email objects and more specifically the email fields within that object that relates to the current or logged in user profile and then for looping over those items in a form. To me that would be the way that then I could dynamically show them all emails they have and allow them to edit them. I believe if I could implement this I could figure out how to do the rest that I need.
Do you have any ideas?
Thanks so much!
JJ
Lachlan Musicman
And I probably could have been less gruff.
What I was trying to say was, as someone that's been hanging in these
parts for a few years now, I can tell you that it is unlikely the devs
would introduce it to standard Django. That's why the BaseUser is so
base - it's specifically designed to be extenisble and easily
replaced, and that type of functionality - and you are very right here
- is probably needed by many, but not by every. And as such, is a
perfect candidate for an app or extension rather than inclusion in the
base. See Django Debug toolbar, or REST frame work or model-utils or
any number of other very useful apps - essential and invaluable for
some, not needed by all.
On another note, FYI there is an URLField that could be used on athleteurl
https://docs.djangoproject.com/en/1.7/ref/models/fields/#urlfield
or you could just create a slug per Athlete and then refer to each
Athlete by the get_absolute_url function? (I don't know if you've done
this and rejected it - but it's what I'd do straight up).
https://docs.djangoproject.com/en/1.7/ref/models/instances/#get-absolute-url
cheers
L.
Carl Meyer
To make a form for users to add/remove emails with a linked model
approach, you'll need an inline model formset:
https://docs.djangoproject.com/en/dev/topics/forms/modelforms/#inline-formsets
Carl
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-users...@googlegroups.com
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/django-users/46257514-13d8-4a7e-ad34-2595d102fe7d%40googlegroups.com?utm_medium=email&utm_source=footer>.
JJ Zolper
JJ Zolper
Lachlan Musicman
your mind. Makes everything easier.
L.
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users...@googlegroups.com.
> To post to this group, send email to django...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit