| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
We do not want to recategorise a report into the off-road
category if it is going to be sent to Highways England.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
If switched on, sends first five letters of the SHA1 hash of the entered
password to HIBP's API, which then returns all matching hashes in their
database of breached passwords. If we find a match, tell the user they
need to pick a different password.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
This is a current full list of extra keys that could be set on a report
that could confuse the moderation diff display.
|
| | | |
|
| | | |
|
| |/
| |
| |
| |
| | |
As string_diff is used in hash values, it must always return something,
otherwise you could end up with e.g. category => 'extra'.
|
|/
|
|
|
| |
Sort the table when showing search results, and show users
without name at the bottom, rather than at the top.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If we create one category_meta_message for each category, removing when
not relevant, then duplicat suggestion showing leads to duplicate
messages because the layer is still relevant, just not visible, and so
the old layer message is not removed. Instead, repurpose the ID of any
existing category_meta_message, so there is only ever one in existence.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This simplifies the code wherever used.
|
| |/
| |
| |
| |
| | |
Make GetUpdates and GetServiceRequestUpdates share a common base;
spot all visible states.
|
| |
| |
| |
| |
| |
| | |
Because Hackney doesn't have any matching categories for TfL red routes
skip sending the body, otherwise you get a "no contact details" message
when you click on a red route in Hackney
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
For some reason the BBOX query would return results that weren’t
actually intersecting the BBOX causing false positives and misdirected
reports.
This change uses the Intersects query instead which is more
accurate.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
- Cobrand config can now specify custom scope and other params
e.g. G Suite supports per-domain customisation and the ‘prompt’ param
to always ask the user to select the account they want to login with.
- Token may have an ‘name’ claim instead of needing to concat given_/family_name claims
|
| |
| |
| |
| | |
Turns out there’s nothing strictly Azure-specific about it.
|
| | |
|
| |
| |
| |
| |
| | |
Adds ability for categories to be marked as devolved with their own
send_method, and for the open311_protect flag to be set.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Also bumps up default zoom level a couple of notches
For https://github.com/mysociety/fixmystreet-commercial/issues/1760
|
| | |
|
| |
| |
| |
| |
| |
| | |
Co-Authored-By: Struan Donald <struan@exo.org.uk>
For https://github.com/mysociety/fixmystreet-commercial/issues/1808
|
| | |
|
| |
| |
| |
| |
| | |
Mostly inherits from original Alloy code, with addition of a new format
as Alloy no longer returns a native geoJSON collection.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use Dropzone (the photo upload library) to shrink photos client-side
before uploading in the background and display thumbnails. For the
resized upload, Dropzone restores the original Exif data, including
orientation, so it can be correctly oriented server-side; for a
thumbnail, it orients the image itself for immediate display.
Recently, browsers have started honouring Exif orientation much more
widely (Chrome 81+ and Firefox 77+ both now do it by default). This
means the data Dropzone gets from a resize has already been oriented
according to the Exif orientation data. Then Dropzone either looks at
the orientation to correct for display (thumbnail), or adds back the
Exif orientation data (upload) – in both cases, this leads to a double
implementation of the orientation, and an incorrect display.
To fix this, if we detect we are on a modern browser, we do not try and
fix orientation ourself [1], and in all cases we do not add any Exif
data back in (we only strip it server-side anyway). Conversely, that
means on a non-modern browser, we always perform a manual orientation
because no Exif data will be being sent server-side.
Also includes a fix to the orientation code [2] which wouldn't be
noticed in thumbnail generation as they are square, but could be now we
may be orienting full size photos.
[1] https://gitlab.com/meno/dropzone/-/merge_requests/80
[2] https://gitlab.com/meno/dropzone/-/merge_requests/45
|
| |
| |
| |
| | |
In my Firefox on Windows, .jpeg files are not otherwise shown.
|
|\ \
| |/
|/| |
|