| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |\ \
| | |
| | |
| | | |
'2016-uk-green-banner-position-test' and '2021-uk-homepage-intent-experiment'
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Present "report" vs "browse" choice at time of postcode entry, so we
can track intent, as part of a temporary experiment into what people
expect to see on the fixmystreet.com/around page.
Google Analytics will be able detect which button was pressed by
looking for the `intent=report` or `intent=report` query string param
in the resulting pageview location.
We supply a *third* submit button, immediately before the other two,
and hidden from visual users and assistive devices, to prevent either
of the "intent" submit values being sent when the user submits the
form via the Return/Enter key.
Part of #2021.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
On PRs from external forks, it won't be.
|
| | | |\ |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Store if the report/update was created by someone using the contributed-as
dropdown, and use that information to perhaps not send report-sent emails.
|
| | | | |
| | | |
| | | |
| | | | |
Part of #2016.
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Data collected by #2001 has shown that some people are clicking the big
green "Click map to report a problem" banner on fixmystreet.com/around.
We assume the same is true for other cobrands.
As suggested in #2016, this commit adds a click handler to that banner
element, which will begin a new report at the centre of the screen. It
might not be the exact right location, but the pin can be repositioned
from the /report/new form, and beginning a report is better than just
soaking up the click and doing nothing.
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
I don't think this check could ever have worked, because items are invisible
if their parent is set to `display: none`, so it would hide the links bar if
it was already hidden, and show it if it was already shown.
Use a js- class for the movement of the feed item into the sub map links.
|
| | | | |
|
| |/ /
| |
| |
| | |
Then it can skip working out some things as they are not needed.
|
| |/
|
|
| |
The change to base in fc172603 affected the layout display.
|
| | |
|
| |
|
|
| |
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.
|
| | | |/
| |/| |
|
