blob: e39c3f0c53b084d77f5c021cfc12a389b01cb7e2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
---
layout: post
title: Version 2.4.1
author: matthew
---
<div class="r" align="right">
<a data-flickr-embed="true" href="https://www.flickr.com/photos/bradhoc/6341956589/" title="Docks"><img src="https://farm7.staticflickr.com/6097/6341956589_97f39d3f3b.jpg" width="500" height="304" alt="Docks"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script>
</div>
Today we have released **version 2.4.1** of FixMyStreet.
This release contains a wide variety of new features for use by reusers of our software,
funded by [NDI](https://www.ndi.org/) as part of their FixMyCommunity project; thanks
very much to them. It also includes a number of smaller features and bugfixes.
FixMyStreet now comes with a Dockerfile and example Docker Compose setup for
use by those tools, and we provide a hosted Vagrant box that can be used also.
You can choose to store photos in Amazon S3 rather then the local filesystem,
use an external memcache server,
We've added a script, `cobrand-checks`, that will list/diff template changes in core
that might need applying to a cobrand, to help with upgrading, and added more checks
to our Pull Requests on GitHub to spot included cobrands that need checking with each
PR made.
We have sped up fetching full lists of bodies to help installs that have
thousands of bodies, sped up the display of `/_dev` pages, fixed the display of
pins on a body page when using Bing or TonerLite maps, and fixed an issue where the
`from_body` field was lost on a user when edited by a non-superuser admin.
[Full changelog](https://github.com/mysociety/fixmystreet/releases/tag/v2.4.1)
|
