| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
Bromley previously had an override for fill_in_details_form.html, just
so that it could display a custom sign-in arrangement.
Now that the core fill_in_details_form.html delegates the sign-in stuff
to form_user.html, Bromley can override just that template, and inherit
all the other reporting form goodness from core.
|
|
|
|
|
|
|
|
|
|
|
| |
Form input styling is mostly left up to the browser default now.
A custom border, drop-shadow, and border-radius can be applied by
adding the `.form-control` class, which standardizes the appearance
of inputs, selects, and textareas.
The core reporting form, authentication forms, local alert forms,
contact form, and questionnaire form have all been updated to use
the new `.form-control` class.
|
|
|
|
|
| |
This message doesn’t make sense when displayed on a council’s website.
(Maybe it was originally intended for FMS.com instead?)
|
|
|
|
|
|
| |
The ticks and crosses already imply that these are things you should
and shouldn’t do. Removing the headings reduces visual clutter, and
better associates the tips with the form input directly above.
|
| |
|
|
|
|
|
| |
`form_user.html` now acts as a counterpart to `form_report.html` and
contains all the form elements to do with login / personal details.
|
|
|
|
|
| |
Labels in category_extras.html now match the style of labels in the
rest of the reporting form (ie: no closing colon).
|
|
|
|
|
| |
Switching between categories with / without extra questions no longer
results in nested `#category_meta` elements.
|
|
|
|
|
|
|
| |
Previously only Bristol, Angus, and FMS.com had the category select
box at the top of the form. In our experience, this has worked well,
and hasn’t affected the usability of the form, so let’s standardize
and put it at the top of the form for all cobrands.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
|/
|
|
|
|
|
| |
This adds an update field to the bottom of the inspect form, requiring the
inspector to provide an update to be added to the report as it's sent.
See mysociety/fixmystreetforcouncils#64
|
| |
|
| |
|
| |
|
|
|
|
| |
Adapt code so that it could be opened up more in future.
|
| |
|
|
|
|
| |
Stop IDs being shown on 404 pages, provide a nicer message on 403 pages.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Allow get_extra_metadata to return all the data with no argument.
|
|/
|
|
|
|
|
| |
This is a cut-down version of the full inspect screen.
We truncate the co-ordinates just in case (they should be anyway but
e.g. the test report isn't).
|
|\ |
|
|/
|
|
|
|
|
| |
This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.
For mysociety/fixmystreetforcouncils#66
|
|\ |
|
|/
|
|
|
|
|
|
|
|
|
| |
Categories can now require reports to be marked as 'inspected' via the frontend
before they're sent by send-reports.
A side-effect here is that send-reports will perform an extra n queries for each
report, where n is the number of bodies that report is being sent to, but
hopefully in practice this won't matter as it's an offline cronjob.
See mysociety/fixmystreetforcouncils#50
|
|\ |
|
| |
| |
| |
| |
| | |
A very subtle nudge that you can/should upload multiple photos. With a
fallback to singular if Dropzone fails to load for some reason.
|
| | |
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Form labels now describe what the user should do, and placeholders
give a supporting example of what their input should look like.
Placeholder text in the "Summary" box now suggests that people
include a location in their summary. Likewise with a timescale in
the "Description" box.
Placeholders use potholes as an example, since potholes are the most
common complaint on FMS. Maybe eventually we might want to change the
placeholder text based on the category the user selects…
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Firefox would, on a page that pulled in a report via ajax, only
return the reporting form's name field with #form_name. Switch
to using a class on the relevant fields.
|
| | |
|
| |
| |
| |
| | |
Firefox still only scrolls precisely to the focus.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the user is a member of the body the report was sent to (and the
cobrand has the option enabled), show the remove from site button.
This was previously cobrand-based (it was shown if the user was a
member of the body the cobrand has hardcoded as its council_id),
which was confusing and harder to implement. Fixes #1508.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces a new `is_council_with_case_management` flag for Cobrands, that,
when active, considers any report that's been confirmed as having been received
by the Council in question.
See mysociety/fixmystreetforcouncils#65
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
This builds on the response templates in the Zürich cobrand:
- Allow response templates to be assigned to categories
- Also adds a auto_response flag, which will be used to automatically create
updates when reports are made.
- Include response templates select box on update form
For mysociety/fixmystreetforcouncils#31
|
|\ |
|
| | |
|
| | |
|