| Commit message (Collapse) | Author | Age | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| | |
The export flow and the admin search request more data
from the database than they need, which slows it down.
|
| | | |
|
| |/
|
|
|
|
| |
If the web param is used, show an error web page rather than the normal
plain text output. Also do the normal remember/show uploaded photos
feature, and hide the inputs better if unneeded.
|
| |\ \
| | |
| | |
| | | |
'2962-pin-move-category-group' and 'move-admin-index-stats-to-stats-page'
|
| | |/
| |
| |
| |
| | |
These stats can take a while to generate, and we don't want to slow
down people mostly coming to the admin index to do something else.
|
| |/
|
|
|
|
|
| |
Adds a new tickbox to the contact editing form that protects the category
and group names from being changed by Open311.
For mysociety/fixmystreet-commercial#1776
|
| |
|
|
|
| |
Restrict cobrand to HE categories. Want to do it by body, not category,
because otherwise there's a "missing" council body.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
On an around page on the HE cobrand, both bodies (HE and council) are
listed and so when you clicked the map (not on a HE road) the not-HE
code did not fire because it wasn't the only body present. But New.pm
calls only return the HE body because they call munge_report_new_bodies.
So it worked when you picked category/ moved pin. Around should call the
munge function too so bodies is set up same as on New.pm.
We need to always use the cobrand package, regardless of if it is a
valid cobrand or not (for e.g. Bromley/Hounslow tests).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Make it a bit easier to see if any reports have been sitting unsent for
some time
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
If you submit the non-JS image map from an around page with a particular
category selected, that is sent to the server in filter_category and
should be checked to see if we can pre-fill the category dropdown on new
report.
|
| |\ \ |
|
| | |/
| |
| |
| |
| | |
This state will appear when reporting if you are logged in as a staff
member of the relevant body, but otherwise not appear on the site.
|
| | | |
|
| | |
| |
| |
| | |
This saves hammering the FS for every front page request
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
If a SQLite file exists at `../data/analytics.sqlite` with a table
named `location_searches_with_no_results`, then a row will be created
for each /around search that returns no results.
Could come in useful for anybody running an instance and looking to
better understand how well their geocoder is performing.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, you can safely add the TfL body to other councils
(namely the ones surrounding London that include TfL bus stops);
clicking in those councils on other cobrands will have no change, as the
TfL body will be fully ignored on a non-London council, but on the TfL
cobrand it will allow it for e.g. the selection of bus stops outside
London.
It removes the body rather than just all its categories to prevent a "We
do not have details of the other body covering this area" message
appearing.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This basic service worker behaves identically to the existing appcache -
some static scripts and CSS are cached, any HTML offline instead returns
a static HTML page that knows how to show data on stored problems out of
localStorage (stored there when /my/planned was visited online). Inspect
form submissions will be captured and can be synced back when online.
Once feature parity is established, we will then remove appcache, switch
from using localStorage to the cache API, and hopefully move all offline
support into the service worker.
|
| |
|
|
|
| |
Reads information from a theme object if present, and icons from a
theme directory, with fallbacks.
|
| |\ |
|
| | | |
|
| |/
|
|
|
| |
Use a token that does not log the user in, but lets the report be shown,
even if it's a private report. Allow old tokens of that type to work.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Attempting to load the /report/ajax/<id> URL for a problem that
had a public response and wasn't in the ‘external’ state was causing
a crash because the call to FixMyStreet::App::View::Web::add_links
in updates_as_hashref was returning a FixMyStreet::Template::SafeString
that the JSON module didn't know how to serialise.
This commit adds a TO_JSON method to SafeString, and ensures the output
of /report/ajax is JSON-encoded with convert_blessed turned on so the
TO_JSON method is called.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Historically, the FixMyStreet admin was accessed via HTTP Basic Auth and
a secure proxy, so the auth user was used for logging purposes. Nowadays
all admin use is by FixMyStreet user, and any Basic Auth is used for the
purpose of hiding staging sites from bots. This configuration means that
on those staging sites, all admin is logged by the one staging user, not
the actual user, so let's swap that round.
|
| |/
|
|
| |
For #2668.
|
| |
|
|
| |
Includes an updated version of jquery-multi-select.
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
This changes the existing logic to account for the fact that multiple
questions might have the disable form checkbox ticked for one of their
options.
At the moment this just displays one of the messages at a time, with the
first one taking priority. So if you have a "Is this an emergency"
question and a "Is this on private land" question which both disable the
form, and the user has selected "Yes" to both, then only the message for
the first question is displayed. This can potentially be improved in the
future, but seemed out of scope for this change.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Includes a bit of refactoring of PhotoSet::get_image_data to make
it easier to call subsequent methods on the photo object. We then
do this to get the width and height.
Also adds width/height attributes to FixMyStreet::ImageMagick
Attributes are updated every time the image is transformed and before
the as_blob data, which also undefs the image, is returned so it always
present for subsequent calls.
Fixes #2394.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
If we wait until after to filter the contacts and the constructed
options, then we can end up in the situation where e.g. we've filtered
out all the TfL contacts but the category option is still the TfL one
(with its associated group).
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some contacts (e.g. TfL) don’t have a valid email address but aren’t Open311
categories - the email destination is managed via the borough_email_addresses
feature. This prevents any changes to the contact being made via the admin
due to the email validation error message.
This commit updates the logic to only check that the email address is valid
if it’s been changed from the existing value (which may be blank if a it’s a
new contact).
Fixes https://github.com/mysociety/fixmystreet-freshdesk/issues/108
|
| |\ |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
These categories display a ‘please ring’ message and so
have nowhere to be resent if selected.
|
| | |
|
