| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
| |
This adds an update field to the bottom of the inspect form, requiring the
inspector to provide an update to be added to the report as it's sent.
See mysociety/fixmystreetforcouncils#64
|
| |
|
|
|
|
| |
Adapt code so that it could be opened up more in future.
|
|
|
|
| |
Stop IDs being shown on 404 pages, provide a nicer message on 403 pages.
|
|\ |
|
| |
| |
| |
| | |
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 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
|
|
|
|
|
|
|
|
|
|
|
| |
Categories can now require reports to be marked as 'inspected' via the frontend
before they're sent by send-reports.
A side-effect here is that send-reports will perform an extra n queries for each
report, where n is the number of bodies that report is being sent to, but
hopefully in practice this won't matter as it's an offline cronjob.
See mysociety/fixmystreetforcouncils#50
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users with the `report_inspect` permission can click a new 'inspect' button on a
report page to input more detailed problem information into a new form that
appears in a column alongside the report detail.
- Inspector data is stored in problem's 'extra' field
- Report category/state can be edited
- Location can be changed by dragging the pin or HTML5 geolocation
(Factored out Zurich admin pin drag into own function)
For mysociety/fixmystreetforcouncils#22
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Searches the `id` and `external_id` fields.
This takes you directly to the report if only a single report matches, otherwise
a disambiguation page is shown.
For mysociety/fixmystreetforcouncils#16
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This makes sure the correct dropdown is shown.
|
|
|
|
|
| |
The config page is only accessible by superusers.
The stats page only shows figures for the user’s from_body unless superuser.
|
| |
|
|
|
|
|
|
|
| |
Superusers can set a user's from_body to any value, but a normal staff user
can only set another user's from_body to the same as their own or undefined.
This is presented in the UI as a 'staff' tickbox.
|
|
|
|
|
|
|
|
| |
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 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
|
|/
|
|
| |
Fixes #1313.
|
|
|
|
| |
This is a continuation of b45b29c8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Design is all Zarino. This adds the ability to send HTML emails,
including attached inline images. When included, this is done as a
multipart/related email containing a multipart/alternative (of plain and
HTML) and any attached images, so that the images are available even if
HTML mail is not.
The alert emails list data has been improved so it can be constructed in
the templates rather than the code. Various templates have been tidied.
Various workarounds for email clients have been made, including:
* <th> is used so that the Android 4.x mail client can give them
`block` styling in the small screen media query.
* Font settings defined on every table cell (<th>) so that sans-serif
fonts are used in Outlook, rather than Times New Roman.
* A three-column wrapper table to create a 620px centred content area
that also shrinks down on narrow screens. (Outlook doesn’t like
max-width, so this is the simplest alternative.)
* Enforcing a sensible (500px) min-width for the main content area,
on clients that don’t support media queries (eg: native Gmail app).
* Giant borders on buttons so Outlook displays them
* Image alignment with align rather than float.
|
| |
|
|
|
|
| |
(VERSION disappears in some recent version.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- 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.
|
| |
|
| |
|
|
|
|
|
| |
Missed this from 8a8b34, and it was causing a crash on certain /reports/ pages
when trying to display the list of problems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is a concern that excluding district council reports from a two-tier
council's cobrand's /around page might lead to duplicate reports or reports
never being seen.
This commit adds them to the map and the sidebar and displays the destination
council in the report list item. Clicking the pin or the report link leads to
the report on FMS.com.
Reports sent to the a council other than the the active cobrand are shown as
grey pins on the map, and the receiving council's name is shown in the sidebar
list.
|
|
|
|
|
|
|
| |
The message shown to the user if the report was sent to a
council other than the cobrand owner was confusing so the wording
has been clarified. Also added a call to action to view the report
on FMS.com or the cobranded FMS.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
If you had no session cookie, started reporting a problem, logged in
through that process, you would then get a CSRF error as the token
had been created before the session was.
|
|
|
|
|
| |
Tidy up use of absolute URLs when in the admin.
Have the 404 handler spot static files in admin as a fallback.
|