| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
| |
Similarly to 1f69e28c, we were previously only checking the first
matching entry, which led to confusing behaviour in places. Include
consequential amendments for e.g. one body being unresponsive, the
other not.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Remove the server-side zoom-in-url fix, instead use an ArgParser
subclass to default to the provided data if nothing in URL. Then
we can switch to using short lat/lon in geocoder URLs.
|
| | |
| |
| |
| |
| |
| | |
Fixes #2242.
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Template Toolkit treats keys starting with ‘_’ as private and does not
expose them. It is possible for an Open311 server to return fields
starting with an underscore, and we want to use those in the template.
|
| | |/
|/|
| |
| |
| | |
Add a configuration variable to use for the front page stats/
recent list, plus the max-age of `/reports`.
|
| |/ |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
If someone tries to moderate after someone else has, re-show the
form and an error.
|
| |
|
|
| |
This will also be used by the moderation conflict code.
|
| |
|
|
|
| |
The server doesn't need to know about it, it was
only for us to pick the appropriate body.
|
| | |
|
| |
|
|
|
|
|
|
| |
This adds a question to check whether a flytipping report concerns
flytipping on a road or not. Client-side, it is asked when a road is
selected and destination adjusted according to the answer; server side
it uses the answer to direct any both-tier submissions (from e.g.
non-JavaScript or phone app).
|
| | |
|
| | |
|
| |
|
|
|
| |
Old moderation history entries will have blank category/co-ords,
and we don’t want to say they’ve changed on appearance.
|
| |\ |
|
| | |
| |
| |
| |
| | |
If a state is passed in (on a cobrand), update problem state and add a
comment to record this (as state changes are updates not moderations).
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If the user has moderating permission, or a cobrand allows the viewing
of moderation history, show moderation history within the updates on a
report page.
|
| | |/ |
|
| |/
|
|
|
|
|
| |
Add in validation to check names, email and phone numbers don't exceed
maximum lengths permitted by HIAMS.
Fixes mysociety/fixmystreet-commercial#1244
|
| |
|
|
| |
So state/confirmed setting in one place.
|
| | |
|
| |
|
|
|
|
|
|
| |
As perlsyn says, "NOTE: The behaviour of a `my`, `state`, or `our`
modified with a statement modifier conditional or loop construct (for
example, `my $x if ...`) is undefined. The value of the `my` variable
may be `undef`, any previously assigned value, or possibly anything
else."
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is so you can have a search box on an around page (wrapped in a
form going to /report/new) to start a new search, ignoring the lat/lon
that will also be submitted.
|
| | |
|
| |
|
|
|
|
| |
Add a method to do some basic filtering of emails and phone numbers from
report descriptions. To be used on reports pulled in from Confirm as a
first pass at removing personal information.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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 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.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
