| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Currently keeping the same front end functionality of only reverting to
the original.
|
| |
|
|
|
|
|
|
|
| |
body.url could still be in use by old-school /reports table index pages
(though they were dropped in 2.1, so a cobrand would have to have
overridden it since then) and the update to speed up body lists in #2248
broke it. This puts it back in minimal form.
|
|
|
|
| |
We can now use the new open311_post_update_skip function.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Then it can skip working out some things as they are not needed.
|
|
|
|
|
|
|
| |
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!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Include actual times, not just human-readable ones, and
make sure state is translated correctly.
|
|
|
|
|
|
| |
This includes stopping some emails being sent (moderation, alert,
questionnaire), dealing with Open311/email report sending, and
tokenised_url.
|
|
|
|
|
|
|
| |
If we've stored the nearest address then display that at the top of the
inspector panel.
Fixes mysociety/fixmystreetforcouncils#234
|
|
|
|
|
| |
For temp URLs there was not already a query string, and
so "?" needs to be used rather than "&" when appending.
|
|
|
|
|
|
|
| |
Adds a Ward column to the council dashboard CSV export with the name of
the ward.
Fixes mysociety/fixmystreetforcouncils#220
|
|\ |
|
| |
| |
| |
| |
| | |
We keep the internal states hardcoded, plus the core open (confirmed)
and closed ones, but the remainder are moved to the database.
|
|/
|
|
| |
If set to 1, this restricts all pages on the site to logged-in users.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This avoids the need to search the whole table to find a report's
duplicates. And is easier than constructing an index or upgrading
PostgreSQL.
|
|
|
|
|
|
| |
Calling the function 'translate' causes gettext-extract to add the
string to the .po file. Also, we no longer need an admin 'updated'
message as the main form has its own success message.
|
|
|
|
|
|
| |
As category is used both for display and as a link between Problem and
Contact tables, add `category_display` for use whenever a category is
displayed.
|
|
|
|
|
|
|
|
| |
A recent change doubled the size of the pin images, which meant the static
maps included in report emails had the pin in the wrong place because the
compositing code made assumptions about the pin size which were wrong. This
commit ensures the pin image is of a known size before compositing, putting
the pins back in the right place.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically in UK cobrands, bodies have had IDs the same as the MapIt
area ID they cover. This can be confusing (if you are setting up a dev
environment, say) and should not be necessary. This commit removes the
requirement entirely, by switching any ID checks to either the name of
the body, or the actual area it covers.
One note: the body name in the test has to match so that we do not get
two bodies both covering 2237 created. This will not be necessary when
the tests are compartmentalized in the next commit.
|
|
|
|
| |
Add hook so that cobrands can change pin hover title.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid doing cobrand-specific logic within SendReport::Open311.
The hooks defined are:
open311_config: set extra fields
open311_pre_send: set endpoints and munge data
These are tested in the new t/app/sendreport/open311.t, which does
not send any actual reports, but just checks that all the data is
munged into the expected format. (tests under t/open311* should
already test the actual sending)
Remove unused Open311 special cases.
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#98
|
|
|
|
|
|
|
|
|
|
| |
The RDI file format encapsulates information about inspections that have taken
place, and can be uploaded into Exor to create defects in bulk.
This commit adds a page to the Oxfordshire cobrand's admin allowing RDI files
to be generated and downloaded from FMS.
For mysociety/fixmystreetforcouncils#127
|
| |
|
|
|
|
|
|
| |
This method creates a token that logs the reporting user in, optionally
with some parameters which are stored with the token for use when redirecting
after login.
|
| |
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#159
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Use Problem->pin_data for single report page
- Promote markers_highlight to fixmystreet.maps API
We want to highlight map pins on the duplicate report selection UI, so let's use
what's already there instead of writing something new.
- Make sure duplicate report pins aren’t draggable
|