| Commit message (Collapse) | Author | Age | Lines |
|
|
|
| |
This was missed in 0998aef4.
|
|
|
|
|
| |
We keep the internal states hardcoded, plus the core open (confirmed)
and closed ones, but the remainder are moved to the database.
|
| |
|
|
|
|
|
|
|
| |
- Also provides an editor for the extra Open311 fields on contacts.
- Adds .btn--small class for small buttons
Fixes #1743.
|
|
|
|
|
|
| |
A reference to ->storage was missed as this script changed in a
different branch. The schema files contain transaction commands
themselves. A check for migration 52 was missing.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Problems can have an associated defect type, that can be assigned during
an inspection. Include an admin interface for managing these types, that
can also be assigned on a per-category basis, currently available to the
Oxfordshire cobrand.
(Also include 'TM' in traffic management Exor RDI output.)
|
| |
|
| |
|
|
|
|
| |
Used internally to provide more details about when a priority is applicable.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
A user with the appropriate permission can add/remove reports from their
list of planned reports using a button on a report page. The list can be
viewed at /my/planned.
|
|
|
|
| |
We'll soon be adding more new permission types.
|
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mechanism is general, but current implementation only used
for Zurich.
- Zurich: Record time_spent field mysociety/FixMyStreet-Commercial#676
- template changes (including jQuery spinner)
- backend changes to save data are made:
- in log_edit, if supplied
- and time on category change (and arbitrary actions)
- Add update_admin_log to all paths for DM, ensuring that it gets called,
while resetting the `time_spent` parameter, to make sure that
there is never a duplicate record created.
- Also quell warning about using DateTime values in query.
- Also add (seemingly unrelated) parens to stop misparsing of OK line in
questionnaire test now that DT::Format::Pg is used in Zurich cobrand
See mysociety/FixMyStreet-Commercial#676
|
|
|
|
|
|
|
| |
This provides a ResponseTemplate model that an admin/staff
user can choose from when responding to problems.
For mysociety/FixMyStreet-Commercial#671.
|
| |
|
| |
|
|
|
|
|
| |
This override is not used anywhere, it dates from a very old long-gone
test script, and causes issues with database query planning.
|
| |
|
|
|
|
|
| |
Call the necessary boilerplate in each script so you can call them
directly. Remove boilerplate from files that don't need it.
|
| |
|
|
|
|
|
|
| |
bin/update-schema --commit should now work
A downgrade is also provided. Run bin/update-schema --help for details
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
bin/update-schema
locale/sv_SE.UTF-8/LC_MESSAGES/FixMyStreet.po
perllib/FixMyStreet/DB/Result/Body.pm
|
| | |
|
| |
| |
| |
| | |
to allow a wider range of action logging.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the development parameter is passed to the install-script, don't
install a crontab, don't set up nginx, don't force the repository
to a particular version, and don't set up an application server.
Also only create a general.yml file if one doesn't already exist,
and add some locales that the test suite assumes are present. And
run the db schema update script.
|
|/ |
|
|
It will examine the current database to see at what state it is,
and optionally run the newer schema SQL files in order to bring
the database up to date.
At the 'adding bodies' stage, it will also query MapIt to fill the
name column of the new body table.
|