| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | | |
|
| | |
| |
| |
| | |
Fixes #2331
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Fixes #1649.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Currently keeping the same front end functionality of only reverting to
the original.
|
| | | |
|
| |/ |
|
| |
|
|
| |
To avoid adding a new, but identical translation
|
| |
|
|
|
|
|
|
|
| |
use the bodies array of reporting_data to check if there is council
specific javascript validation and, if so, load that into the JS
validation rules.
This does mean we reset the validation rules each time you select a
category.
|
| |
|
|
|
|
|
|
| |
Some of these were occasional failures due to timing issues.
One was due to a hard coded body id meaning the addition of bodies in
other tests meant this was creating two bodies with the same id, which
happened to be used in a test which depended on the bodies having
different ids.
|
| |
|
|
|
|
| |
`report_check_for_errors` now fetches the cobrand for the current report
and, if present, runs `report_validation` method from cobrand over the
report.
|
| |
|
|
|
|
| |
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.
|
