| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Hitherto when creating a body or ward alert on a UK site,
the MapIt area ID has been stored instead of the body ID.
This is okay for www.fixmystreet.com which for historical
reasons does have body IDs that match MapIt area IDs, but
other UK-based sites may well not. The alert lookup looks
for body ID, meaning those alerts will not work. Save the
body ID instead, plus fix some tests that were making the
same assumption.
|
| |
|
|
| |
Fixes mysociety/fixmystreetforcouncils#275
|
| |
|
|
|
|
|
|
|
| |
Add a button to the user edit page that sends a login token email to the
user. Helpful for user support situations where someone is having
trouble logging in. Also for situations where you have added a user and
want to get them logged in.
Fixes #2041
|
| |
|
|
|
| |
As with priorities, they depend upon the category and so must be
looked up after that has been updated.
|
| | |
|
| |
|
|
|
|
|
| |
This allows the mobile app to explicitly detect when a body is
unresponsive and display the category_extra text.
For mysociety/fixmystreet-mobile#266
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
| |
Add a check in the root controller `auto` to a cobrand hook that denies
access if it returns true. This goes here so that cobrands and users are
set up, which is not the case for `check_login_required`. Used to do
things like deny site access unless the user is a superuser.
|
| |\ |
|
| | |
| |
| |
| | |
This assumes the SendReport code will deal with the issue.
|
| |/
|
|
| |
The User model now also has a created column.
|
| |
|
|
|
|
|
|
| |
Display fields that are automatically filled in the contact editing form
otherwise the data is lost. Also include the automated field in the
form.
Fixes #2136
|
| |
|
|
|
| |
Return an error if an id for either a hidden update or one not
associated with the problem id is passed to the contact form.
|
| | |
|
| | |
|
| |
|
|
|
| |
Both filter categories and new report category lists went through mappings
to different data structures, which doesn't seem to be needed.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
So that you can build functionality to add extra limitations on
to the map pins displayed. Useful for Collideoscope initially
to filter out (or in) reports from the Department of Transport's
Stats19 Data.
|
| |/
|
|
|
|
|
|
| |
Instead of just a Yes/No display a formatted list of values in extra.
Has special handling for known fields otherwise just prints them out
dumbly.
Fixes #1809
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
This allows a cobrand to categorise the reports however it wishes.
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
UI to update the fetch_all_problems setting in extra for a body. This also
adds handling for extra body values in the Admin in a similar manner to the
way other body params are handled.
|
| |
|
|
|
|
|
| |
I find myself wanting to view the current report in the admin all the time -
this commit adds a link to the top of the inspector column that goes right there.
Only visible for superusers and staff users with permission to actually view the
admin.
|
| | |
|
| |
|
|
|
|
| |
Add a single_body_only form value to reports that contains the name of
the only body to send the problem to. If the name doesn't match any of
the valid bodies for the report then send to all.
|
| |
|
|
|
| |
test to check creating a new report for a category for which there are
multiple bodies
|
| |
|
|
|
|
|
| |
Comments added offline by an inspector set the time in JavaScript using
a UTC epoch. We need to add the FMS timezone to this so it's in the
timezone the database expects for timestamps otherwise it's incorrect
when we fetch it back out
|
| |
|
|
|
|
| |
Hides the empty “Help <council> resolve your problem quicker” section of
the new report form if report metas for the selected category are all
hidden fields.
|
| | |
|
| |
|
|
|
| |
We do need to store them, so that the sending knows which fields are being
requested, but we do not want them output to the client at all.
|
| | |
|
| |
|
|
|
| |
Store if the report/update was created by someone using the contributed-as
dropdown, and use that information to perhaps not send report-sent emails.
|
| |\ |
|
| | |
| |
| |
| | |
This fixes #2023 by removing the comma.
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
| |
The Zurich code was written a long time ago, and used overriding so that
e.g. the hard-coded 'investigating' state referred to Wunsch (wish). Now
that states are stored in the database, we can create ones specially for
Zurich and use them instead. Hooray!
|
| |
|
|
|
| |
If you rotated a photo, updates and the category list weren't loaded. If you
changed a report's state, the map pin colour was derived from the old state.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This means the questionnaire is considered 'answered' as soon as
a (HTML) link is clicked, which I think is okay. Then filling in
the questionnaire form will update the same questionnaire.
|
| | | |
|
| | |
| |
| |
| |
| | |
This means we don't show separate 'Still open' messages
when an update was also left at the same time.
|
| | | |
|
| | | |
|
