| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
| | |
| |
| |
| |
| |
| | |
- Record state change when leaving update and marking as duplicate
- Change save button wording to match problem state when inspecting
- Make it clearer that updates marking a report as duplicate actually close the report
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Use Problem->pin_data for single report page
- Promote markers_highlight to fixmystreet.maps API
We want to highlight map pins on the duplicate report selection UI, so let's use
what's already there instead of writing something new.
- Make sure duplicate report pins aren’t draggable
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The Zurich::admin_type function was setting $c->stash->{body}, meaning that
when trying to edit a superuser the 'fetch_contacts' function wasn't being
called, causing an "Can't call method "all" on an undefined value" error as
$c->stash->{live_contacts} wasn't ever being set.
Fixed by changing the conditional to simply determine whether fetch_contacts
needs to be called.
Included a regression test that meant a small addition to the MapItZurich mock.
|
| |
|
|
|
|
| |
The default cobrand does not have a template directory, so the
directory change to it was not working. Use the root directory
of the repository instead.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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).
|
| |\ |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
- 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
|
| |
|
|
|
| |
This is less confusing than redirecting to /auth and then to /my
(as they're logged in). Fixes #1566.
|
| |
|
|
| |
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.
|
| |/
|
|
| |
Used internally to provide more details about when a priority is applicable.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
If you changed the around filters on a URL with latitude/longitude, the
co-ordinates were not passed through as determine_location needed to be
called first.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
- Superusers couldn't view response priorities due to invalid $c->forward call
- Navigation to other areas of admin was broken on response priority admin pages
|
| |
|
|
|
|
| |
Reduce some duplicated code, and as a side effect gives HTML emails our
internal html_para filter, allowing single line returns in contact form
submissions.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
The report form is now split into "Public" and "Private" sections,
with a third, matching heading, for the category_extras, if shown.
|
| | |
| |
| |
| |
| | |
When a trusted user makes a report in a category that requires inspection, it'll
be sent immediately (i.e. without being inspected first).
|
| | | |
|
| | |
| |
| |
| | |
Fixes (the first part of) #1138.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
- Zurich users don't need permission to access user_edit page
- from_body can be set to any body by Zurich admin users, not just their own
- Don't show the area field on user_edit form
|
| |/ |
|
