| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
No need for bullets here, nor margins above/below each label.
|
| |
|
|
|
|
|
|
| |
Prevent people from using very long titles.
Fixes mysociety/fixmystreet-commercial#1344
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If someone tries to moderate after someone else has, re-show the
form and an error.
|
|
|
|
| |
This will also be used by the moderation conflict code.
|
| |
|
|
|
|
|
|
| |
If the user has moderating permission, or a cobrand allows the viewing
of moderation history, show moderation history within the updates on a
report page.
|
|
|
|
|
| |
Checks for a fieldtype property and uses that for the input type to
allow setting the type of the field for e.g. date fields.
|
|
|
|
|
| |
Otherwise you can get an error trying to look up the body name on
submission.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Since questionnaire responses were recorded on email link click, we
should have been showing those that reopened or fixed reports, not
just steady-state "Still open" ones.
|
| |
|
| |
|
|
|
|
| |
Previously, CSS was absolutely positioning one on top of the other.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Simplify markup required for the status banner.
* Simplify styles - the banner is now identical on all screen sizes.
* Move the banner from `report/display.html` into `report/_main.html`
so that it can appear after `.problem-back` in the source order.
* Use real pin icon instead of `pin-flat-white-small.png`.
* Set a default `$col_fixed_label` colour in `_base.scss`, so cobrands
don’t have to define it themselves if they’re happy with green.
* Introduce `$col_fixed_label_light`, with a sensible default for all
cobrands, even ones that have a custom `$col_fixed_label`.
* Remove `$col_fixed_label_dark` – no longer needed.
|