| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
| |
This is shown when reporting and in map list filters.
|
| |
|
|
|
| |
Both filter categories and new report category lists went through mappings
to different data structures, which doesn't seem to be needed.
|
| |
|
|
|
| |
Only the contacts table gets a button added to toggle the display
of deleted rows; elsewhere the rows need to continue to be shown.
|
| | |
|
| |
|
|
|
|
| |
This updates the privacy policy with changes for the incoming GDPR.
Fixes #1900
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since #map_sidebar no longer disappears behind #site_header, there is
no need for .internal-link-fixed-header to compensate for the height
of the header. Just an arbitrary 2em offset is enough to prevent it
butting up against the top of the #map_sidebar scrollable element.
Meanwhile, moving the .internal-link-fixed-header anchor element to
the top of its parent list item means it no longer has to compensate
for the height of the moderation form elements, because those elements
(indeed, the entire list item <form>) now comes *after* the anchor.
Fixes mysociety/fixmystreet-commercial#1027.
|
| |
|
|
|
| |
Some Open311 servers will refuse an update with a
timestamp earlier than one it already received.
|
| |
|
|
| |
Otherwise we may not warn on otherwise skipped updates.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The easy thing first - IE appears to 'stack' :before entries, so if a
stylesheet is loaded multiple times (e.g. due to critical CSS loading
on the front page), a font-size of 2.5em gets multipled. Switching to
rems fixes this.
The preload polyfill in IE8/9 loads the base stylesheet as if it were
after the layout stylesheet, which breaks the navigation display. The
polyfill has a new version which is somewhat simplified, updating the
existing <link> rather than creating a new one, so we upgrade to that
plus a PR to prevent browser hanging.
However, in IE8 this now incorrectly uses the print styles on screen,
meaning the navigation and footer disappear. So use an IE conditional
comment to just cut IE8 out entirely. This means we can also cut down
the polyfill somewhat.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This is already defined in fixmystreet.utils further up.
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
So that you can build functionality to add extra limitations on
to the map pins displayed. Useful for Collideoscope initially
to filter out (or in) reports from the Department of Transport's
Stats19 Data.
|
| | | | |
|
| | |/
|/| |
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
If no text, photo, or state change, hide the update from display.
|
| | | |
| | |
| | |
| | | |
Fixes mysociety/FixMyStreet-Commercial#1024.
|
| |/ /
| |
| |
| |
| |
| |
| | |
If a new user registers during the report/update process
and their password starts or ends with whitespace or has
consecutive whitespace chars then those would be stripped
and the entered password wouldn’t work for subsequent logins.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous approach of requesting a small bounding box from the
WFS server and using the first asset, if any, wasn’t sufficiently
tolerant of reports that were made more than 5M away from a road,
of which there were many. The problem with extending the bounding
box used to fetch assets from the server is that the order of the
returned assets didn’t have any bearing on their proximity to the
centre of the bounding box (i.e., the location of the report). As
an alternative approach this commit changes the method to instead
fetch all assets within a much wider bounding box surrounding the
report and iterates across the returned features in order to find
the closest point and uses the site_code value from that feature.
|
| |/
|
|
|
|
|
|
| |
Instead of just a Yes/No display a formatted list of values in extra.
Has special handling for known fields otherwise just prints them out
dumbly.
Fixes #1809
|
| |
|
|
|
|
|
|
|
| |
Previously send-comments errors would only be printed the first time
they occurred so there was no visibility of ongoing errors. This brings
send-comments in line with send-reports by emitting errors if the script
is called with --verbose.
Fixes #2091
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
This makes it easier to override them.
|
| | | |
|
| | |
| |
| |
| |
| | |
One to alter the category after initially set, one to change
any details of the report before saving to the database.
|
| | | |
|
| | |
| |
| |
| |
| | |
This allows a cobrand to e.g. display a subset
of bodies based on a query parameter.
|
| | |
| |
| |
| | |
This allows a cobrand to categorise the reports however it wishes.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Add a more helpful error message when a problem fetched over Open311 is
rejected for problems with the date.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This hopefully works around some odd test failures on Travis.
|
| | |
| |
| |
| |
| | |
This also moves the 'this will be public'
text next to the fields it applies to.
|
| | |
| |
| |
| |
| |
| |
| | |
Response templates won't be triggered unless the problem state or
external status code is changed.
Fixes #2075
|
| | |
| |
| |
| |
| |
| |
| | |
If JavaScript is enabled hide the deleted contacts from the list on the
body page. Display as normal if no JavaScript.
Fixes #1962
|
| | |
| |
| |
| |
| | |
It’s not quite a ‘radius’ as it’s a square box, but this does
bring it closer in line with the cobrand JS behaviour.
|
