-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deprecate EMAIL_CONFIRM_LA_HTTP_PROTOCOL and EMAIL_CONFIRM_LA_DOMAIN #20
Comments
EMAIL_CONFIRM_LA_DOMAIN can be omitted and Site.objects.get_current().domain will be used ? Omitted : EMAIL_CONFIRM_LA_HTTP_PROTOCOL = 'http' and send email: http://example.com/email_confirmation/key/57c3bf1f5d174e8cb7ad8a7f52caf537/ no have using my bd django sites,But it uses the default value. |
I'm planning to do: Remove those two settings:
Explicitly specify Make |
Although the README says
That is actually not happening. This caused us great trouble. Any plans to fix that? |
If you add in the code and in the documentation, a migrate for the user to
set your domain. Because the problem is that when using the default it uses
the default of django itself which is www.example.com
2017-03-27 12:55 GMT+00:00 Carlos de la Torre <[email protected]>:
… Although the README says
If you are using the sites framework, then EMAIL_CONFIRM_LA_DOMAIN can be
omitted and Site.objects.get_current().domain will be used.
That is actually not happening. This caused us great trouble.
Any plans to fix that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHTZm1GQtJz8Yf7fC7MRfOpbd9vfNcozks5rp7GmgaJpZM4JU9-3>
.
--
João Pedro Cardoso
*http://lattes.cnpq.br/3682402342405212
<http://lattes.cnpq.br/3682402342405212>*
*"*As pessoas não sabem o que querem, até mostrarmos a ela.*"**Steve Jobs*
|
What you propose does not work. We are using version 2.3.0 |
We should use
EMAIL_CONFIRM_LA_TEMPLATE_CONTEXT
instead.The text was updated successfully, but these errors were encountered: