| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
| |
Remove some unused code.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The “Get updates” flow on a report page, if logged in, was showing
an input label but no input field (because one is not needed), but
then on submission asking for your email address. Add missing name
on submit button to fix this.
|
| |
|
|
|
|
|
|
|
|
|
| |
Hitherto when creating a body or ward alert on a UK site,
the MapIt area ID has been stored instead of the body ID.
This is okay for www.fixmystreet.com which for historical
reasons does have body IDs that match MapIt area IDs, but
other UK-based sites may well not. The alert lookup looks
for body ID, meaning those alerts will not work. Save the
body ID instead, plus fix some tests that were making the
same assumption.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If there was a normal email alert, and then an alert for an update with
no text (so no email should be sent), it would still try to send the
blank email, and then die because no e.g. $data{cobrand} set.
This moves the skip-blank-update check higher up, above any email
sending code.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If a staff user changed a problem’s state and an empty update was generated,
it was possible for alert emails to be sent with missing URLs because the
empty string in the update text was falsy and Alert.pm took the wrong path.
This fixes the problem by changing the test to defined() and includes a
regression test.
|
| |
|
|
| |
This means that the tests can be run in parallel.
|
| | |
|
| |
|
|
|
|
| |
The code was adding two days and seven/eight hours to a floating
DateTime, which from 5-7pm on 23rd March 2017 created a DateTime
between 1-2am on 26th March which does not exist in e.g. the UK.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This improves create_user_ok to work more like create_body_ok where extra params
can be passed in and set on the model.
|
| | |
|
| |
|
|
|
| |
It’s best if Zurich keeps the old text, so now they have their
own overrides for those template files.
|
| |
|
|
|
|
|
| |
Restrict email_sign_in token to one day, unused confirmation tokens to
one month. Used tokens will redirect to the created thing but not log
in; don't log in with alert links (unsubscribe link never expires, reply
link will still show "reopen" tickbox).
|
| |
|
|
| |
Fixes #1011.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The body-based alert only works if the body ID matches the MapIt ID.
This fixes #959. Further work needs to be done to enable proper
body-based alerts that work properly in all circumstances.
Consequently, factor out fixed body IDs from many tests.
Also fix a couple of tests not overriding geocoder correctly.
|
| |
|
|
| |
And FixMyStreet.com specific open questionnaire page.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is useful for sites where the updates aren't published on the site
so you need a bit more context in the email alerts.
Add inlude_time_in_update_alerts to default cobrand, off as default
If this is set then the date is added after the name string in the
email, passing in 'alert' as the type to dt_prettify in order to allow
the cobrand to format it accordingly.
This does require pulling out the alert confirmed time from the database
in the send_alerts code where it wasn't before.
|
| |
|
|
|
| |
This is very old, no-one seems to want/need it any more,
and more than one reuser does not want it. Fixes #715.
|
| | |
|
| |
|
|
| |
running test suite
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is so they can more easily update, especially if the update they've
just received has mistakingly 'fixed' the report. This fixes #7.
|
| |
|
|
| |
linebreaks in test match string (non public alerts)
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
