| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
If e.g. a report was made on .com and sent to TfL, it would
be sent with TfL colours but a (stretched) .com logo.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
| |
sets the state of the report to `for_triage` upon sending
|
| |
|
| |
|
|
|
|
| |
This is intended to be used by Westminster, but not quite yet.
|
|
|
|
|
|
| |
It is possible that the category of a report no longer exists and in
that case the Open311 send process was falling over. This checks that
we've found a contact and if not sets the error and skips the report.
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new upload_files flag (which cobrands can set in their
open311_config method) to Open311 which means any general enquiry files
are POSTed to the Open311 endpoint in a multipart/form-data request.
Photos on hidden reports are also sent if this flag is set, because they
wouldn't be accessible to the Open311 endpoint via media_url as the
reports are non_public.
This feature is not part of the Open311 specification.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The test has to now create a new comment object each time as
`get_cobrand_logged` is cached on the object.
|
|
|
|
|
|
|
| |
Includes an option to send to the council instead for e.g. reports on
underpasses or bridges.
Fixes #736
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Allow flytipping reporting on cobrand and .com, with road reports going to
Bucks Confirm and email, and non-road reports going to district and Bucks
emails.
|
| |
|
| |
|
|
|
|
|
| |
22f0fed0b made the closest address an object, and objects can’t
be directly stored in the extra column.
|
|
|
|
| |
reports
|
|
|
|
|
|
| |
If the map was not clicked and we don't have a postcode we should still
send the easting and northing extra attributes if send_notpinpointed is
set.
|
|
|
|
|
|
|
|
| |
Per cobrand configurable option to send multiple photos over open311
instead of just a single one. Does this by sending multiple media_url
parameters in the POST body.
The default remains to send the first photo associated with a report.
|
|
|
|
|
|
|
| |
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!
|
| |
|
| |
|
|
|
|
|
|
| |
By default encode_entities uses named entities, which don't exist
by default in XML. It seemed nicer to switch to only escaping the
minimum rather than switching to numeric entities.
|
|
|
|
|
|
| |
This includes stopping some emails being sent (moderation, alert,
questionnaire), dealing with Open311/email report sending, and
tokenised_url.
|
| |
|
|
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
|
|
|
|
| |
Both uses can be covered by existing modules.
This means we can drop FCGI also.
|
| |
|
|
|
|
|
|
| |
To deal with a recipient mail server not allowing inbound email
using the same domain as an internal domain, e.g.
https://community.mimecast.com/docs/DOC-1419
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid doing cobrand-specific logic within SendReport::Open311.
The hooks defined are:
open311_config: set extra fields
open311_pre_send: set endpoints and munge data
These are tested in the new t/app/sendreport/open311.t, which does
not send any actual reports, but just checks that all the data is
munged into the expected format. (tests under t/open311* should
already test the actual sending)
Remove unused Open311 special cases.
|
| |
|
|
|
|
| |
This joins easting, northing and an external ID field.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
It will still output via cron on the first failure. However, reduce the
verbosity of a couple of SendReport modules which are reporting failure
every time.
|
| |
|