| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Prevents potential odd-element hash in e.g. response_priorities.
|
| |
|
|
|
| |
This deals with a bootstrapping issue of adding new admin users that
haven't yet interacted with the system.
|
| | |
|
| |
|
|
|
| |
As with d3d0ab6d, we need to only decode_utf8 strftime output that has
not already been decoded, to prevent errors in Perl 5.20+.
|
| |
|
|
|
| |
The change to remove inline JavaScript stopped the Bromley-specific
tiles from working. Put them back with an extra JavaScript file.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/
|
|
| |
[Bristol] Use more zoomed-in default link zoom.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
This matches the behaviour on /around, and prevents a refresh when
changing the state or category filters.
|
| |\ \ |
|
| | |/
| |
| |
| |
| | |
Instead of returning all templates for the problem's body, return those
for the problem's category (or with no category).
|
| | |
| |
| |
| |
| | |
- Priorities with no categories selected are available to all categories
- Display active categories in response priorities table
|
| |/
|
|
| |
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.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
It would always create a new report rather than return an existing one,
if present.
|
| |
|
|
|
|
| |
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.
|
| | | |
|
| | | |
|
