aboutsummaryrefslogtreecommitdiffstats
path: root/templates
Commit message (Collapse)AuthorAgeLines
* Version 2.5.v2.5Matthew Somerville2018-12-21-1/+1
|
* Show all questionnaire responses lacking updates.Matthew Somerville2018-12-20-1/+8
| | | | | | Since questionnaire responses were recorded on email link click, we should have been showing those that reopened or fixed reports, not just steady-state "Still open" ones.
* [fixmystreet.com] Add donate banner.Matthew Somerville2018-12-19-0/+5
|
* [Buckinghamshire] Get topic when reporting abuse.Matthew Somerville2018-12-19-0/+48
|
* [fixmystreet.com] Get topic when reporting abuse.Matthew Somerville2018-12-19-3/+15
|
* Make who question more prominent.Matthew Somerville2018-12-19-32/+39
|
* Improved report/update display on contact form.Matthew Somerville2018-12-18-12/+12
|
* Stop both Unknown/In progress banners appearing.Matthew Somerville2018-12-13-6/+3
| | | | Previously, CSS was absolutely positioning one on top of the other.
* Modernise report "status" bannerZarino Zappia2018-12-13-9/+22
| | | | | | | | | | | | | * Simplify markup required for the status banner. * Simplify styles - the banner is now identical on all screen sizes. * Move the banner from `report/display.html` into `report/_main.html` so that it can appear after `.problem-back` in the source order. * Use real pin icon instead of `pin-flat-white-small.png`. * Set a default `$col_fixed_label` colour in `_base.scss`, so cobrands don’t have to define it themselves if they’re happy with green. * Introduce `$col_fixed_label_light`, with a sensible default for all cobrands, even ones that have a custom `$col_fixed_label`. * Remove `$col_fixed_label_dark` – no longer needed.
* [Buckinghamshire] Nicer not-our-road messages.Matthew Somerville2018-12-11-6/+28
|
* [Buckinghamshire] New tracking code.Matthew Somerville2018-12-08-14/+26
|
* [Bromley] Tidy up some form templates.Matthew Somerville2018-12-08-83/+33
|
* Show email form after logging in as leaving updateMatthew Somerville2018-12-08-11/+12
| | | | | | | | | With the recent login changes, the user form was being hidden after logging in while leaving an update, meaning you had to click "Continue" to see the thing it was asking you to check. Refactor the update flow slightly in this area to be more like reporting, showing the relevant bit of the user form immediately (and thus also not having it within a hidden section).
* Specify type variable to both in and out templatesMatthew Somerville2018-12-08-3/+3
| | | | All templates call private_details.html, which uses this variable.
* Fix issue with multiple button IDs on page.Matthew Somerville2018-12-05-8/+8
| | | | | | When a report is pulled in via ajax, it means there are then two sets of login flow buttons on the page, and the JS setup only attaches to the first of these.
* Merge branch '642-new-report-flow-changes'Matthew Somerville2018-12-05-537/+330
|\
| * Move email input nearer password input on forms.Zarino Zappia2018-12-05-25/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This moves the email input from `user_loggedout.html` closer to the password inputs in `user_loggedout_{by_email,password}.html`, because we want to emphasise the connection between your login email/username and your password, and, now that only one "Yes I have an account / No I do not have an account" fieldset is displayed at a time, there was no reason to ask for the email/username up front. This, however, now means the form includes two username inputs, so: * `Report/New.pm` and `Report/Update.pm` now pick the first non-empty username param and use that. * `user_loggedout_email.html` now expects a `name` parameter, so that we can give the two username inputs unique ids in the markup. Also: * The "optional" phone and email inputs in user_loggedout_by_email.html are printed *after* the main username input if SMS login is enabled (since one or other of them is unhidden by javascript, based on whether you entered a phone number or and email address into the "username" input, and it would look weird to have an input become unhidden *above* the input you’re currently editing).
| * Update sign in flow for new reports/updates.Matthew Somerville2018-12-05-143/+193
| | | | | | | | Co-authored-by: Zarino Zappia <zarino@mysociety.org>
| * Fix form_email/form_username typo in logged-in report formZarino Zappia2018-12-05-1/+1
| |
| * Form submit buttons no longer inline with inputs.Zarino Zappia2018-12-05-17/+9
| | | | | | | | | | | | This was a cute space-saving feature at the time, but the layout made it look like the button was specific to that input, rather than submitting the whole form. Make similar buttons full width, and improve spacing.
| * Simplify category required attribute.Matthew Somerville2018-12-05-3/+3
| |
| * Consolidate the report/update loggedout templates.Matthew Somerville2018-12-05-332/+92
| |
| * Tweak update templates to better match reporting.Matthew Somerville2018-12-04-43/+49
| | | | | | | | Remove update/form_name.html template.
| * Remove form-focus-trigger/hidden behaviour.Matthew Somerville2018-12-04-22/+22
| |
| * Do not show second email form if SMS_AUTHENTICATION off.Matthew Somerville2018-12-04-0/+2
| |
| * Remove “Keep me signed in” box.Matthew Somerville2018-12-04-26/+0
| |
* | Fix moderation without JavaScript.Matthew Somerville2018-12-04-4/+10
|/
* Associate moderation history with admin log.Matthew Somerville2018-11-27-2/+6
|
* Show moderation history in report/update admin.Matthew Somerville2018-11-26-0/+41
|
* Store all moderation change history in database.Matthew Somerville2018-11-26-4/+4
| | | | | Currently keeping the same front end functionality of only reverting to the original.
* Improve update display on admin report edit page.Matthew Somerville2018-11-26-14/+17
|
* [UK] council specific javascript validationStruan Donald2018-11-26-1/+18
| | | | | | | | | use the bodies array of reporting_data to check if there is council specific javascript validation and, if so, load that into the JS validation rules. This does mean we reset the validation rules each time you select a category.
* [UK] server side cobrand specific validationStruan Donald2018-11-26-0/+9
| | | | | | `report_check_for_errors` now fetches the cobrand for the current report and, if present, runs `report_validation` method from cobrand over the report.
* add report_prefill user permissionStruan Donald2018-11-19-2/+4
| | | | | | | If set then when the user creates a new body report it will prefill the report title and description with some basic text. For mysociety/freshdesk#23
* add default_to_body permissionStruan Donald2018-11-19-2/+2
| | | | | | | If a user has this permission then the report_as dropdown will default to reporting as the body. For mysociety/freshdesk#23
* [Bristol] include highways england dataStruan Donald2018-11-19-0/+1
| | | | | | This changes the projection from EPSG:3857, which is not included in the bristol openlayers build, to the identical EPSG:900913 which is, so that the conversion happens.
* [Buckinghamshire] Allow reports on Highways England roadsStruan Donald2018-11-19-1/+1
| | | | | Do not hide the report form if you click on a non Bucks road that is managed by Highways England.
* [UK] send reports on highways agency roads to highways agencyStruan Donald2018-11-19-0/+4
| | | | | | | Includes an option to send to the council instead for e.g. reports on underpasses or bridges. Fixes #736
* Sort user updates in reverse date order.Matthew Somerville2018-11-19-2/+2
|
* add report_mark_private permissionStruan Donald2018-11-12-1/+1
| | | | | | | | Allows user's to see the inspector panel to mark reports as Private, and also to view those non-public reports. Useful for call centre staff who want to record private reports but don't need to other permissions. Fixes mysociety/fixmystreet-commercial#1213
* Simplify /auth sign in page.Matthew Somerville2018-11-09-63/+88
|
* Make .btn--block work on button and input elementsZarino Zappia2018-11-09-1/+1
| | | | | | | | | The intention of .btn--block is to make the element full width. Because of the weird way browsers handle sizing of form elements, just setting `display: block` on `<button>` and `<input type="submit">` elements wasn’t making them full width. Instead, .btn--block needed to explicitly set a 100% width, and then reset any margins or box-sizing issues that might cause it to overflow its parent.
* Clearer relocation options while reporting.Zarino Zappia2018-11-06-1/+4
| | | | | | | | | | | | | | | | Now that the "Report a problem" link in the nav bar links, more often than not, to the reporting form rather than the homepage, it could be challenging to actually start a new report in a location *other* than the one currently on screen. Rather than adding a link to the homepage, this change hopefully adds a link right at the moment the user expects it – right on the "Report a problem" form. It also gave us an opportunity to reword the "Wrong location" message and give it an icon more suitable for high-dpi displays. Fixes #2238.
* Revert "Clearer relocation options while reporting."Matthew Somerville2018-11-06-4/+1
| | | | This reverts commit ee3c4e05daf3f4df01762ead3d07697a12f13a28.
* [FixaMinGata] Don't scroll report on loadJoe Siltberg2018-11-05-0/+3
|
* use submitted phone number and email in login formStruan Donald2018-10-23-4/+4
| | | | | | do not use details directly from user object because in the slim chance that the user has phone and email verified and there is a failed email login we display the phone number from the database.
* Use Chains in /report.Matthew Somerville2018-10-22-3/+3
|
* add alert editing to user edit page in adminStruan Donald2018-10-19-0/+11
| | | | disable, enable and delete for user alerts on user_edit page
* list user's alerts on user edit page in adminStruan Donald2018-10-19-0/+51
| | | | | Include a list of alerts the user is subscribed to at the bottom of the user_edit page in the admin.
* [Bromley] update footer links to httpsStruan Donald2018-10-18-11/+10
| | | | Also, remove top of page link that was hardcoded to a now missing page.