Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/confirmation/confirm.html

24 lines
674 B
HTML
Raw Normal View History

Rename content_base.html -> portico.html (imported from commit 556fb5aeca76eb186013a28da9bab77c1e56d700)
2012-10-16 05:46:57 +02:00
{% extends "zephyr/portico.html" %}
Implement confirmation for new user signups. We add a few templates for django-confirmation. We define a "PreregistrationForm" which is validated by accounts_home, which then generates a confirmation object and emails the user. This required creating a new table for a PreregistrationUser with an email and status (confirmed) field. The register function now no longer accepts a "email" field in the form and deals only with confirmation IDs to determine the email used to sign up a user. (imported from commit 4fcde04530aa7ad4de84579668daee7290b424ac)
2012-09-28 22:47:05 +02:00
Rename more_content -> portico_content (imported from commit 4a3df508bb0227e998115eeff24b789dd8b42698)
2012-10-16 05:49:53 +02:00
{% block portico_content %}
Implement confirmation for new user signups. We add a few templates for django-confirmation. We define a "PreregistrationForm" which is validated by accounts_home, which then generates a confirmation object and emails the user. This required creating a new table for a PreregistrationUser with an email and status (confirmed) field. The register function now no longer accepts a "email" field in the form and deals only with confirmation IDs to determine the email used to sign up a user. (imported from commit 4fcde04530aa7ad4de84579668daee7290b424ac)
2012-09-28 22:47:05 +02:00
<div class="pitch">
<hr/>
{% if confirmed %}
<p>You're confirmed. We're not exactly sure what we confirmed you for, but whatever it is you're totally good.</p>
{% else %}
Wrap extremely long lines in HTML (imported from commit 4a18013ae001223709d91b7433128f8e75ebf399)
2012-10-25 06:09:28 +02:00
Implement confirmation for new user signups. We add a few templates for django-confirmation. We define a "PreregistrationForm" which is validated by accounts_home, which then generates a confirmation object and emails the user. This required creating a new table for a PreregistrationUser with an email and status (confirmed) field. The register function now no longer accepts a "email" field in the form and deals only with confirmation IDs to determine the email used to sign up a user. (imported from commit 4fcde04530aa7ad4de84579668daee7290b424ac)
2012-09-28 22:47:05 +02:00
<p class="lead">Whoops, something's not right. We couldn't find your confirmation ID!<p>
Wrap extremely long lines in HTML (imported from commit 4a18013ae001223709d91b7433128f8e75ebf399)
2012-10-25 06:09:28 +02:00
<p>Make sure you copied the link correctly in to your browser. If you're
still encountering this page, its probably our fault. We're sorry.<p>
<p>Anyway, shoot us a line at <a
href="mailto:support@humbughq.com">support@humbughq.com</a> and we'll get
this resolved shortly.</p>
Implement confirmation for new user signups. We add a few templates for django-confirmation. We define a "PreregistrationForm" which is validated by accounts_home, which then generates a confirmation object and emails the user. This required creating a new table for a PreregistrationUser with an email and status (confirmed) field. The register function now no longer accepts a "email" field in the form and deals only with confirmation IDs to determine the email used to sign up a user. (imported from commit 4fcde04530aa7ad4de84579668daee7290b424ac)
2012-09-28 22:47:05 +02:00
{% endif %}
</div>
{% endblock %}