| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
- Apply Confirm validation rules
- Add admin_user_domain and Confirm-required open311 fields
- Prefix Open311 updates with notice that it’s come from FMS
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This is no longer needed on tilma-served layers since we have upgraded to MapServer 7.
A side-effect of using the MultiCurveFix format_class was that it
implied the use of GML v3 as that was its base class.
This commit sets the default format_class to OpenLayers.Format.GML.v3,
which is required to parse the GML v3 responses from tilma.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
It's possible an asset has been selected before a category (e.g. if
assets are showing for a whole category group. So on category change,
make sure we check if any attribute fields need setting/clearing.
|
| | |
| |
| |
| |
| |
| | |
An assets:selected event is always accompanied by a maps:update_pin
event, which is already being listened on. Reorder the asset selection
so the event still occurs before any attribute field setting.
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
| |
sortable() returns undefined if no elements match, so on admin pages
that weren't the contact editing page a TypeError was being thrown by
the [0] line which resulted in the debug toolbar not being shown.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
As there are two category drop-downs in this situation (one in the
hidden reporting form, one in the inspect form), the correct entry
needs to be specified.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
An upgrade to Bristol’s server means this will need to be requested.
|
| |/ |
|
| |\ \
| | |
| | |
| | | |
'2469-fancy-admin-category-form' and 'fix-missing-body-message-flash'
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Much simplified display of metadata field options.
* Fields can now be dragged into the desired order.
* Drop-down question form disabling can now have
a different message per option.
Co-Authored-By: Matthew Somerville <matthew@mysociety.org>
|
| |/ / |
|
| |/
|
|
|
| |
Change the tilma url based on whether we are using the live or staging
site.
|
| |\ |
|
| | |
| |
| |
| | |
Co-Authored-By: Zarino Zappia <mail@zarino.co.uk>
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The base layer does this transformation,
so I am not sure what this was for.
|
| | | |
| | |
| | |
| | | |
Make it a bit more obvious that something has been selected.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On reports with a state of `for_triage` override the `_inspect.html`
template to display one which allows only allows the user to change the
category from one with a 'Triage' send_method to a non Triage
send_method.
When saved this records a comment with the original category and the
category it was triaged to. This is hidden from the site as it's only
used for audit purposes and sending over Open311.
This assumes that the triage categories have the same names as the
groups of the confirm categories. It uses this to select the first
confirm category in the group corresponding to the triage category.
This also makes the sidebar geolocation onclick handler check for the
presence of the button, as the triage inspect form does not have it.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This uses the Triage categories as the category names and uses the
associated groups to make sure the assets are displayed to staff users.
There is a default streets layer as a fallback for site_codes.
Some of the categories include both line and point assets so the line
assets have `display_zoom_message` in order that both show the details
of the currently selected asset.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
we want the road layers to be able to show the zoom/pick a thing/you
have picked a thing message so add a `display_zoom_message` config
option to override the `non_interative` option. We don't want to remove
the `non_interative` option as otherwise item selection hides the pin.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
check for a `fixmystreet.stopper_after` property and if present insert
the stopper element after the category extra to allow for layout
preferences.
|
| | | |
| | |
| | |
| | |
| | | |
for assets layers where we have both line and point assets it's not
helpful to have the snap threshold be very large.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change the way we set the BBOX strategy for the map layer as otherwise
when we check for bbox_strategy in display_around this is set but has
not been associated with a layer so .activate fails.
|
