| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add an unban button to the user edit page when a user is in the abuse
table.
Fixes #1881
|
|
|
|
|
|
|
| |
move setting the body template to before `fetch_contacts` so it doesn't
override setting the text only email address template.
Fixes #1895
|
|
|
|
|
| |
The check that a name was entered was testing the user's
current name, not the name entered in the form.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a comment on a problem when the admin is used to change the state
of the problem. If only the state is changed then create a comment with
blank text. If the category and state are changing then include details
of the category change in the comment.
Not all the state changes are displayed at the template level by
default.
Fixes #1846
|
|
|
|
|
|
|
| |
This includes search/flagging users, editing user on the report
and update edit pages, and user adding/editing itself.
Add some more tests for user adding/editing.
|
| |
|
|
|
|
|
|
| |
uses the body user but flags the report as anonymous
Fixes #fixmystreetforcouncils/207
|
| |
|
|
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
|
|
|
| |
This means that the tests can be run in parallel.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically in UK cobrands, bodies have had IDs the same as the MapIt
area ID they cover. This can be confusing (if you are setting up a dev
environment, say) and should not be necessary. This commit removes the
requirement entirely, by switching any ID checks to either the name of
the body, or the actual area it covers.
One note: the body name in the test has to match so that we do not get
two bodies both covering 2237 created. This will not be necessary when
the tests are compartmentalized in the next commit.
|
| |
|
|
|
|
|
|
|
| |
The report-sending code has allowed multiple emails for a long time, but the
admin wouldn't allow you to enter multiple emails for each contact.
Fixes mysociety/FixMyStreet-Commercial#835
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is less confusing than redirecting to /auth and then to /my
(as they're logged in). Fixes #1566.
|
| |
|
|
|
|
| |
Used internally to provide more details about when a priority is applicable.
|
|
|
|
|
| |
When a trusted user makes a report in a category that requires inspection, it'll
be sent immediately (i.e. without being inspected first).
|
| |
|
|
|
|
|
|
|
| |
This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.
For mysociety/fixmystreetforcouncils#66
|
|
|
|
|
|
|
|
|
|
|
| |
This builds on the response templates in the Zürich cobrand:
- Allow response templates to be assigned to categories
- Also adds a auto_response flag, which will be used to automatically create
updates when reports are made.
- Include response templates select box on update form
For mysociety/fixmystreetforcouncils#31
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The 'user_edit' permission is required to edit users.
The admin pages on UK council cobrands only allow editing of users whose
from_body is the same as the logged-in user, or who have sent reports or updates
to the council.
|
| |
|
|
|
|
|
| |
This improves create_user_ok to work more like create_body_ok where extra params
can be passed in and set on the model.
|
| |
|
|
|
|
|
|
|
|
|
| |
- Adds is_superuser flag to User
- Logged-in user must be a superuser or have from_body set in order to access
anything within /admin
- has_permission_to on a superuser will always return true
- Only superusers can create/grant superusers
- New `createsuperuser` command for creating superusers
|
|
|
|
| |
This also updates the body column to match the category.
|
|
|
|
|
| |
Tidy up use of absolute URLs when in the admin.
Have the 404 handler spot static files in admin as a fallback.
|
|
|
|
| |
Show bodies for which details are missing, and any send method used.
|
| |
|
| |
|
|
|
|
| |
Fixes #1266.
|
|
|
|
|
|
| |
There might be the odd update alert we are interested in (those not
auto-signed up for as part of report or update creation), but they
will be rare.
|
| |
|
| |
|
|
|
|
| |
Maintain old location wrappers.
|
|
|
|
|
| |
This override is not used anywhere, it dates from a very old long-gone
test script, and causes issues with database query planning.
|
| |
|