Files
notifications-admin/app/templates/views/find-users/find-users-by-email.html
Pea Tyczynska 8258de084c Change part of the tests to use client_request
Two tests retained the old syntax because of mocker conflict:
when logging in as a user through client_request, it sets up a
side_effect on user_api_client.get_user to the user you log in
as. If you later want to set return_value for get_user to
something else, problems start :d.
2018-07-16 15:37:53 +01:00

52 lines
1.3 KiB
HTML

{% extends "views/platform-admin/_base_template.html" %}
{% from "components/page-footer.html" import page_footer %}
{% block per_page_title %}
Find users by email
{% endblock %}
{% block platform_admin_content %}
<h1 class="heading-large">
Find users by email
</h1>
<form
method="post"
action="{{ url_for('.find_users_by_email') }}"
class="grid-row"
>
<div class="column-three-quarters">
{{ textbox(
form.search,
width='1-1',
label='Find users by email, or by partial email'
) }}
</div>
<div class="column-one-quarter align-button-with-textbox">
<input type="hidden" name="csrf_token" value="{{ csrf_token() }}">
<button type="submit" class="button">Search</button>
</div>
</form>
<form id="search-form" method="post">
<input type="hidden" name="csrf_token" value="{{ csrf_token() }}">
</form>
{% if users_found %}
<nav class="browse-list">
<ul>
{% for user in users_found %}
<li class="browse-list-item">
<a href="{{url_for('.user_information', user_id=user.id)}}" class="browse-list-link">{{ user.email_address }}</a>
<p class="browse-list-hint">{{ user.name }}</p>
</li>
<hr>
{% endfor %}
</ul>
</nav>
{% elif users_found == [] %}
<p class="browse-list-hint">No users found.</p>
{% endif %}
{% endblock %}