| Commit message (Collapse) | Author | Age | Lines |
... | |
|
|
|
|
|
| |
The EmailUtil library expects "\n" line endings, otherwise it gets
confused. It also doesn't handle a different SMTP port, and so on.
We also make sure the return path is chomped.
|
|
|
|
| |
Fixes #2294
|
| |
|
|
|
|
|
| |
This should reduce the incidence of the ‘Problem id X for Y has an
invalid time, not creating’ cron errors we’ve been seeing.
|
|
|
|
|
|
|
| |
If set then when the user creates a new body report it will prefill the
report title and description with some basic text.
For mysociety/freshdesk#23
|
|
|
|
|
|
|
| |
If a user has this permission then the report_as dropdown will
default to reporting as the body.
For mysociety/freshdesk#23
|
| |
|
|
|
|
|
|
| |
This changes the projection from EPSG:3857, which is not included in the
bristol openlayers build, to the identical EPSG:900913 which is, so that
the conversion happens.
|
|
|
|
|
| |
Do not hide the report form if you click on a non Bucks road that is
managed by Highways England.
|
|
|
|
|
|
|
| |
Includes an option to send to the council instead for e.g. reports on
underpasses or bridges.
Fixes #736
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(This might well have been done client-side by Dropzone.)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Allows user's to see the inspector panel to mark reports as Private, and
also to view those non-public reports. Useful for call centre staff who
want to record private reports but don't need to other permissions.
Fixes mysociety/fixmystreet-commercial#1213
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Given recent changes to the button mixins, now is a good opportunity to
clear out some overcomplicated button styling from a few UK council
cobrands: Greenwich, Hart, and Oxfordshire.
All three referred to `button.green-btn` elements that don’t seem to
exist any more, and I couldn’t find a reason for the extra specificity
in the `input.green-btn` selectors either.
Oxfordshire’s buttons are drastically restyled from the FMS defaults,
so its button rules are a little complex. But I’ve tried to make the
distinction clearer between buttons we’re having to build from scratch
(.btn, .green-btn, etc) and buttons we’re simply re-colouring.
|
|
|
|
| |
.btn--social doesn't do anything, and neither do the text-transforms.
|
|
|
|
|
|
|
|
|
| |
The intention of .btn--block is to make the element full width. Because
of the weird way browsers handle sizing of form elements, just setting
`display: block` on `<button>` and `<input type="submit">` elements
wasn’t making them full width. Instead, .btn--block needed to explicitly
set a 100% width, and then reset any margins or box-sizing issues that
might cause it to overflow its parent.
|
| |
|
|
|
|
| |
This is so the dev server notices and restarts.
|
|
|
|
|
| |
Cobrands might include the fields elsewhere, e.g. in moderation.
Also only use 6 decimal places.
|
|
|
|
|
|
|
| |
- Group wasn’t being set correctly by open311-populate-service-list as cobrand attribute
not being updated for each body.
- Extra metadata was being persisted to the DB every time even if nothing had changed,
causing lots of duplicate entries in contacts_history.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the "Report a problem" link in the nav bar links, more often
than not, to the reporting form rather than the homepage, it could be
challenging to actually start a new report in a location *other* than
the one currently on screen.
Rather than adding a link to the homepage, this change hopefully adds
a link right at the moment the user expects it – right on the "Report
a problem" form.
It also gave us an opportunity to reword the "Wrong location" message
and give it an icon more suitable for high-dpi displays.
Fixes #2238.
|
| |
|
|
|
|
| |
This reverts commit ee3c4e05daf3f4df01762ead3d07697a12f13a28.
|
| |
|
| |
|
|
|
|
| |
use symbol code to limit the types of roadworks that show.
|
|
|
|
|
| |
use the filter option to only display roadworks message for road related
categories
|
|
|
|
|
| |
add a `fixmystreet.roadworks.filter` option which cobrands can override
to control when the message is displayed. e.g. limit by category.
|
|
|
|
| |
Uses same parsing of roadworks messages as Lincs
|
|
|
|
|
|
|
|
|
| |
The addition of `:3000` to `BASE_URL` is now only made when not using
the FixMyStreet box as this will be supplied in by the `setup` script in
that case. This should also only be applied when not already present to
prevent it being added repeatedly.
[skip ci]
|
|
|
|
|
|
|
|
| |
This adds support in `script/setup` for generating a local `general.yml`
if it doesn't already exist and is run as the `vagrant` user. This is
called from the `Vagrantfile` when using the FixMyStreet Vagrant box.
[skip ci]
|
| |
|
| |
|
|
|
|
|
|
|
| |
This adds a cobrand configuration option for always showing the
body user's name in updates.
Fixes #1860
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Previously if there was a mix of groups and top-level categories
they weren’t sorted together.
|
|
|
|
|
| |
Utility script that takes a time window and an option body name and then
fetches all the comments over that period in 24 hour blocks
|
|
|
|
|
| |
Allows creating scripts that fetch comments for a single body, e.g for
batch updating or because they require special setup.
|
|\ |
|
| |
| |
| |
| | |
If a cobrand provides those fields.
|