Lancaster-University/DEMOS2
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
This repository has been archived on 2022-08-01. You can view files and clone it, but cannot push or open issues or pull requests.
DEMOS2/allauthdemo/templates/polls/create_event.html

763 lines
54 KiB
HTML
Raw Normal View History

Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
{% extends "bases/bootstrap-with-nav.html" %}
{% load staticfiles %}
{% load bootstrap3 %}
{% block content %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<script type="text/javascript">
// This events list is generated for later input validation
var events_list = [
{% for event in events %}
{% if not forloop.first %},{% endif %}
{
title: "{{ event.title }}",
Updated the voting and event decryption pages. On the voting page, added the ability to vote by selecting checkboxes instead of a drop down select menu. This adds flexibility at event creation to specify a wide range of min and max option selections for polls. On the event decryption page, SK validation was added based on the stored trustee PK as well as a dialog to display any validation errors. Most of the updates took place behind the scenes at the backend.
2018-07-13 16:19:35 +00:00
slug: "{{ event.EID_hr }}"
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
}
{% endfor %}
];
// This list of demo user emails will be used for input validation
var user_emails = [
{% for user in demo_users %}
{% if not forloop.first %},{% endif %}
{
email: "{{ user.email }}"
}
{% endfor %}
];
General housekeeping such as adding package.json for Node server, bash script for launching a celery worker and updating the readme to assist with launching the DEMOS2 app. Updated some models to include UI helper functions. Main work done is around event preparation - with a Celery worker running and the Node server, trustees are now emailed a link to prepare events. The event detail page has also had a bit of an overhaul to include additional information and to make it easier to use
2018-07-02 09:06:05 +00:00
{% if invalid_fields.poll_count %}pollCount = {{ invalid_fields.poll_count.val }};{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</script>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<!-- The following UI was ported from the Election Authority UI in DEMOS1 by Vincent de Almeida -->
<!-- The DEMOS1 repository can be found at: https://github.com/mlevogiannis/demos-voting -->
General housekeeping such as adding package.json for Node server, bash script for launching a celery worker and updating the readme to assist with launching the DEMOS2 app. Updated some models to include UI helper functions. Main work done is around event preparation - with a Celery worker running and the Node server, trustees are now emailed a link to prepare events. The event detail page has also had a bit of an overhaul to include additional information and to make it easier to use
2018-07-02 09:06:05 +00:00
<!-- TODO: look into i18n translations as this was a feature implemented in DEMOS1 to enable automatic translations -->
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<div class="container">
Updated the voting and event decryption pages. On the voting page, added the ability to vote by selecting checkboxes instead of a drop down select menu. This adds flexibility at event creation to specify a wide range of min and max option selections for polls. On the event decryption page, SK validation was added based on the stored trustee PK as well as a dialog to display any validation errors. Most of the updates took place behind the scenes at the backend.
2018-07-13 16:19:35 +00:00
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<div class="page-header">
<h2>Create New Event with Polls</h2>
</div>
<div class="row">
<div class="col-xs-12">
<form id="election-form" class="form-horizontal" method="POST" novalidate>
{% csrf_token %}
<!-- TODO: Have not imported the if form not valid template code as this needs further investigating -->
<!-- Name -->
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<div class="form-group">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<label for="name-input" class="col-sm-3 col-md-2 control-label">Name:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<input type="text" class="form-control input-control" id="name-input" placeholder="Example: EU Election" name="name-input" maxlength="255" {% if invalid_fields %}value="{{ invalid_fields.event_name_data.val }}"{% endif %}>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="name-input-hint-block" class="help-block">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
A short and clear name.
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
<span id="name-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.event_name %}{{ invalid_fields.event_name.error }}{% endif %}
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</span>
</div>
</div>
<!-- Slug / Identifier -->
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<div class="form-group">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<label for="identifier-input" class="col-sm-3 col-md-2 control-label">Identifier:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<input type="text" class="form-control input-control" id="identifier-input" placeholder="Example: eu-election" name="identifier-input" maxlength="255" {% if invalid_fields %}value="{{ invalid_fields.identifier_data.val }}"{% endif %}>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<span id="identifier-input-help-block" class="help-block">
Used in the election URL, it must only consist of letters, numbers, underscores or hyphens; no whitespace is permitted.
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
<span id="identifier-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.identifier %}{{ invalid_fields.identifier.error }}{% endif %}
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</span>
</div>
</div>
<!-- Voting start time -->
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<div class="form-group ">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<label for="vote-start-input" class="col-sm-3 col-md-2 control-label">Voting starts at:</label>
<div class="col-sm-9 col-md-10">
<div class="input-group date">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<input type="text" class="form-control input-control" data-date-format="YYYY-MM-DD H:mm Z" id="vote-start-input" name="vote-start-input" {% if invalid_fields %}value="{{ invalid_fields.starts_at_data.val }}"{% endif %}>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<span class="input-group-addon btn">
<i class="fa fa-calendar" aria-hidden="true"></i>
/
<i class="fa fa-clock-o" aria-hidden="true"></i>
</span>
</div>
<span id="vote-start-input-help-block" class="help-block">
Laid the ground work for client-side input validation by setting up a fn that's triggered before the form is submitted. The vote start and end date time is now being validated both server side and client side and now includes UTC offsets
2018-06-13 12:01:55 +00:00
Date and time when registered voters can commence voting. This includes the UTC offset starting with '+'.
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</span>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="vote-start-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.starts_at %}{{ invalid_fields.starts_at.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
<!-- Voting end time -->
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<div class="form-group ">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<label for="vote-end-input" class="col-sm-3 col-md-2 control-label">Voting ends at:</label>
<div class="col-sm-9 col-md-10">
<div class="input-group date">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<input type="text" class="form-control input-control" data-date-format="YYYY-MM-DD H:mm Z" id="vote-end-input" name="vote-end-input" {% if invalid_fields %}value="{{ invalid_fields.ends_at_data.val }}"{% endif %}>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<span class="input-group-addon btn">
<i class="fa fa-calendar" aria-hidden="true"></i>
/
<i class="fa fa-clock-o" aria-hidden="true"></i>
</span>
</div>
<span id="vote-end-input-help-block" class="help-block">
Laid the ground work for client-side input validation by setting up a fn that's triggered before the form is submitted. The vote start and end date time is now being validated both server side and client side and now includes UTC offsets
2018-06-13 12:01:55 +00:00
Date and time when registered voters can no longer vote. This includes the UTC offset starting with '+'.
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</span>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="vote-end-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.ends_at %}{{ invalid_fields.ends_at.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<span id="event-timings-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.event_timings %}{{ invalid_fields.event_timings.error }}{% endif %}
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
<!-- Questions -->
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<div class="form-group">
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
<label for="questions-input" class="col-sm-3 col-md-2 control-label">Polls:</label> <!-- This text can be a template variable -->
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<div class="col-sm-9 col-md-10">
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<div class="form-group">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<table id="polls-input-table" class="table table-hover">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<thead>
<tr>
<th class="text-center">#</th>
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
<th>Question / Statement</th>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<th class="text-center">Actions</th>
</tr>
</thead>
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<tbody class="formset questions-formset" data-formset-prefix="polls" data-formset-type="modal" data-formset-modal-title="Add a New Poll">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields %}
{% for poll in invalid_fields.polls_data.val %}
<!-- Poll -->
<tr class="formset-form" data-formset-form-prefix="poll">
<!-- # -->
<td class="formset-form-index text-center" scope=row>
{{ forloop.counter }}
</td>
<!-- Question / Statement Label -->
<th class="formset-form-name">
{{ poll.name.val }}
</th>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-edit" aria-label="Edit">
<i class="fa fa-pencil-square-o" aria-hidden="true"></i>
</button>
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
<td class="hidden">
<div class="formset-form-fields">
<!-- Name -->
<div class="form-group dialogFormField">
<label for="question-name-input">Question / Statement</label>
<input type="text" class="form-control dialogQ" id="question-name-input-{{ poll.no.val }}" name="question-name-input-{{ poll.no.val }}" placeholder="Example: Elections for the European Parliament" maxlength="200" value="{{ poll.name.val }}">
<span id="question-name-input-help-block" class="help-block">
Question / Statement that will be put forward to voters along with the below options.
</span>
<span id="question-input-error-block-{{ poll.no.val }}" class="help-block errorText">
<!-- Errors flagged here -->
{% if poll.errors.val.name %}{{ poll.errors.val.name.val }}{% endif %}
</span>
</div>
<!-- Options -->
<div class="form-group dialogFormField">
<label for="options-table">Options</label>
<table id="options-table" class="table table-hover">
<thead>
<tr>
<th class="text-center">#</th>
<th>Option</th>
<th class="text-center">Actions</th>
</tr>
</thead>
<tbody id="sort" class="formset option-formset" data-formset-prefix="options" data-formset-type="inline">
{% for option in poll.options.val %}
<!-- Option -->
<tr class="formset-form sorting-row" data-formset-form-prefix="option">
<!-- # -->
<th class="formset-form-index text-center" scope=row>
{{ forloop.counter }}
</th>
<!-- Option Label -->
<td>
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control dialogO" placeholder="Example: Candidate 1" id="option-name-input-{{ poll.no.val }}" name="option-name-input-{{ poll.no.val }}" maxlength="200" value="{{ option }}">
</div>
</td>
<!-- Delete Action -->
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% endfor %}
<!-- Option: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="option">
<!-- # -->
<th class="formset-form-index text-center" scope=row>
X
</th>
<!-- Option Label -->
<td>
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control dialogO" placeholder="Example: Candidate X" id="option-name-input-{{ poll.no.val }}" name="option-name-input-{{ poll.no.val }}" maxlength="200">
</div>
</td>
<!-- Delete Action -->
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
</tbody>
</table>
<div class="clearfix">
<button type="button" class="btn btn-primary formset-add" data-formset-prefix="options">
<span class="glyphicon glyphicon-plus" aria-hidden="true"></span>
Add Poll Option
</button>
</div>
<span id="question-input-help-block" class="help-block">
Drag and drop to re-order options.
</span>
<span id="options-input-error-block-{{ poll.no.val }}" class="help-block errorText">
<!-- Errors flagged here -->
{% if poll.errors.val.options %}{{ poll.errors.val.options.val }}{% endif %}
</span>
</div>
<!-- Number of option selections -->
<div class="form-group dialogFormField">
<label for="selections-input" class="control-label">Number of Selections:</label> <!-- This text can be a template variable -->
<div class="row">
<div class="col-xs-6">
<label class="sr-only" for="minimum-input">Minimum</label>
<input type="number" class="form-control min-input" id="minimum-input-{{ poll.no.val }}" placeholder="Minimum" value="{{ poll.min_selection.val }}" name="minimum-input-{{ poll.no.val }}" min="0" max="{{ poll.options.val.length }}"> <!-- Max is the default number of options initially displayed (2) -->
</div>
<div class="col-xs-6">
<label class="sr-only" for="maximum-input">Maximum</label>
<input type="number" class="form-control max-input" id="maximum-input-{{ poll.no.val }}" placeholder="Maximum" value="{{ poll.max_selection.val }}" name="maximum-input-{{ poll.no.val }}" min="1" max="{{ poll.options.val.length }}"> <!-- Max is the default number of options initially displayed (2) -->
</div>
</div>
<span id="question-input-help-block" class="help-block">
Minimum and maximum number of option selections that a voter can make for the specified question / statement.
</span>
<span id="selections-input-error-block-{{ poll.no.val }}" class="help-block errorText">
<!-- Errors flagged here -->
{% if poll.errors.val.min_max %}{{ poll.errors.val.min_max.val }}{% endif %}
</span>
</div>
</div>
</td>
</tr>
{% endfor %}
{% else %}
<!-- Poll -->
<tr class="formset-form formset-form-empty hidden" data-formset-form-prefix="poll">
<!-- # -->
<td class="formset-form-index text-center" scope=row>
1
</td>
<!-- Question / Statement Label -->
<th class="formset-form-name">
<!-- Q Label Goes Here -->
</th>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-edit" aria-label="Edit">
<i class="fa fa-pencil-square-o" aria-hidden="true"></i>
</button>
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
<td class="hidden">
<div class="formset-form-fields">
<!-- Name -->
<div class="form-group dialogFormField">
<label for="question-name-input">Question / Statement</label>
<input type="text" class="form-control dialogQ" id="question-name-input" name="question-name-input" placeholder="Example: Elections for the European Parliament" maxlength="200">
<span id="question-name-input-help-block" class="help-block">
Question / Statement that will be put forward to voters along with the below options.
</span>
<span id="question-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
</span>
</div>
<!-- Options -->
<div class="form-group dialogFormField">
<label for="options-table">Options</label>
<table id="options-table" class="table table-hover">
<thead>
<tr>
<th class="text-center">#</th>
<th>Option</th>
<th class="text-center">Actions</th>
</tr>
</thead>
<tbody id="sort" class="formset option-formset" data-formset-prefix="options" data-formset-type="inline">
<!-- Option -->
<tr class="formset-form sorting-row" data-formset-form-prefix="option">
<!-- # -->
<th class="formset-form-index text-center" scope=row>
1
</th>
<!-- Option Label -->
<td>
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control dialogO" placeholder="Example: Candidate 1" id="option-name-input" name="option-name-input" maxlength="200">
</div>
</td>
<!-- Delete Action -->
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Option -->
<tr class="formset-form sorting-row" data-formset-form-prefix="option">
<!-- # -->
<th class="formset-form-index text-center" scope=row>
2
</th>
<!-- Option Label -->
<td>
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control dialogO" placeholder="Example: Candidate 2" id="option-name-input" name="option-name-input" maxlength="200">
</div>
</td>
<!-- Delete Action -->
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Option: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="option">
<!-- # -->
<th class="formset-form-index text-center" scope=row>
X
</th>
<!-- Option Label -->
<td>
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control dialogO" placeholder="Example: Candidate X" id="option-name-input" name="option-name-input" maxlength="200">
</div>
</td>
<!-- Delete Action -->
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
</tbody>
</table>
<div class="clearfix">
<button type="button" class="btn btn-primary formset-add" data-formset-prefix="options">
<span class="glyphicon glyphicon-plus" aria-hidden="true"></span>
Add Poll Option
</button>
</div>
<span id="question-input-help-block" class="help-block">
Drag and drop to re-order options.
</span>
<span id="options-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
</span>
</div>
<!-- Number of option selections -->
<div class="form-group dialogFormField">
<label for="selections-input" class="control-label">Number of Selections:</label> <!-- This text can be a template variable -->
<div class="row">
<div class="col-xs-6">
<label class="sr-only" for="minimum-input">Minimum</label>
<input type="number" class="form-control min-input" id="minimum-input" placeholder="Minimum" value="" name="minimum-input" min="0" max="2"> <!-- Max is the default number of options initially displayed (2) -->
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
</div>
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<div class="col-xs-6">
<label class="sr-only" for="maximum-input">Maximum</label>
<input type="number" class="form-control max-input" id="maximum-input" placeholder="Maximum" value="" name="maximum-input" min="1" max="2"> <!-- Max is the default number of options initially displayed (2) -->
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
</div>
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
</div>
<span id="question-input-help-block" class="help-block">
Minimum and maximum number of option selections that a voter can make for the specified question / statement.
</span>
<span id="selections-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
</span>
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
</div>
</div>
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
</td>
</tr>
{% endif %}
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</tbody>
</table>
<div class="clearfix">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<button type="button" class="btn btn-primary formset-add" data-formset-prefix="polls">
<span class="glyphicon glyphicon-plus" aria-hidden="true"></span>
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
Add Poll
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</button>
</div>
<span id="question-input-help-block" class="help-block">
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
Drag and drop to re-order polls.
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</span>
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<span id="polls-input-error-block" class="help-block errorText">
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.polls_errors %}{{ invalid_fields.polls_errors.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
</div>
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<!-- { Hidden field: Number of Polls } -->
General housekeeping such as adding package.json for Node server, bash script for launching a celery worker and updating the readme to assist with launching the DEMOS2 app. Updated some models to include UI helper functions. Main work done is around event preparation - with a Celery worker running and the Node server, trustees are now emailed a link to prepare events. The event detail page has also had a bit of an overhaul to include additional information and to make it easier to use
2018-07-02 09:06:05 +00:00
<input type="number" id="poll-count-input" name="poll-count-input" class="hidden" {% if invalid_fields.poll_count %}value="{{ invalid_fields.poll_count.val }}"{% endif %}>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<!-- Organisers -->
<div class="form-group">
<label for="organisers-input" class="col-sm-3 col-md-2 control-label">Organisers:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
<div class="form-group">
<table id="organisers-input-table" class="table table-hover">
<thead>
<tr>
<th class="text-center">#</th>
<th>Email</th>
<th class="text-center">Actions</th>
</tr>
</thead>
<tbody class="formset organiser-formset" data-formset-prefix="organisers" data-formset-type="inline">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields %}
{% for organiser in invalid_fields.organiser_emails_data.val %}
<!-- Organiser -->
<tr class="formset-form sorting-row" data-formset-form-prefix="organiser">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
{{ forloop.counter }}
</th>
<td>
<!-- Email -->
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: organiser@example.com" id="organiser-email-input" name="organiser-email-input" value="{{ organiser }}" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<!-- Action -->
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% endfor %}
<!-- Organiser: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="organiser">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
X
</th>
<td>
<!-- Email -->
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: organiserX@example.com" id="organiser-email-input" name="organiser-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% else %}
<!-- Organiser -->
<tr class="formset-form sorting-row" data-formset-form-prefix="organiser">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
1
</th>
<td>
<!-- Email -->
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: organiser@example.com" id="organiser-email-input" name="organiser-email-input" value="{{ user_email }}" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<!-- Action -->
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Organiser -->
<tr class="formset-form sorting-row" data-formset-form-prefix="organiser">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
2
</th>
<td>
<!-- Email -->
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: organiser@example.com" id="organiser-email-input" name="organiser-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Organiser: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="organiser">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
X
</th>
<td>
<!-- Email -->
<div>
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: organiserX@example.com" id="organiser-email-input" name="organiser-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% endif %}
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</tbody>
</table>
<div class="clearfix">
<button type="button" class="btn btn-primary formset-add" data-formset-prefix="organisers">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<span class="glyphicon glyphicon-plus" aria-hidden="true"></span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
Add Organiser Email
</button>
</div>
<span id="question-input-help-block" class="help-block">
Drag and drop to re-order emails.
</span>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="organisers-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.organiser_emails %}{{ invalid_fields.organiser_emails.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
</div>
<!-- Trustees -->
<div class="form-group">
<label for="trustees-input" class="col-sm-3 col-md-2 control-label">Trustees:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
<div class="form-group">
<table id="trustees-input-table" class="table table-hover">
<thead>
<tr>
<th class="text-center">#</th>
<th>Email</th>
<th class="text-center">Actions</th>
</tr>
</thead>
<tbody class="formset trustee-formset" data-formset-prefix="trustees" data-formset-type="inline">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields %}
{% for trustee in invalid_fields.trustee_emails_data.val %}
<!-- Trustee -->
<tr class="formset-form sorting-row" data-formset-form-prefix="trustee">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
{{ forloop.counter }}
</th>
<td>
<!-- Email -->
<div> <!-- Has error conditional class removed -->
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: trustee@example.com" id="trustee-email-input" name="trustee-email-input" value="{{ trustee }}" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<!-- Action -->
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% endfor %}
<!-- Trustee: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="trustee">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
X
</th>
<td>
<!-- Email -->
<div> <!-- Has error conditional class removed -->
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: trusteeX@example.com" id="trustee-email-input" name="trustee-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% else %}
<!-- Trustee -->
<tr class="formset-form sorting-row" data-formset-form-prefix="trustee">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
1
</th>
<td>
<!-- Email -->
<div> <!-- Has error conditional class removed -->
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: trustee@example.com" id="trustee-email-input" name="trustee-email-input" value="{{ user_email }}" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<!-- Action -->
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Trustee -->
<tr class="formset-form sorting-row" data-formset-form-prefix="trustee">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
2
</th>
<td>
<!-- Email -->
<div> <!-- Has error conditional class removed -->
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: trustee@example.com" id="trustee-email-input" name="trustee-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
<!-- Trustee: Hidden -->
<tr class="formset-form sorting-row formset-form-empty hidden" data-formset-form-prefix="trustee">
<th class="formset-form-index text-center" scope=row>
<!-- # -->
X
</th>
<td>
<!-- Email -->
<div> <!-- Has error conditional class removed -->
<!-- TODO: Add an invisible screen reader label to associate with this and other inputs -->
<input type="text" class="form-control input-sm input-control" placeholder="Example: trusteeX@example.com" id="trustee-email-input" name="trustee-email-input" maxlength="255">
</div>
</td>
<td class="formset-form-actions text-center">
<button type="button" class="btn btn-sm btn-default formset-form-remove" aria-label="Remove">
<i class="fa fa-trash-o" aria-hidden="true"></i>
</button>
</td>
</tr>
{% endif %}
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</tbody>
</table>
<div class="clearfix">
<button type="button" class="btn btn-primary formset-add" data-formset-prefix="trustees">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<span class="glyphicon glyphicon-plus" aria-hidden="true"></span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
Add Trustee Email
</button>
</div>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="trustees-input-help-block" class="help-block">
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
Drag and drop to re-order emails.
</span>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="trustees-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.trustee_emails %}{{ invalid_fields.trustee_emails.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
</div>
<!-- Voters List -->
<div class="form-group">
<label for="voters-list-input" class="col-sm-3 col-md-2 control-label">Voters List:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<textarea class="form-control input-control" id="voters-list-input" placeholder="alice@example.com, bob@example.com..." name="voters-list-input" rows="4">{% if invalid_fields %}{{ invalid_fields.voters_emails_data.val }}{% endif %}</textarea>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<span id="voters-list-input-help-block" class="help-block">
Manually enter email addresses separated with commas. Alternatively, you can also upload a CSV file:
</span>
<label for="files" class="btn btn-primary">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<span class="glyphicon glyphicon-cloud-upload"></span>
Upload CSV
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</label>
<input type="file" id="files" name="file" class="btn-info">
Added delete functionality for events. Additionally, made improvements and fixed to the validation for event creation.
2018-06-19 14:15:42 +00:00
<h4 id="result" class="hidden successText"></h4>
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="voters-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
{% if invalid_fields.voters_emails %}{{ invalid_fields.voters_emails.error }}{% endif %}
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
<!-- reCAPTCHA -->
<div class="form-group">
<label for="recaptcha-input" class="col-sm-3 col-md-2 control-label">reCAPTCHA:</label> <!-- This text can be a template variable -->
<div class="col-sm-9 col-md-10">
Updated README to include details on dependency requirements. Updated Create Event page to disable the create button when the reCAPTCHA expires
2018-06-12 13:30:23 +00:00
<div class="g-recaptcha"
data-callback="reCVerificationCallback"
data-expired-callback="reCExpiredCallback"
data-sitekey="{{ G_R_SITE_KEY }}"></div> <!-- Need to finish server implementation and import key from settings -->
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
<span id="recaptcha-input-help-block" class="help-block">
Tick the box to prove that you're not a robot.
</span>
Updated create_event view backend to perform full form validation as a backup in the event the front end validation is incorrect and or is disabled. In the event that the back-end validation detects an error, the form is returned with the original data and errors informing the user on what pieces of information need corrected
2018-06-26 16:02:36 +00:00
<span id="recaptcha-input-error-block" class="help-block errorText">
<!-- Errors flagged here -->
{% if invalid_fields.recaptcha %}{{ invalid_fields.recaptcha.error }}{% endif %}
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</div>
</div>
<hr>
<input class="btn btn-success" type="submit" value="Create Event" id="submit-event-create" disabled/>
Laid the ground work for client-side input validation by setting up a fn that's triggered before the form is submitted. The vote start and end date time is now being validated both server side and client side and now includes UTC offsets
2018-06-13 12:01:55 +00:00
<input class="btn btn-danger" type="button" value="Cancel" id="cancel-event-create" onclick="location.href='{% url 'polls:index' %}'" />
Added full input validation to the Create Event including unique event name and slug validation as well as email validation. The appropriate template data required for this from Event and DemoUser model is passed in upon rendering the create_event html template
2018-06-14 16:01:14 +00:00
<span id="all-errors-help-block" class="help-block errorText">
<!-- Place a summary of all errors here -->
</span>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
</form>
</div>
</div>
</div>
Upgraded the Create Event page and back-end view to handle the creation of multiple polls in one go. The validation has been appropriately updated to cope with the UI changes but requires further testing. Event list has been updated to include a delete action which requires wiring up to a back-end function which hasn't been created yet
2018-06-18 16:09:44 +00:00
<!-- This dialog has been imported from DEMOS1 -->
<div class="modal fade" id="formset-modal" tabindex="-1" role="dialog" data-backdrop="static" data-keyboard="false" aria-labelledby="formset-modal-label">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
<h4 class="modal-title" id="formset-modal-label"></h4>
</div>
<div class="modal-body">
<div class="row">
<div class="col-xs-12">
</div>
</div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-danger" data-dismiss="modal">Cancel</button>
<button type="button" class="btn btn-success formset-form-save">Save</button>
</div>
</div>
</div>
</div>
Initial commit of DEMOS2 with the upgraded 'Create Event' UI. However, there is no input validation currently
2018-06-12 12:31:38 +00:00
{% endblock %}
Reference in a new issue Copy permalink