| Commit message (Collapse) | Author | Age | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
This fixes a bug whereby a double quote in an item would not be JSON-escaped
due to being HTML-escaped first, meaning it would not parse as JSON on the
client.
|
|
|
|
|
|
|
| |
So that you can build functionality to add extra limitations on
to the map pins displayed. Useful for Collideoscope initially
to filter out (or in) reports from the Department of Transport's
Stats19 Data.
|
|
|
|
| |
Adds and extra column for bodies and the associated Extra role.
|
|
|
|
|
| |
Also stop caching lat/lon specific alert photo lists, and improve
Memcached code.
|
| |
|
|
|
|
|
| |
For controlling if reports pulled in via Open311 should have the
position converted from Easting/Northing to lat/long.
|
| |
|
| |
|
|
|
|
|
| |
We do need to store them, so that the sending knows which fields are being
requested, but we do not want them output to the client at all.
|
| |
|
|
|
|
| |
Then it can skip working out some things as they are not needed.
|
|
|
|
|
| |
Add a per body configuration option to allow Open311 updates to contain
only a status change, rather than emitting a warning when this happens.
|
|
|
|
|
|
|
|
|
|
| |
This enables the display of existing reports from the back end on FMS
if the body is configured to do this.
Reports will not be created if they are missing an id, a lat or a long,
if the lat/long is outside the area covered by the body, if there is
already a report with a matching id, or if we can't parse out the
request time.
|
|
|
|
|
|
|
| |
The Zurich code was written a long time ago, and used overriding so that
e.g. the hard-coded 'investigating' state referred to Wunsch (wish). Now
that states are stored in the database, we can create ones specially for
Zurich and use them instead. Hooray!
|
|
|
|
| |
Remove old unused setup-contacts code, superceded by fixtures.
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
This brings in my new format_for_country function which allows
for nicer display of phone numbers to people.
|
|/
|
|
| |
Though when running tests, decrease it for speed.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 'updates are not sent to the council' message was incorrectly being
shown on reports where updates would in fact be sent. This was affecting
non-Bromley/Stevenage reports on fms.com and all cobrands using Open311.
This commit moves the logic out of the template and adds the
Problem->updates_sent_to_body method which inspects the receiving body's
Open311 configuration to determine whether updates will be sent.
The duplication of the Lewisham/Oxfordshire logic between Problem.pm and
send-comments isn't ideal but hopefully there won't be any new Open311
bodies that only send and don't receive updates. If there are we'll have
to look at refactoring that list.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
When more than one photo has been uploaded, allow each one to
be published/not independently.
|
|/ |
|
| |
|
|
|
|
| |
And use the existing ones more.
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
| |
Include actual times, not just human-readable ones, and
make sure state is translated correctly.
|
| |
|
|
|
|
|
| |
/around will now show all reports all the time, but we are about to
introduce pagination to stop that.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a comment on a problem when the admin is used to change the state
of the problem. If only the state is changed then create a comment with
blank text. If the category and state are changing then include details
of the category change in the comment.
Not all the state changes are displayed at the template level by
default.
Fixes #1846
|
| |
|
|
|
|
|
| |
We have no way of knowing whether a +1 geographic number is fixed
line or mobile, so accept them all as potentially mobile.
|
|
|
|
|
|
| |
This expands the 'change email' functionality to work with phone
number also, allow addition of missing details, and verifying of
unverified details.
|
| |
|
|
|
|
|
|
|
| |
This includes search/flagging users, editing user on the report
and update edit pages, and user adding/editing itself.
Add some more tests for user adding/editing.
|
|
|
|
|
|
| |
This includes stopping some emails being sent (moderation, alert,
questionnaire), dealing with Open311/email report sending, and
tokenised_url.
|
|
|
|
|
| |
These are so we can state whether a user's email address or phone number
have been verified by confirmation email/text.
|
|
|
|
|
|
|
| |
If we've stored the nearest address then display that at the top of the
inspector panel.
Fixes mysociety/fixmystreetforcouncils#234
|