| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
|
|
|
|
| |
The code now uses this translation as the hard-coded way was removed.
|
|\ |
|
| |
| |
| |
| | |
This fixes #2023 by removing the comma.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
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 is part of the integration with our open311-adapter. The automated
property indicates that it's an expected value but either it's going to
be set by the server, or appear as a hidden field.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per cobrand configurable option to send multiple photos over open311
instead of just a single one. Does this by sending multiple media_url
parameters in the POST body.
The default remains to send the first photo associated with a report.
|
| | |
| | |
| | |
| | |
| | | |
Web and email template changes, CSS plus cobrand file with open311
config
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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 event handlers for category changing were being added too early,
before fixmystreet.map had been created. For cobrands with category
grouping enabled this was causing a crash in the JS because the grouping
code emits a category change event during its setup (which runs between
fixmystreet.assets.add and .assets.init).
This commit adds the event handlers for each layer during
fixmystreet.assets.init - at point at which fixmystreet.map has been set
up. Also extracts the code for initing each layer into its own function
for clarity.
|
| | |
| | |
| | |
| | |
| | | |
This allows users (e.g. customer service staff) to search for a user's
reports in the admin without being able to edit them.
|
|/ /
| |
| |
| |
| | |
This commit re-sets the values of any form inputs when the
category extra elements are reloaded, e.g. when the category is changed.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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!
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This variable existed to keep a copy of the categories before it was
overwritten by report_edit_location (if a bad location was provided)
calling the variable setup functions again. But really, the function
shouldn't be overwriting the stash, it's only testing the lookup and
so should restore the stash at its end.
|
| | | |
|
| | |
| | |
| | |
| | | |
Remove old unused setup-contacts code, superceded by fixtures.
|
| | |
| | |
| | |
| | | |
Adapt look of default dashboard filtering.
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Remove 'hooks' functions, and Split out USRN handling to its own object.
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
Add an update with each report closure.
|
|/ /
| |
| |
| | |
This makes it clearer what is being shown.
|
| |
| |
| |
| |
| | |
Our fork was merged upstream.
This reverts commit 77d4d709.
|
| | |
|
|/
|
|
|
| |
When running on a Mac, the dev server only
watches changes to directories, not files.
|
|\ |
|
| |
| |
| |
| |
| | |
The code for moving a report to the intermediary state was running
even if the report was in a closed state and had not been changed.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Plus remove some now-unneeded CSS.
|
| | |
| | |
| | |
| | |
| | | |
If you rotated a photo, updates and the category list weren't loaded. If you
changed a report's state, the map pin colour was derived from the old state.
|
| | | |
|
| |/ |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 5px cellpadding on the wrapper table was resulting in 15px of white
space either side of emails when viewed on narrow screens. Which, on a
window that could be as narrow as 320px, is a lot of wasted space!
We only wanted the 15px of horizontal padding to be removed from the
sides of the "main" content, leaving the top and bottom "hints" with
some padding so that their text doesn’t crash up against the edge of
the window on narrow screens.
The easiest way to achieve this was to split the top and bottom "hints"
out into their own slightly wider tables, with built-in cell padding.
To make things simpler, the min- and max-widths are now stored in
variables, and the changes also meant we could simplify the media
queries controlling mobile breakpoints in modern email clients.
Fixes #1928.
|