| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Prevents potential odd-element hash in e.g. response_priorities.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Instead of returning all templates for the problem's body, return those
for the problem's category (or with no category).
|
|/
|
|
|
| |
- Priorities with no categories selected are available to all categories
- Display active categories in response priorities table
|
| |
|
|
|
|
|
|
|
| |
This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.
For mysociety/fixmystreetforcouncils#66
|
|
|
|
|
|
|
|
| |
This introduces a new `is_council_with_case_management` flag for Cobrands, that,
when active, considers any report that's been confirmed as having been received
by the Council in question.
See mysociety/fixmystreetforcouncils#65
|
|
|
|
|
|
| |
A user with the appropriate permission can add/remove reports from their
list of planned reports using a button on a report page. The list can be
viewed at /my/planned.
|
| |
|
|
|
|
| |
Also don't fetch tiles if running tests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When viewing a report on FMS.com whose recipient council has a
FMS cobrand, turns the council name into a link to view the same report
on that council's cobranded site.
Includes methods cribbed from Hakim's Open311 refactor branch from
commit 47daa02420a4f5a4264c31efcf2a2e8611c2f23e.
|
|
|
|
|
|
|
|
|
| |
When viewing on FMS.com a report made via a council cobrand, this
adds a link to the FMS for Councils page for more info.
This works by breaking out the report meta line ('Reported in the
Street lighting category by Joe Bloggs at 09:51, Tuesday 1 March 2016')
into its own template which can be overridden for the fixmystreet.com cobrand.
|
|
|
|
|
|
|
|
|
|
|
| |
- Use new `getLocation95` method for geocoding addresses
- Replace Coordinates::CH1903 with Coordinates::CH1903Plus
- Refactor Map::Zurich to use WMTSBase instead of duplicating code
- Slightly refactor map templates to make using custom WMTS tiles easier
- Use correct sizes for marker pins on maps
Closes mysociety/FixMyStreet-Commercial#769.
Closes mysociety/FixMyStreet-Commercial#768.
|
| |
|
| |
|