| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
| |
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
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Also takes the opportunity to fix the incorrectly-encoded sender name which
was appearing to some clients as "Züri Wie Neu".
|
| | |
|
| |
|
|
|
| |
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.
|
| |/
|
|
|
|
| |
If a category had eg. a double space, the use of the filter meant it
was output in the HTML with only a single space and so woudn't match
the database entry. Switch to more explicit template space chomping.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
The tests were running slowly because of gaze.mysociety.org's rate-limiting.
|
| |
|
|
|
|
| |
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.
|
| |\ |
|
| | |
| |
| |
| | |
Show bodies for which details are missing, and any send method used.
|
| | | |
|
| |/
|
|
|
|
| |
jhead 3.00 considers 0 an invalid value for EXIF orientation and will replace it
with 1 when run with the -autorot flag. This was causing a test failure as the
SHA hash of the sample image was being changed.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
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.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some UK councils with Open311 integrations (e.g. Bromley) have a custom wording
in the confirmation email sent when updates are left on reports, to make the
user aware that the update is sent to the council in question.
Bromley noticed that some emails were being sent without this wording, leading
at least one user to contact the council directly about the report.
It turns out that although the email template contains an IF clause to use the
appropriate wording for Bromley (and Stevenage) reports, the incorrect template
file was being used when updates were made via the Bromley cobrand.
This commit solves the problem by introducing a new
`Cobrand::Default::path_to_email_templates` method, which is overridden by
`Cobrand::UKCouncils` to include the `templates/email/fixmystreet` path. Paths
returned by this method are used as the `additional_template_paths` param when
templating emails. A regression test is included.
Additionally moves email templates for fixmystreet.com to a directory name
reflecting their purpose, in the same way the web templates are arranged.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
If we don't do this, the default quoted-printable encoding will make
sure the lines are physically wrapped anyway. format=flowed could be
an alternative, but I think "=" acting as a quasi-hyphen is somewhat
nicer than every line ending with "=20".
A better solution could be quoted-printable doing soft wrapping only
at word breaks, making each line be readable though end with a " =",
but that didn't seem worth the effort involved.
|
| | |
|
| |
|
|
|
|
|
| |
Historically, emails sent offline (alerts, questionnaires, etc) used a
different templating system from those sent by the website (e.g. login
emails), though the newer system was also being used for the site name
and signature of offline emails.
|
| |
|
|
| |
Fixes #1286.
|
| |
|
|
|
| |
Even when we ask for a specific range of dates, we sometimes get given
more in the response.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
And associated, e.g. nothing references fixmystreet-old-box.js any more.
|
| | | |
|
