| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
| |
It was not being caught by rerun_dbic_loader.pl otherwise.
|
|
|
|
|
|
|
|
|
| |
Times in the database should be stored in the application server's local
timezone, by e.g. using `current_timestamp`, or by setting that timezone
explicitly before storage (the database columns are all without timezone
so any timezone info is silently ignored). Reports & updates fetched via
Open311 and offline updates were being put into the TIME_ZONE setting if
present, meaning they were stored incorrectly for future usage.
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Rather than compile it all into on big string for output, write the
output as we go. Also output headers to encourage intermediaries to
stream as well.
|
|/
|
|
|
| |
This simplifies the places where a date range is used;
it also makes Dashboard date parsing more flexible.
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Unused right now, but will be soon, for the duplicate suggestion UI.
|
| |
|
|\ |
|
| |
| |
| |
| | |
Fixes #1957
|
|/ |
|
|
|
|
|
|
| |
Update database to store an array of IDs rather than only one;
consequential changes to the admin and the dashboard to allow
selection.
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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).
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
Currently keeping the same front end functionality of only reverting to
the original.
|
| |
|