| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
| |
This reverts commit 6bc39892d7075fac79c0f40b2740de095535329d.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The inactive report script can mark matched reports as closed for updates.
This removes the update form and signing up for updates from a report page.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Some Open311 servers will refuse an update with a
timestamp earlier than one it already received.
|
|
|
|
| |
Otherwise we may not warn on otherwise skipped updates.
|
|
|
|
|
|
|
|
|
| |
Previously send-comments errors would only be printed the first time
they occurred so there was no visibility of ongoing errors. This brings
send-comments in line with send-reports by emitting errors if the script
is called with --verbose.
Fixes #2091
|
|
|
|
| |
Adds and extra column for bodies and the associated Extra role.
|
| |
|
| |
|
|
|
|
| |
Also adds script for fetching the last 24hrs of reports
|
| |
|
|
|
|
|
| |
For controlling if reports pulled in via Open311 should have the
position converted from Easting/Northing to lat/long.
|
| |
|
|
|
|
|
|
|
|
| |
I don't think this check could ever have worked, because items are invisible
if their parent is set to `display: none`, so it would hide the links bar if
it was already hidden, and show it if it was already shown.
Use a js- class for the movement of the feed item into the sub map links.
|
|
|
|
|
| |
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.
|
|/
|
|
| |
Add an update with each report closure.
|
| |
|
|
|
|
|
| |
This also can set up users so that the admin
"Log user out" function works correctly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bristol's Open311 endpoint still seems to be returning empty metadata
for some services that claim to have metadata. They have made changes to
their published services since the change was made to exclude their
endpoint, which is causing issues for new reports.
Rather than exclude their endpoint entirely from being updated, this
commit just silences the noisy error message for Bristol.
Reverts the change made in 491eb26e4.
|
| |
|
| |
|
| |
|
|
|
|
| |
And use the existing ones more.
|
|
|
|
|
|
|
|
|
|
| |
It took a few years but somebody finally made a report at a whole-number
lat/lon (52°N in this case) which was duly rejected by the OCC Exor
script as not being a valid coordinate due to the assumption that all
lat/lon values will contain a ‘.’ character.
This commit makes the decimal part of the value optional, allowing
integer values to be sent.
|
| |
|
| |
|
|
|
|
|
| |
Only works on bodies with an associated area, and requires the
object to be passed in, not just its ID.
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#251
|
|
|
|
| |
otherwise the login doesn't work post sms auth changes.
|
| |
|
| |
|
|
|
|
|
| |
These are so we can state whether a user's email address or phone number
have been verified by confirmation email/text.
|
|
|
|
|
| |
body_str is encoded with the provided charset/encoding, body is used
as-is (and so will die in email sending if it contains wide characters).
|