| Commit message (Collapse) | Author | Age | Lines |
... | |
|\ |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
form_heading.html was a misleading name for a partial containing the
optional message that some cobrands display after the reporting form
title, so we’ve now renamed it to make it clearer. This also allowed
us to spin out the actual “Report your problem” heading into its own
partial template, called form_heading.html.
|
| | |
| | |
| | |
| | | |
We retain the code as it is updating the URL on map move.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When an open311 category has multiple groups it puts them in the groups
element using CSV escaping. This means that group names can sometimes
feature double quotes. If we send these to the front end then putting
them into the optgroup name attribute breaks the HTML as if the group
name is in the database as `"group name"` you end up with
<optgroup name="" group="" name="">
instead of
<optgroup name="group name">
Hence, stripping the double quotes.
|
| | |
|
|\ \ |
|
| | | |
|
| |/
|/| |
|
| | |
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
The request cobrand is set on the schema during the app's
setup_request(), which is called by the root auto action.
So anything in a controller's begin action will access an
incorrect cobrand (if one has already been set).
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the coordinates are (0,0) then return that straight back as trying to
reproject causes Geography::NationalGrid::GB to fall over as 0 lat is
outside UK
Fixes #2617
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Fixes a bug that appears to have been introduced in edf8456, where the
RSS icons on the /alert page were being stacked behind the relatively
positioned form labels, making them unclickable.
While I was there, I also standardised the markup for all three RSS
images to use the translatable alt text and double quotes for the HTML
attributes.
Fixes #2624.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Fixes test suite failures in new Vagrant environments.
See also: #2487
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This improves the reporting journey to only ask for category,
and then category extra questions if appropriate, first, so that
if the choice would lead to the form being disabled, this can
be shown immediately.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In non-JS scenario, this means you must enter email in both boxes to
continue. JS still makes it required appropriately when available.
|
| | |/
| |/| |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The extras may be a confusing stopper message that only applies to the
'main' body, or it may be extra questions that are now not required.
Either way, we should hide this information, and we need to make sure
the server no longer checks if required extra questions have been
answered.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was previously restricted to coming directly to /report/new, but
this meant it wasn't being run when e.g. Buckinghamshire winter routes
or Westminster TfL roads were being loaded after the appropriate
category selection, so their effects did not occur (as the checkFeature
code was called prior to the layer finishing loading).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The stopper check runs first, which could mean that if the asset layer
has not yet loaded, the form is disabled when it should not be (e.g. on
a TfL road in a road category). Make sure that we always run the stopper
check after the TfL layer check, in case it changes something.
|
| |/ |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
If a body was set to Open311, and a contact set to Email, it was
impossible to unset the contact's send method and set an Open311
code, because it would always demaned a valid email address.
|
|/ /
| |
| |
| |
| |
| | |
It's still not working as expected, with lots of rejected reports.
This reverts commit 49c74ded4275005e766a948ec47d4cc722e0567e.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
| |
Note how in road_not_found, the Highways England check could never pass
because the only_send was being removed the line before. When the
Buckinghamshire and Northamptonshire code was factored together, it
looks like bits were taken from one that weren't present in the other,
and so should not have been present in the shared code.
|
|
|
|
|
| |
Any message being included there will be for the appropriate council and
not relevant.
|
|
|
|
| |
Not sure how this has not arisen before!
|