| Commit message (Collapse) | Author | Age | Lines |
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I think I was wrong in a83b379fd2d676172855825d0592937b234371e2 in
assuming that all email gets properly encoded for transfer. Looking
at the mail gem load method
https://github.com/mikel/mail/blob/b159e0a542962fdd5e292a48cfffa560d7cf412e/lib/mail/mail.rb#L175a,
it reads raw email content from a file in binary mode. So this commit
makes both reading and writing the raw_email a binary mode operation
and adds a data_as_text method for displaying the data in the admin
interface that coerces it to valid utf-8.
|
| | |
| |
| |
| | |
Move setup to spec - not in common with other specs.
|
| | |
| |
| |
| |
| | |
We don't write the data for a raw email to the database anymore.
It's written to a file.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Remove unneeded setup, fixtures are not used in these specs.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
mb_chars provides a multibyte-aware wrapper for strings. It should
have no effect on ruby 1.9.3 and above. Although ruby 1.8.7 wouldn't
raise errors on a badly sliced multibyte string, on upgrading to ruby
1.9.3 and above, string operations such as gsub, match and join may
produce ArgumentErrors with the message "invalid byte sequence in UTF-8".
Additionally, a database with 'UTF-8' encoding may produce the error
"PG::CharacterNotInRepertoire: ERROR: invalid byte sequence for encoding "UTF8""
|
| |
|
|
|
| |
Mistakenly committed from previous version of
da6c11531a761847ee129f92677a44fdb02de04e
|
| |
|
|
|
|
|
|
|
| |
Stops the RequestMailer trying to send a stopped_responses mail if the
To: address can’t be parsed from the incoming message.
ArgumentError:
An SMTP To address is required to send a message. Set the message
smtp_envelope_to, to, cc, or bcc address.
|
| |
|
|
|
| |
Prevents mailin exiting with an error code of 75 and sending error
reports to the team@ email address.
|
| |
|
|
|
| |
If you run an Alaveteli in a region where we can’t show holiday
suggestions the holiday import page breaks. This commit rescues from
an unavailable region so that we display a friendly error message.
|
| |
|
|
|
|
| |
Next commit adds a new spec; this before block was affecting the
behaviour of the new spec.
https://robots.thoughtbot.com/lets-not
|
| |
|
|
| |
In practice, it's just confusing if you've been away from the site.
|
| |
|
|
|
|
|
|
|
|
| |
Now that we use global CSRF authenticity checks, searches were logging
logged-in users out as the form is an HTML form, not a Rails-generated
form with a CSRF token. So form submission raised an InvalidAuthenticityToken
error and reset their session. We could generate the form in Rails, but we
also want to minimise the number of non-logged in people who have a
session cookie, so that varnish can cache pages extensively. So we don't
want to put the CSRF token for the search form in everyone's session.
|
| |\
| |
| |
| |
| | |
Conflicts:
config/initializers/alaveteli.rb
|
| | |
| |
| |
| | |
Thanks to @RichardTaylor for reporting.
|
| |/
|
|
| |
Needs to be restored as part of https://github.com/mysociety/alaveteli/issues/2137.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Closes Â#434.
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Fixes submission of form containing both existing and new
translations
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | | |
Conflicts:
app/views/public_body/show.html.erb
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
There's only one call to this function in the rest of the code. That
has 'html' set to true.
|
| |\ \ \ |
|
| | |/ / |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This functionality has been moved to whatdotheyknow-theme:
https://github.com/mysociety/whatdotheyknow-theme/commit/963d1453e94056eaf6f93a4f73a1f348a0817656
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
- Redefined User#public_banned? to User#banned?
- Add specs for User#banned?
- Deprecate User#public_banned?
- Replace use of User#public_banned? with User#banned?
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
Existing behaviour seems to be that when a tag is specified, only
bodies that already have that tag will be updated.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
As I understand it, the expectation is to replace any existing tags
with both the tag from the UI and the tags from the csv.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the call to public_body.send would return the value for
the default locale if no value was set in the current locale,
meaning that translations for attributes that were the same as
the attribute values in the default locale were not being loaded.
Fixes #2134.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The code here was hard to follow. Now we have a cleaner path to decide
whether to show the Make Request button or not.
- Always show any notes associated with the body
- If a request can be made to the body
- Show any tag-specific notes that may affect the request
- Show the Make Request button
- If a request cannot be made to the body
- Show the most relevant reason why a request cannot be made
Added PublicBodyHelper#public_body_not_requestable_reasons to extract
the logic of finding the reason a user can’t request out of the template
|
| | | |
|