| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | |
| |
| |
| | |
This was causing layout issues on the Lincolnshire cobrand.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Allows cobrands to customise message displayed, and includes
description in GeoJSON feature properties.
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Bing no longer shows it at zoom level 11.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #2016.
When you load a page that includes either a problem report, or is
centered on a location, the "Report a problem" button in the nav bar
(that normally takes you to the homepage) becomes a "Report a(nother)
problem here" button, that leads directly to the new report form
for the location in question.
On full map pages (/around and any /report/<id> pages loaded via it)
the reporting form will be rendered client-side, avoiding a full page
reload.
On pages lacking the full map (eg: missing fixmystreet.bbox_strategy),
namely /reports/<area> and any /report/<id> page that hasn’t been
client-side loaded via /around, we fall back to a server-side page load.
Finally, as you’d expect, the text and URL for the button dynamically
update as you move around the map, or switch between the different
client-side states of the reporting flow.
We also hide the button entirely when you’re reporting a problem,
which was something suggested a long time ago.
|
| | | |
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| | |
Part of #2012.
Should make it much quicker to report multiple problems in the same
location, one after the other.
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Allow flytipping reporting on cobrand and .com, with road reports going to
Bucks Confirm and email, and non-road reports going to district and Bucks
emails.
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
If an inspector clicks on a report from an around page the code to setup
the pin dragging needs to be called. This adds a method to the map to
allow the setup code to be called on report load.
Fixes #2073
|
| |/ /
| |
| |
| | |
Fixes #2197.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| | |
A move between fixed states (presumably from fixed-user to fixed-council)
should not count as a state change for the purposes of generating comment
text from templates.
|
| | |
| |
| |
| |
| |
| |
| | |
Asset layer visibility depends on fixmystreet.bodies, which is updated from
ajax request by pin selection or category change, but the visibility change
happens before the ajax request - so if visibility is not also checked when
category_extras returns it can get out of sync.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
add a do_not_send parameter to reports which allows the front end to specify a
comma separated list of bodies that reports should not be sent to even if
there is a valid contact match. This enables asset layers to override backend
body processing, e.g. if a body only accepts reports that are on a road this
allows the front end to specify that.
|
| | |
| |
| |
| |
| |
| | |
is_only_body() checks if the supplied body is the only one listed in
fixmystreet.bodies and hence if it's the only one that reports for
the current pin position will be sent to.
|
| | |
| |
| |
| | |
currently will show even if it's only appropriate for one body
|
| | |
| |
| |
| |
| |
| |
| | |
Also add body name to layer defaults, so they are only used where appropriate.
Switch mapit area javascript calls to GeoJSON, so we can drop KML support in
OpenLayers.wfs.js which saves a small amount of bandwidth.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Return a list of associated bodies on around/new pages and in category ajax
calls, and use that when deciding whether to show/hide layers. If the layer
has no body information, then we show it as before, maybe based on category
selected; if it does, it is only shown if the layer body matches the bodies
for the point.
As part of this create a new VectorAsset class to handle all the visibility
changes for asset layers as it makes it a bit tidier.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2180.
Input placeholders are a generally problematic UI convention, and we’ve
accidentally started using them in more and more parts of FMS over the
last few years.
In some cases, the placeholders simply repeated text from the input’s
existing label element. In cases like those, the placeholder attribute
could just be removed.
In other cases, we broke the placeholder text out into a .form-hint
element, between the input and its label, so that the text is easily
accessible and falls into the top-to-bottom reading flow.
Notable changes:
* Form hint on main postcode search form, instead of placeholder.
* Form hint on alert search form, instead of placeholder.
* Form hints in reporting form (problem summary and description),
instead of placeholders.
* Removed placeholders from most login/password inputs.
* The character limit for "Inspector" report updates is no longer
displayed in the textarea placeholder.
* Form hints now `#666` grey, and better spaced when immediately
following a label element.
|
| |
|
|
| |
[fixmystreet.com] Update to use OS OpenMap Local tiles.
|
| | |
|
| |
|
|
| |
Removing this while we sort out the process.
|
| |
|
|
| |
This reverts commit 6bc39892d7075fac79c0f40b2740de095535329d.
|
| | |
|
| |\
| |
| |
| | |
'origin/issues/commercial/1087-dashboard-csv-download-teaser'
|
| | |
| |
| |
| | |
Fixes mysociety/fixmystreet-commercial#1087.
|
| | |
| |
| |
| | |
Fixes mysociety/fixmystreet-commercial#1104
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Users who double click links were seeing an error when visiting the
questionnaire page. This change gives a grace period of two minutes
for revisiting the questionnaire page.
Fixes #2123.
|
| | |
|
