| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
| |
Include the usual generate new .pot file, gettext-merge, push to
Transifex, pull from Transifex step.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
No need for bullets here, nor margins above/below each label.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Prevent people from using very long titles.
Fixes mysociety/fixmystreet-commercial#1344
|
| |
|
|
| |
For mysociety/fixmystreet-commercial#1331
|
| | |
|
| |
|
|
|
| |
Prevent the user from making a report unless they have clicked on an
asset.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Shared margin rules for `.box-warning` and `.extra-category-questions`
in `_base.scss` and `_layout.scss` (where the margin can potentially
change based on the `$mappage-sidebar-padding` variable).
* Move the Sass rules for `.box-warning` further up `_base.scss` to be
next to `.extra-category-questions` since they’re both so similar.
* No need for `.full-width` on the `.extra-category-questions` div since
we were overriding the margin-top anyway.
* Remove the little triangle between the category select box and the
grey `.extra-category-questions` div, since the category questions
isn’t always presented immediately after the category select box.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Make the expandable list item’s expanded state look more like the
regular `.problem-header`, to more strongly imply that you don’t need
to visit the individual report page to read more.
Since expandable list items now *always* contain more information in
their expanded state, there’s no need for the `show_more` flag in the
templates.
Addresses part of the feedback in mysociety/fixmystreet-commercial#1304.
|
| |
|
|
|
| |
If the site only has the one category, it was being preselected
but the extra attribute questions were not being shown.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the Vector tiles layers which Alloy provided which don't require
and API key or paging. This code is still a bit work in progress as it
makes a few assumptions:
* the zoom level is hard coded
* adding assets to layers assumes things are not async when they are
* we are using itemId which is not the correct thing
This uses an event to notify that loading a request for a new set of
tiles has started and then uses counting to check we've fetched them all
and hence can get the layer to check for an asset.
It also uses start times to throw away requests for tiles in a previous
request if they come in after a new request has started.
This also doesn't have anything for putting labels on assets because
that information doesn't seem to be in the tiles.
A final point is that the tiles can contain multiple assets at the same
coőrdinates and we don't do anything about that at the moment so the
user will just get the last one added when they click.
This includes a dump of all the layers from alloy and then matches them
up to categories displayed on FixMyStreet
|
| |
|
|
|
| |
Co-authored-by: Zarino Zappia <zarino@mysociety.org>
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
| |
|
|
|
| |
Add a privacy_policy_url function to the cobrand and use that in the
templates instead of hard coding /privacy
|
| | |
|
| |
|
|
|
| |
If an Open311 server returned an empty set of values, it was possible
for this template to then display a set of empty dropdown options.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reduce the space between checkbox and label, so the text isn't lost if
the page is zoomed in. Fixes #2411.
Replace the creator_fixed question with segmented control to match the
full questionnaire, and the admin verified checkboxes with inline-text
as they need no padding. Having done that, all uses of .inline are now
on their own lines, so no post-padding is needed any longer, but we’ll
leave some in case of future use.
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On some UK council cobrands, some reports listed might not have been sent
to that council, so links to those must go to the national site. However,
using absolute URLs for all these reports means that sometimes you change
domain when you don't need to (eg. if you’re on osm.fixmystreet.com or an
aliased version of the site), which can cause confusion. State when we’re
happy to use a relative link (ie. web-facing report links, not emails, or
share links) and do that when we can.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previously staff-only fixmystreet.set_up.manage_duplicates() has
been promoted from staff.js to its own file so that we can use it to
display the duplicate suggestions on the `/report/new` form.
render_duplicate_list (the old refresh_duplicate_list) no longer filters
or slices the reports_list returned by the ajax call, since it turns out
the server handles all of that (`sub _nearby_json` in `Report.pm` and
`sub nearby` in `Nearby.pm`).
Since the expandable list items include the "fancybox" image previews,
the fancybox CSS now has to be included in the `/report/new` page head,
hence the addition of "photo-js.html" in `fill_in_details.html`.
The “Get updates” flow reuses the same JavaScript that handles the
submission of the "Get updates" drawer at the bottom of around pages.
|
| |
|
|
|
| |
There’s no need for this `--reports` to be there, so let’s start phasing
it out.
|
| |
|
|
|
|
|
|
|
|
| |
`_item_expandable.html` is an alternative to regular list items, where
you can display extra information on the first click on the item, and
then also, optionally, offer a further action, as a separate button.
Right now the expandable list items aren’t used anywhere, but we’ll
soon be using them in the duplicate report suggestion UI for council
staff and the public.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
The “Get updates” flow on a report page, if logged in, was showing
an input label but no input field (because one is not needed), but
then on submission asking for your email address. Add missing name
on submit button to fix this.
|
| |/ |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Update database to store an array of IDs rather than only one;
consequential changes to the admin and the dashboard to allow
selection.
|
| |/
|
|
| |
It is needed in e.g. South Kesteven; link to .com help page.
|
| |
|
|
|
|
|
| |
Similarly to 1f69e28c, we were previously only checking the first
matching entry, which led to confusing behaviour in places. Include
consequential amendments for e.g. one body being unresponsive, the
other not.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Remove the server-side zoom-in-url fix, instead use an ArgParser
subclass to default to the provided data if nothing in URL. Then
we can switch to using short lat/lon in geocoder URLs.
|
| | |
| |
| |
| |
| |
| | |
Fixes #2242.
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| | |
Template Toolkit treats keys starting with ‘_’ as private and does not
expose them. It is possible for an Open311 server to return fields
starting with an underscore, and we want to use those in the template.
|
| |\ \ |
|
| | | | |
|
