Generating email with activation link. about django-hunger

[joshuakarjala]

The app generates the token automatically - then in the admin you can manually send out the invite to the user.

Or you could use the invitation_code_sent signal to send out the emails automatically.

On 25/02/2012, at 15.32, Harshil Parikh wrote:

Hi,

Does this app generate an email with an activation token once a user submits an email in the invite form? If you have any working examples of how this works, that would be great.

---

Reply to this email directly or view it on GitHub:
#2

[hsparikh]

It seems like there is a hard requirement for a BETA_EMAIL_MODULE & BETA_EMAIL_CONFIRM_FUNCTION in receivers.py to successfully send an email. Sorry for the potentially trivial question, but how would these be configured if I am using standard django email settings such as EMAIL_HOST, EMAIL_PORT, etc.

[yesimon]

i think it would be a good idea if there were some default invite email sending functions. This can be done fairly easily I believe!

[joshuakarjala]

I have added some watered down examples of the email functions I'm currently using.

I'm just using the standard Django email framework to send out these mails.

[yesimon]

Perhaps we can have some sensible defaults for these emails. I saw the commit that you attached but they still rely on a user-defined template mail/<template_name>.txt/html, which might be confusing esp. because there isn't much documentation. Can we have as default an email template with request.get_host() (in the case that they aren't using the sites framework)? I think that would be a sensible default option.

[joshuakarjala]

I prefer to keep the actual emails as templates in the spirit of many other reusable django apps.

But you're welcome to edit the beta_mails.py to include request.get_host() and add default templates to the examples/ folder

On 26/02/2012, at 11.14, Simon Ye wrote:

Perhaps we can have some sensible defaults for these emails. I saw the commit that you attached but they still rely on a user-defined template mail/<template_name>.txt/html, which might be confusing esp. because there isn't much documentation. Can we have as default an email template with request.get_host() (in the case that they aren't using the sites framework)? I think that would be a sensible default option.

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[hsparikh]

Thanks for providing the examples. I am not sure if you are actually implementing them right now, but they don't work right off the bat. Certain changes are necessary (mainly removing the signal parameter) to the receiver functions to get them to work properly.