| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
| |
The gettext-extract script looks for loc() in templates, it did not find
the loc_js() calls.
|
|
|
|
| |
Tweaks due to stopping using HTML entities in a number of places.
|
|\
| |
| |
| | |
'origin/issues/commercial/1659-bromley-shortlist-css-bug'
|
| |
| |
| |
| |
| |
| |
| | |
Brings Bromley more in line with how other cobrands do their button
styling, and also fixes mysociety/fixmystreet-commercial#1659 (where
Bromley’s high-specificity input styles were causing the shortlist
"star" input to display as a regular button).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A couple of small fixes to tidy the output of button-variant() and
make it easier to style up flat, borderless buttons.
* If $bg-top and $bg-bottom are identical, no linear-gradient() will
be generated. Same goes for $hover-bg-top and $hover-bg-bottom.
* If $border or $hover-border are `false`, then it’s assumed you don’t
want a border, and `border: none` will be generated.
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
For some unknown reason the redirect we've had sometimes fails.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removed needless differences, or files where there weren't
really any differences between fixamingata and base.
Also made our site more like base by moving stuff we had in
footer.html to footer_extra.html and stuff we had in
front/recent.html to front/footer-marketing.html.
Should hopefully make the templates easier to maintain.
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| | |
For local testing, we'll now treat a box named `fms-local` as if it
was the Vagrant Cloud box.
|
|/
|
|
|
|
|
|
|
|
|
| |
This adds a script, `bin/install_packages`, that will install packages
listed in versions of `conf/packages*` and calls it from the bootstrap
script in a way appropriate to the environment it is being run under.
This should ensure that, for example, changes to dependencies will be
applied to Vagrant machines in-between tagged releases.
The default packages file used will be `packages.generic`.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Might be exporting data for old categories.
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
Since we require the user to enter their full name Buckinghamshire have
asked us to change the text to "Full name" to make it clearer that the
full name is required to complete the form.
|
| |
| |
| |
| | |
This is under the assumption it will be replaced by a manifest theme on fixmystreet.com
|
| | |
|
| |
| |
| |
| | |
This saves hammering the FS for every front page request
|
| |
| |
| |
| |
| |
| |
| | |
For some reason switching to a Select stopped the update_model changes being applied
when persisting the model, meaning the INSERT query failed because the cobrand column
was null. This commit switches to a hidden input field for the cobrand which I’m
not super keen on, but it does get the job done...
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
If a user had no confirmed updates, but did have e.g. an unconfirmed
update that had mark_fixed set, you would get an error when trying to
hide the user's reports/updates.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 fixes a bug where the new tree plantings group was requiring a tree
group to be selected, which isn't the desired behaviour.
The bug was caused by the group layer not having the same `relevant`
function as the points layers. This adds the shared bits into a shared
config that the assets both use.
Also hide the asset item message for request to plant a new tree
category.
|
|
|
|
|
| |
We always want a tree code for tree reports, so add the code needed to
make the asset selection step mandatory.
|
|
|
|
|
|
| |
Checks that the correct bits of the problem's extra fields are sent when
creating the report in Open311, and that extra bits of info are sent
when sending comments to Open311.
|
|
|
|
|
|
|
|
| |
This allows you to restrict the message to a certain group of
categories.
This is so we can add a "is this problem on private land" message to the
categories in the "Trees" group for Peterborough.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to plant trees where there are already trees, so we add a
separate layer for new tree requests, and disable pin snapping for that
layer.
This adds a new option for layers named "relevant". If provided it will
be called with an options object, allowing you to check ".category" and
".group" and return a boolean for whether you want to display the layer
based on the passed options.
Note: You still need to provide an "asset_group" option even if you use
the "relevant" option as this is used elsewhere.
The "regular" tree-points layer uses this to exclude just the new trees
subcategory from being displayed.
|
|
|
|
| |
Two layers, one for tree points, the other for tree groups.
|
|
|
|
|
|
| |
This field is shown in the FMS interface, but doesn't need to be sent to
open311, it's just to check that the user isn't reporting problems on
private land.
|
|
|
|
|
| |
This is needed to route reports correctly when using the "Multi"
backend.
|