| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
This includes adding/removing reports from a user's shortlist, and
manual reordering of a shortlist with up/down buttons.
The backend code can cope with an item moving to any point in the list.
|
| | |
|
| |
|
|
|
|
| |
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
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
The report form is now split into "Public" and "Private" sections,
with a third, matching heading, for the category_extras, if shown.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| | |
Allow get_extra_metadata to return all the data with no argument.
|
| |/
|
|
|
|
|
| |
This is a cut-down version of the full inspect screen.
We truncate the co-ordinates just in case (they should be anyway but
e.g. the test report isn't).
|
| | |
|
| |
|
|
| |
This makes sure the correct dropdown is shown.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows users who have the correct permissions to add reports on
behalf of the body or another user.
We enable editing of the email box by default, so that if JavaScript
isn't available, someone can still change the email for the 'another
user' option.
For mysociety/fixmystreetforcouncils#10 and
mysociety/fixmystreetforcouncils#11
|
| |
|
|
| |
This also updates the body column to match the category.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Replaced duplicate code blocks that are responsible for sending
confirmation of problem email with a function. Should make it
easier to do two-tier conditional messages later on. Also fixes a
minor bug where the wrong confirmation email would be sent for
reports from the mobile app to unresponsive councils.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This adds a new Cobrand::Default::categories_restriction method that can be used
to limit what categories are available when making a new report on a per-cobrand
basis.
This is used by Cobrand::Bristol to only show Open311 categories when making a
new report on fixmystreet.bristol.gov.uk but allowing all categories on FMS.com.
Also removes the Hart::hidden_categories and uses the new categories_restriction
method to achieve the same thing.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
It errored on new-style parsed XML, rather than let it through.
Add a new category to the test that highlights this.
|
| | | |
|
| |/
|
|
|
| |
Parse the XML in such a way other parts of the code do not have to worry
about single-value folding or the like.
|
| |
|
|
|
| |
It was being treated as a new report and showing errors, rather than
showing you the same page with updated filters. Fixes #1422.
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The app doesn't currently use the unresponsive body data returned
via /report/new/ajax, so make sure it's returned via the category
look up it does make.
|
| |/ |
|
| |
|
|
|
|
| |
Make sure the unresponsive message shows, if you're in a two-tier area
and one of the areas is marked as unresponsive, for all the categories
of that area.
|
| |
|
|
|
| |
This variable can then be used by e.g. extra_name.html to know what form
it is on.
|
| |
|
|
|
|
| |
This adds a new cobrand variable, report_form_extras, which contains a
list of extra fields that will be saved in the 'extra' metadata of the
report. Fields may optionally be marked as required.
|
| |
|
|
|
| |
It is currently only used for processing extra fields (the list, not the
metadata hash) which is really only of relevance to Open311.
|
| |
|
|
| |
Thanks to @jonkri for spotting.
|
| |
|
|
| |
Makes the flow more like new reporting.
|
| | |
|
| |
|
|
|
|
| |
Travis has Cpanel::JSON::XS preinstalled, which means that the build
would fail there, as JSON::MaybeXS would try and upgrade JSON::XS to
version 3 which the snapshot did not contain.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Three file inputs, progressively enhanced with dropzone.
This moves the photo input higher up, so that photos can upload while
you're filling out the form. It standardises and improves photo error
handling.
[fixmystreet.com] Guidance for what photos should and shouldn’t include.
|
| |
|
|
|
|
|
|
| |
See issue in mysociety/FixMyStreet-Commercial#663 with
problems not appearing in the "Erfasst" filter. It looks like Zurich
requires a single id in the `bodies_str` (like '4'), and may rely on the
configuration of bodies/contacts in database to be perfect to avoid them
becoming something like '4|47,48'.
|
| |
|
|
|
|
|
|
| |
For Zurich, see mysociety/FixMyStreet-Commercial#664.
This commit includes a new PhotoSet class (NB: called Model:: though not
really a model), should handle binary data (e.g. old style photos in
database), fileids (40-char hash), and Catalyst::Upload objects.
|
| |
|
|
| |
See mysociety/FixMyStreet-Commercial#669
|
| |
|
|
| |
Fixes #1210.
|
| |
|
|
| |
This makes testing easier.
|
| | |
|
