Re: Registering only folks with .org email

[Kurtis Mullins]

Hey Steve,

There's a number of ways you could go about tackling this task. I, typically, would read the original's application code and first determine how it worked. In some cases, I would write my code to subclass (or re-use) theirs and just make the modifications required. Other times, depending on the complexity of the particular function/feature, I would simply roll my own out based on what I've learned.

Another great way to go about this, since your effort could potentially be something useful to others, is to see if the "registration plugin" is available on github with the proper licensing and then "fork" it. You could make all of your changes there on github and use "pip" to install your copy (the fork you made) instead of the original author's. This would be great because you get to share with others, have a manageable way of monitoring your changes, and may even get some help from others.

Anyways, those are just some ideas... I'm sure others will have more!

Good luck!

- Kurtis

On Fri, Aug 3, 2012 at 3:58 PM, Steve <stvh...@gmail.com> wrote:

I am very new to Django but I like it a lot. I learned about the registration plugin and I am trying to modify it such that only the individuals who have and can validate an email with .org address can register. I was wondering if someone could point me in the right direction in terms of how exactly I should modify the plugin. I am reading the docs and I see some forms for the default strategy. For example, there is one form disallowing the hotmail, gmail, etc. addresses. My strategy would be similar to that. However, since I am new to Django and Python, I don't know how I should modify the app. For ex., should I download a copy and put it in the main project folder? Any best practices and tips would be greatly appreciated.

Steve

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/iaxHEo8NmWoJ.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

[Steve]

Thanks, Kurtis. I'll start with subclassing and see how it goes.

On Friday, August 3, 2012 4:25:46 PM UTC-4, Kurtis wrote:

Hey Steve,

There's a number of ways you could go about tackling this task. I, typically, would read the original's application code and first determine how it worked. In some cases, I would write my code to subclass (or re-use) theirs and just make the modifications required. Other times, depending on the complexity of the particular function/feature, I would simply roll my own out based on what I've learned.

Another great way to go about this, since your effort could potentially be something useful to others, is to see if the "registration plugin" is available on github with the proper licensing and then "fork" it. You could make all of your changes there on github and use "pip" to install your copy (the fork you made) instead of the original author's. This would be great because you get to share with others, have a manageable way of monitoring your changes, and may even get some help from others.

Anyways, those are just some ideas... I'm sure others will have more!

Good luck!

- Kurtis

On Fri, Aug 3, 2012 at 3:58 PM, Steve wrote:

I am very new to Django but I like it a lot. I learned about the registration plugin and I am trying to modify it such that only the individuals who have and can validate an email with .org address can register. I was wondering if someone could point me in the right direction in terms of how exactly I should modify the plugin. I am reading the docs and I see some forms for the default strategy. For example, there is one form disallowing the hotmail, gmail, etc. addresses. My strategy would be similar to that. However, since I am new to Django and Python, I don't know how I should modify the app. For ex., should I download a copy and put it in the main project folder? Any best practices and tips would be greatly appreciated.

Steve

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/iaxHEo8NmWoJ.
To post to this group, send email to django...@googlegroups.com.

To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.