| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
Cobrands might include the fields elsewhere, e.g. in moderation.
Also only use 6 decimal places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the "Report a problem" link in the nav bar links, more often
than not, to the reporting form rather than the homepage, it could be
challenging to actually start a new report in a location *other* than
the one currently on screen.
Rather than adding a link to the homepage, this change hopefully adds
a link right at the moment the user expects it – right on the "Report
a problem" form.
It also gave us an opportunity to reword the "Wrong location" message
and give it an icon more suitable for high-dpi displays.
Fixes #2238.
|
|
|
|
| |
This reverts commit ee3c4e05daf3f4df01762ead3d07697a12f13a28.
|
|
|
|
| |
use symbol code to limit the types of roadworks that show.
|
|
|
|
|
| |
use the filter option to only display roadworks message for road related
categories
|
|
|
|
|
| |
add a `fixmystreet.roadworks.filter` option which cobrands can override
to control when the message is displayed. e.g. limit by category.
|
|
|
|
| |
Uses same parsing of roadworks messages as Lincs
|
| |
|
|
|
|
|
| |
Previously if there was a mix of groups and top-level categories
they weren’t sorted together.
|
|\ |
|
| |
| |
| |
| |
| | |
Anything using old names should still work as long as they included the
mixins file.
|
|/
|
|
|
| |
As well as the original form using #form_photo, add
Dropzone to any form with a .js-photo-label in it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If /report/new is opened directly then the fixmystreet.reporting_data is
not set, but the categories are already in place. These are then
replaced when update_pin is called. If this has been triggered by
clicking on a category with a subcategory this replaces the category
selects but did not correctly reset them. By saving any selected value
in the main category select we can correctly reset this and hence the
display of the subcategory select.
Fixes #2276
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the "Report a problem" link in the nav bar links, more often
than not, to the reporting form rather than the homepage, it could be
challenging to actually start a new report in a location *other* than
the one currently on screen.
Rather than adding a link to the homepage, this change hopefully adds
a link right at the moment the user expects it – right on the "Report
a problem" form.
It also gave us an opportunity to reword the "Wrong location" message
and give it an icon more suitable for high-dpi displays.
Fixes #2238.
|
|\ |
|
| |
| |
| |
| | |
So version 2.4.1 has no translation changes, putting back straight after.
|
|/
|
|
|
| |
Adds some div wrappers round the non category bit of the form so we can
then hide easily.
|
|
|
|
|
|
| |
replace_query_parameter() was stringifying select multiples, meaning
they were incorrectly recorded by the pushState and thus breaking on
navigation.
|
|
|
|
| |
Fixes mysociety/fixmystreet-commercial#1131
|
|
|
|
|
| |
The change to web/js/front.js was required because Oxfordshire has no
`.report-a-problem-btn`, so the front.js shouldn’t assume it’s there.
|
|
|
|
|
|
|
|
|
|
|
| |
The large negative text-indent can sometimes cause horizontal scrollbars
in Right-to-Left languages, and, in some browsers, can also result in a
huge :focus outline being drawn around the button and off to the right
of the window.
Setting a zero height, padding top, and overflow:hidden is a simpler
way to achieve the same thing, and works regardless of text direction,
text length, or focus state.
|
|
|
|
| |
There is no need for #front_stats to always be nested inside of #front-howto.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the "Report a problem" link in the nav bar links, more often
than not, to the reporting form rather than the homepage, it could be
challenging to actually start a new report in a location *other* than
the one currently on screen.
Rather than adding a link to the homepage, this change hopefully adds
a link right at the moment the user expects it – right on the "Report
a problem" form.
It also gave us an opportunity to reword the "Wrong location" message
and give it an icon more suitable for high-dpi displays.
Fixes #2238.
|
|
|
|
|
|
|
| |
Works for both the "Report" button shown in the mobile header,
and the "Report a problem" span on the desktop site.
Thanks to Louise for suggesting this in mysociety/collideoscope#42!
|
|
|
|
|
|
|
|
| |
Some cobrands (like Collideoscope) don’t have a .report-a-problem-btn
in their mobile nav menu, so .querySelector() would raise an exception
when we tried to attach an event listener to it.
Now we check that the element exists before attaching the listener.
|
| |
|
|
|
|
|
|
| |
We needed this for Collideoscope, where we’re displaying small bar
charts on the Statistics page, and the default bar height of 30px
was much too small when the chart was reduced in size.
|
|
|
|
| |
Couple of texts have newlines in them, and may change anyway.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Collideoscope doesn't have fixed reports so only add a line for fixed
reports if there is data.
|
|/
|
|
|
| |
Avoid a JS error if a line graph has no points. This is mostly useful
for collideoscope where we only want to show one line.
|
| |
|
|
|
|
|
|
| |
Sending to Bucks reports made on non-Bucks roads was only disabled if
Bucks was the only body concerned; flytipping is a concern of both
tiers, but reports on non-Bucks roads should still not be sent to Bucks.
|
|
|
|
| |
GeoJSON is used by the /reports page now, not KML.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
It is possible to get here on e.g. a /report/new page load where the
asset is being shown but hasn't yet been added to the map.
|
| |
| |
| |
| |
| |
| | |
Confusion over client/server side filtering meant Bristol was filtering
client-side on an attribute it was not asking to be returned by the
server.
|
|/ |
|
|
|
|
|
|
| |
Add by_category output to the /report/new/ajax call, containing all the data
that /report/new/category_extras returns for one category. Then alter the JS
to use that data immediately when needed.
|
|
|
|
|
| |
If a layer doesn't have attributes the set_fields_from_attributes
function dies because $.each doesn't like undefined things.
|