| Commit message (Collapse) | Author | Age | Lines |
|---|
| |\ |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Allow multiple asset layers, and setting of multiple asset attributes.
[Bristol] Add Bristol asset layers.
|
| | | |
| | |
| | |
| | | |
Including WFS for forthcoming assets layers.
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Includes newest, oldest, least/most recently updated, and most comments.
The default remains the same, which is last updated on /reports, and
newest on /my and /around (the latter plus not-in-view
sorted-by-distance ones).
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
This pre-filters the 'all reports' link in the main nav and the /around page
reached via the front page postcode form
|
| | |
| |
| |
| |
| | |
- A user can be assigned to any number of its body's categories
- The category ids are stored as a list in the user's extra field
|
| |/ |
|
| |
|
|
| |
Fix title if error in adding user. Fixes #1510.
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
This matches the behaviour on /around, and prevents a refresh when
changing the state or category filters.
|
| | |
| |
| |
| |
| | |
This is so the photo modal works for pulled in report pages.
Fixes #1543.
|
| | | |
|
| | |
| |
| |
| |
| | |
- Priorities with no categories selected are available to all categories
- Display active categories in response priorities table
|
| | |
| |
| |
| |
| | |
- Also adds add select all/none UI
- Adds admin hint for empty category list behaviour
|
| | |
| |
| |
| | |
Used internally to provide more details about when a priority is applicable.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* The same template is now used for creating new contacts as well as editing
existing ones.
* Zurich template for editing contacts has been left unchanged for now
* Reputation threshold is included on form
* Fields are in a more intuitive order
* Required fields are marked as such in DOM for client-side validation
* Rename ‘notes’ field to make its meaning clearer
|
| |/
|
|
|
|
|
|
|
|
| |
Clicking the thumbnail on a report admin page was causing the 'rotating photo
will discard changes' alert to appear unnecessarily. This was due to the
data-confirm attribute on the parent <dd>, the meaning of which was changed by
f5b171f.
Fixed by using a different attribute name. Spotted another bug that I think
caused the dialog to never actually be shown with the correct message because
'this' was the form and not the clicked button element.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This lets people filter by multiple categories or states. It uses our
jQuery multi-select plugin to turn the <select multiple>s into little
overlay lists of checkboxes. HTML5 history is also supported.
|
| |/ |
|
| |\
| |
| |
| | |
'origin/issues/forcouncils/36-mobile-inspector-improvements'
|
| | | |
|
| | | |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want to make sure the extra metadata stored on a problem is kept in sync with
the requirements of the category the report is in. Thus, if a report is moved to
a category that collects extra metadata then the appropriate input fields should
be shown so the inspector can enter the data.
This commit shows the category extra HTML elements for every selectable category
on the inspector page hiding those that don't apply to the selected category. JS
is used to show/hide the extra fields when the category dropdown is changed.
A consequence of the implementation is that any extra metadata from the original
category is lost when the category is changed. Some thought was given to storing
the old values elsewhere in the problem's extra field but I decided against this
for the time being.
For mysociety/fixmystreetforcouncils#45
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When this commit is finished, modern browsers will have a far less
buggy layout on .with-notes pages. The main improvements are:
1. Simplified padding on .with-notes columns, allowing us to link to
an individual column (eg: /inspect#side-report-secondary) without
the browser scrolling down to jump over the #map_sidebar padding on
desktop browsers. Making hash fragment scrolling work means we can
automatically scroll Inspectors down to the Inspect form, when they
click the Inspect button on mobile devices, without worrying about
it breaking the desktop experience.
2. Flexible .with-notes column widths, meaning the layout no longer
breaks when long sidebar content triggers a scrollbar and decreases
the usable width of the sidebar. A predefined width for #side-report
means we can make sure .shadow-wrap is the correct width, despite
its fixed position taking it out of the document flow.
We make a trade-off on mid-size screens (768-960px), of hiding the map
to keep the two-column sidebar usable. Will revisit if it turns out
this causes problems later on.
|
| | |
| |
| |
| |
| |
| | |
Inspectors can now tick the optional “Save with a public update”
checkbox, to reveal the “Public update” textarea. This means there is
no longer a need for two separate submit buttons.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though FMS has had a `.btn` class for a while, styling buttons has
still been difficult, mainly because of the very opinionated base styles
applied to overpowered selectors like `input[type="submit"]`.
This commit brings the FMS styles more in line with modern frameworks
like Bootstrap – inputs and buttons are left completely unstyled by
default, with an opt-in `.btn` class to add the styles back in.
Since `.btn` is just a single class, it’s easy to override, and avoids
selector bloat like `.green-btn, button.green-btn, input.green-btn`.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
IDs and locations at the top, then location-related actions (including
a new “navigate to this problem” button), then status and category
inputs (since these can have an effect on how we display the rest of
the form), then any status/category-related inputs, and finally inputs
for internal details like priority and traffic management.
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| | |
It will default to your logged in address, ignoring what is put in this
box. This should also fix an issue where the update email address field
is initially blank when you are logged in and using the "Provide update
as" functionality (due to both fields having the same name).
|
| | |
| |
| |
| | |
Cope better if things aren't defined.
|
| | | |
|
| | | |
|
