Version 2.3.3 6 June 2018
Today we have released version 2.3.3 of FixMyStreet.
This fixes a few bugs found in the past week of the last release, including one potential data leak. It was possible to obtain from a crafted URL the textual content of an update, and the name of the user who left that update (only if they had made the update non-anonymously), even if that update was unconfirmed or hidden. No other details of the update or user were made available.
Other fixes include incorrect behaviour when selecting report pins on mobile, bad admin navigation links in multi-language installs, and an issue with the map display when an inspector clicked back from a report page on mobile.
Version 2.3.2 31 May 2018
Today we have released version 2.3.2 of FixMyStreet.
This is a minor release, but one with quite a number of bug fixes and other smaller front end and admin improvements.
The questionnaire process has been improved, with “Don’t know” now an option in the email, and recording the answer as soon as the link is clicked. Smaller front end fixes include increasing the size of “sub map links” (hide pins, permalink, etc), clicking the “Click map” instruction banner now begins a new report, and improved cursor/display of the new report pin.
Front end bug fixes include improving chart display in old IE versions, a CSS padding bug in the sidebar “drawer”, a race condition when making a new report quickly, some small RTL text display issues, and making sure the loading spinner is always shown when it should be.
We now store a user’s creation and last active times, and have provided scripts so you can use tis new information to anonymize inactive users or reports, email inactive users, and/or close reports to new updates.
At long last, the contents of a report’s extra field is now fully displayed in the admin.
Open311 has had a number of improvements and bug fixes – we can now fetch problems over Open311, send multiple photos via an Open311 extension, and have the ability to have automated attributes that can be filled in but not shown to the user (e.g. asset IDs).
For development, we’ve added an HTML email previewer at
Version 2.3.1 12 February 2018
Today we have released version 2.3.1 of FixMyStreet.
This is a minor release, with a number of bug fixes but also a number of smaller front end and admin improvements.
The site should be clearer when things are loading now, be that on initial page load or when an asset layer is incoming. Our phone number library has been updated, so national phone numbers should be displayed in a nicer format as long as you’ve set the
FixMyStreet now asks for the current password (or sends an email) on password change, sets a minimum password length and checks against a list of commons passwords. Superusers can have optional two-factor authentication to protect their accounts.
We fixed an error in sending
requires_inspectionreports, issues with multiple select-multiples on a page, a questionnaire CSS snafu, showing deleted bodies in the dashboard list, alongside other minor bugfixes.
For staff users, ‘report as another user’ now allows phone number without email, and the inspector form shows any extra fields again.
Admins can now anonymize/hide all a user’s reports, log a user out, or remove a user’s account details. We’ve provided a script to expire old sessions in the database (plus this script can be run with
--initto set up the database for the new “log a user out” feature).
Version 2.3 18 December 2017
Today we have released version 2.3 of FixMyStreet.
The major new feature in this release is adding confirmation by phone text instead of email, via Twilio, to allow optional verification of reports and updates, and logging in.
Alongside that, there have been numerous front end improvements and bugfixes. Front end improvements include paginating reports everywhere, making sure all maps can be expanded on mobile, the pin loading indicator no longer covering the whole map whilst pins are loading, and improved location disambiguation on small screens.
We now support Open311 category groups, and if we fetch updates via Open311, we can use auto-response templates to fill in updates without their own description.
Lastly, the dashboard and statistics have been streamlined and improved, and are all now available under
/dashboard. This now includes lookup by date range, ward, category or state, and the CSV export uses machine-readable dates and is accessible via token-based authentication.
Staff users got a number of bugfixes to their interfaces, including making sure reports could always be removed from your shortlist (even if they’ve switched body), only creating one update when changing category, and making sure the text-only contacts output was indeed text, not HTML.
Version 2.2 14 September 2017
Today we have released version 2.2 of FixMyStreet, with some new features, some bugfixes, and other improvements.
At long last, body and category names can be translated in the admin interface, letting you easily run sites in multiple languages without having to perform various amounts of custom work;
Report states can now be edited (and translated) in the admin interface, if you wish to have different options for the specific workflow of your site. If you want to have a closed state of “object removed”, now you can;
Also through the admin interface you can now add extra fields to be shown in the reporting form, letting you ask custom questions for your installation without needing to edit any code or templates.
All the above improvements were funded by NDI as part of their FixMyCommunity project; thanks very much to them.
Staff users can now create reports on behalf of people anonymously, and have more filters on report list pages; new configuration options allow you to limit your site to logged-in users only, or prevent new users from using the site.
The email alerts page has had some work to improve its clarity, and some work has gone into improving the performance of various pages. Some deep diving into SQL queries led to some notable cases where things could be sped up, and we also found one place (listing nearby duplicate reports for staff users) where the database was being queried at a radius of 1000km, rather than 1km :)
One notable bugfix is if you logged in during the reporting process, or had a server side error, your photo thumbnails weren’t being redisplayed correctly (though the photo itself was stored fine) due to change in the image library we use – everything should now be okay.
Lastly, if you’re developing on the code, we have added a debug toolbar (similar to the Django Debug Toolbar, if you’re familiar with that) which lets you see which templates have been used, what SQL queries have been made, what external requests, and so on. This is automatically enabled when you run the development server.
Version 2.1.1 3 August 2017
Today we have released version 2.1.1 of FixMyStreet, a bugfix release with a few small improvements.
The map in HTML emails is now a link through to the report page, and we’ve fixed a bug causing the wrong pin size to be shown there. We’ve also fixed a bug that could cause a different language from the requested one to be shown on about pages.
Admin improvements include resending reports if changing the category has changed the
send_methodand displaying the reporter’s phone number on the inspector form. Text deleted during moderation is no longer replaced with
Version 2.1 18 July 2017
Today we have released version 2.1 of FixMyStreet, with some new features and a variety of improvements for users and reusers.
New features include allowing users to hide their own name on reports/updates, and a new graph-based /reports page, which you can see in operation on our main UK site. We also now resize photos client-side before uploading, given the increase in very large images these days.
Admin improvements include adding an ‘inactive’ state to categories, so you can prevent a category being used for new reports but still have it available in filters, various improvements to the inspect form and the new report process for inspectors, and an easier way for inspectors to shortlist all reports in their view.
Geolocation is back on the alert page, lost sometime last year, and some random blank spaces are no longer clickable, hooray!
Development-wise, FixMyStreet now supports Debian stretch and perl 5.24, badly configured SMTP options should now be spotted, and we have refactored and simplified the CSS used for header/content/navigation. This may mean you can simplify overrides in your cobrand. If you wish to have a static front page rather than the normal report page, that’s now possible by creating an
about/homepage.htmltemplate in your cobrand, and cobrands can now easily change the new report pin colour.
The test suite now runs each file in a transaction which means it can be run in parallel and sped up dramatically; on the other hand, on Travis we added code coverage which slowed it down again.
Two backwards incompatible changes that may require changes to your own templates if you have customised them:
nav-wrapper-2class has been removed. If you have a custom footer template, replace that class with ‘container’.
/reportspage now uses different generated data. If you have a custom
reports/index.htmltemplate and wish to keep it, you may need to call
--tableargument to generate the old style data.
Version 2.0.4 13 April 2017
Today we have released version 2.0.4 of FixMyStreet, a bugfix release along with a couple of other improvements.
The bugfixes are updating our Facebook library so that Facebook login works again, stopping an error if you had a devolved body and its contact both lacking a send method, and an issue in the multi-select front end if you had characters such as brackets in your category name.
Strangely, while the backend has always allowed multiple email addresses for a contact, separated by commas, the admin interface hasn’t allowed them to be entered - this has now been corrected.
Lastly, body pages under
/reportswill now limit the reports shown to those within the visible map, which should make moving and zooming around much more intuitive.
Version 2.0.3 31 March 2017
Today we have released version 2.0.3 of FixMyStreet, a bugfix release along with some other improvements.
The map on a mobile report page can now be made full screen, and if you are using Google Maps you can supply a custom map styling. There’s also now a loading indicator whilst data is being fetched for the map.
Various missing translations have been added, for moderation, social login, and offline usage.
We’ve upgraded our email sending to deal with issues sending with SSL, dealt with IE11 caching report Ajax calls too aggressively, and with Safari 5/ Android 4 not showing our questionnaire answer buttons.
Lastly, all the test suite can now run offline, and amusingly I found a bug in a test that only happened if the test was run c. 55 hours before daylight savings time began :)
Version 2.0.2 3 February 2017
Today we have released version 2.0.2 of FixMyStreet, a bugfix release along with some new admin improvements.
The main bugfixes are to mark two missing strings for translation, to make sure email is lowercase when signing in via
/auth, and to make sure a language subdomain can be included in calls to
base_url_for_report. There are also some CSS fixes to the homepage and an improved print layout for report list pages. Fixes to the admin interface include fixing filtering on the shortlist page, and fixing the ‘save with public update’ toggle.
For international users, there have been a few string renames, but we have maintained translations as the concept remains unchanged, so please only feel free to update if you consider it necessary:
- ‘unable to fix’ has been renamed to ‘no further action’
- ‘marked as a duplicate report’ has been changed to ‘closed as a duplicate report’
An offline fallback page has been added using appcache, which inspectors can use for offline updating of reports in their shortlist.
Admin improvements include allowing response templates to be associated with a state (so that template is used by default when the state is changed), allowing shortlist addition/removal from report lists, and shortlist reordering. Users with a new permission can see the body user who left a
contribute_as_bodyreport or update.