| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
|
| |
If we fail to match an update to a problem on the staging server then
print a warning so we can diagnose issues.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Add layers for:
* Road crossings
* Belisha Beacons
* Gullies
* Street signs
* Bollards
|
| | |
| |
| |
| |
| |
| |
| | |
Not all the layers use the same attribute for the feature code so add
and use a config option to set this, and extract out the style map
settings so we can change them to use the correct attribute for the
label.
|
| |/
|
|
|
|
|
| |
use the asset code to determine what sort of type the asset is for
displaying the 'you have selected $type $code' message. Also, pull this
out into a new set of defaults so we can apply it across multiple asset
types.
|
| |
|
|
|
| |
Add a hook to enable the cobrand to do some extra processing when saving
a report on the inspect report screen.
|
| |
|
|
|
| |
Enable the cobrand to save extra data when creating/editing users in the
admin.
|
| | |
|
| |
|
|
| |
Previously, CSS was absolutely positioning one on top of the other.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is so front-end tests will not try and send email, or
call Gaze. Various co-ordinates have to be updated because
the default zoom level of the map has now changed.
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/
|
|
| |
The core validation_rules.js is not included on e.g. the front page.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
| |
All templates call private_details.html, which uses this variable.
|
| |
|
|
|
| |
This doesn't appear to cause any issues on Linux, but on Mac it fails to
find the translation file without this. Matches the code in App.pm.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| | |
| |
| |
| | |
Co-authored-by: Zarino Zappia <zarino@mysociety.org>
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Remove update/form_name.html template.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
