| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
| |
And use the existing ones more.
|
| |
|
|
|
|
|
| |
/around will now show all reports all the time, but we are about to
introduce pagination to stop that.
|
| |
|
|
|
|
|
| |
These are so we can state whether a user's email address or phone number
have been verified by confirmation email/text.
|
|
|
|
| |
This can fail if the tests are being run in parallel.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was possible for _hardcoded_states to be reached with no locale
selected (e.g. bin/update-all-reports), causing an error trying to
translate Open/Closed. But translating those there wasn't correct,
because that would then be cached and returned even if a different
language was being used. Caching was ignored in testing, which did
not help.
We no longer translate the state names in their objects, only upon
display at the point that we will know the locale. We can't simply
return the translation of Open/Closed because there may be entries
in the translation table as well.
|
|
|
|
|
|
|
|
|
|
|
| |
State display names are now got from the database wherever they are
displayed, including admin dropdowns, list filters, and update meta
statements. This also covers the open/closed/fixed 'groups'.
This also fixes a bug whereby if e.g. an update has problem_state
investigating, the next update has no problem_state, and the last
update has investigating again, it was previously showing a state
change to investigating on that third update.
|
|
|
|
|
| |
We keep the internal states hardcoded, plus the core open (confirmed)
and closed ones, but the remainder are moved to the database.
|
| |
|
|
|
|
|
|
|
| |
- Also provides an editor for the extra Open311 fields on contacts.
- Adds .btn--small class for small buttons
Fixes #1743.
|
| |
|
|
|
|
|
| |
Inactive ones can still be used for e.g. list filtering,
but not when making a new report.
|
|
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
|
|
|
|
|
| |
When the category or state changes, the list of available templates
updates (previously it was frozen at what the category was on page
load, and didn't care about the state).
|
|
|
|
|
| |
This now lets the response priority and defect type handling share the
same code.
|
| |
|
|
|
|
|
|
|
|
|
| |
Problems can have an associated defect type, that can be assigned during
an inspection. Include an admin interface for managing these types, that
can also be assigned on a per-category basis, currently available to the
Oxfordshire cobrand.
(Also include 'TM' in traffic management Exor RDI output.)
|
|
|
|
|
| |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
|
|
|
|
|
|
|
| |
Includes newest, oldest, least/most recently updated, and most comments.
The default remains the same, which is last updated on /reports, and
newest on /my and /around (the latter plus not-in-view
sorted-by-distance ones).
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This lets people filter by multiple categories or states. It uses our
jQuery multi-select plugin to turn the <select multiple>s into little
overlay lists of checkboxes. HTML5 history is also supported.
|
|/ |
|
| |
|
|
|
|
|
| |
The 'created' and 'state' column names are shared between the 'problem' and
'comment' tables, and this was causing ambiguous column references in the SQL.
|
| |
|
|
|
|
|
|
| |
There might be the odd update alert we are interested in (those not
auto-signed up for as part of report or update creation), but they
will be rare.
|
|
|
|
|
|
|
|
|
|
|
|
| |
5c79337 simplified a bit too far, as after then a particular cobrand
could in Nearby and My only filter reports to a particular body, not
any other criteria. To fix this, introduce more generic functions in
the default cobrand to allow more flexibility.
Make sure a few tests delete their bodies fully so that new tests
pass when run as part of the suite.
Fixes #1289.
|
|
|
|
| |
Maintain old location wrappers.
|
| |
|
|
|
|
| |
Command line scripts don't need a full blown app, just database.
|
| |
|
|
|
|
|
|
|
|
| |
* Don't show a categories summary unless asked via a link
* Don't needlessly join in questionnaire/update summaries
* Switch count(distinct()) to a subselect as it turns out
select count(*) from (select distinct(user_id) from problem) temp;
is a lot quicker than select count(distinct(user_id)) from problem;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See mysociety/FixMyStreet-Commercial#690
- external_message for Extern/Wunsch states
- as per PDF mockups, the "public response" field is now editable
from more states, namely:
- Ruckmeldung ausstehend
- Extern
- Zustandigkeit unbekannt
- Wunsch
- Nicht kontaktierbar
- Unsichtbar
- test fixes
NB: slight hack to reorder Zurich report_display tests
As these remove 'investigating' from hidden_states, these break
tests for default cobrand (the FMS::App code expects to be called
once on request start, not multiple times within one test)
- Not contactable button
and tests for this and the similar `send_back` functionality
(previously untested).
NB: Unsure why we need to specify form_number=2 just for these submits,
but test won't find the buttons otherwise.
- Make sure SDMs' "time_spent" figure is recorded.
(See mysociety/FixMyStreet-Commercial#718)
|
|
|
|
|
|
| |
If a cobrand has a body restriction, then a report without any body
won't be shown on it, so we need to make sure links to the report (in
email alerts and RSS) are to the base URL, not the cobrand.
|
|\ |
|
| |
| |
| |
| |
| | |
Matches send_email, remove unneeded setting of sender in one call, and
add contact name to report sent email.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Make dashboard work properly in two-tier councils, showing reports sent
to both. Create an index on the array of the bodies_str column to speed
up performance, and use that throughout the code replacing all LIKE
scans. This also enables a simplifying tidy of the restriction code.
|
| |
| |
| |
| | |
Fixes #893.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
This makes no actual change to the query (the joins are all on the same
value, after all), but along with the removal of ms_current_timestamp in
the previous commit massively speeds it up as the query planner realises
it can do a hash join rather than a nested merge join.
|
|
|
|
|
| |
This override is not used anywhere, it dates from a very old long-gone
test script, and causes issues with database query planning.
|
|
|
|
|
| |
Add an index on the radian values, make the function stable, and switch
to a full bounding box rather than a slower angle check.
|
|
|
|
|
|
|
| |
Restrict email_sign_in token to one day, unused confirmation tokens to
one month. Used tokens will redirect to the created thing but not log
in; don't log in with alert links (unsubscribe link never expires, reply
link will still show "reopen" tickbox).
|
|
|
|
|
| |
If present, the 'status' param can be set to 'open' or 'fixed' to display
ensure only open or fixed reports respectively are included in the response.
|
| |
|