| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
| |
should never have been pushed in the first place. Sorry!
Revert "Revert "Revert "In the API, when parsing posted responses, assume all multipart mail parts that are Tempfiles are attachments"""
This reverts commit 49ff1a1c0304cd292d3eae80dc0b91b2f83727b9.
|
|
|
|
|
|
| |
multipart mail parts that are Tempfiles are attachments""
This reverts commit d4a700da1760fc2ba09cf19613a995569e4965ea.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
parts that are Tempfiles are attachments"
This change makes the tests fail, I think, and doesn’t have
(IMHO) a desperately strong rationale, so let’s try it without
for now.
This reverts commit 4490482cedf362390b25efe453232ac1b7dfce99.
|
| |
| |
| |
| | |
that are Tempfiles are attachments
|
| |
| |
| |
| | |
something, even when there are no errors.
|
| |
| |
| |
| | |
"external request" changes (mainly that InfoRequests no longer necessarily have a User).
|
| |
| |
| |
| | |
(including from themes). Fixes #524
|
| |
| |
| |
| | |
CensorRules that aren't attached to a User or Request or Public Body (but don't expose this in the admin UI). Fixes #33
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We need not only new requests, but new outgoing correspondence
of any sort.
The idea is that this feed will contain any event that would have
triggered an email to be sent to the public body, so can be used
as an alternative, equivalent way to stay up-to-date with happenings
on WDTK (or the Alaveteli installation of choice).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Gemfile.lock
script/handle-mail-replies
script/handle-mail-replies.rb
spec/controllers/request_controller_spec.rb
|
| |\ |
|
| | |
| | |
| | |
| | | |
purging set up
|
| | |
| | |
| | |
| | | |
Relatedly, document the consequences of getting the Varnish config wrong; and make it easier to grep for problems with Varnish in the log.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
files. Closes #428"
This reverts commit 506af7a640f63b17000ccfc5e1344bbc3039c913.
See issue #428 for a discussion
|
| | |
| | |
| | |
| | | |
requested the attention, not the user who made the original request.
|
|\ \ \
| |/ /
|/| | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
I can’t see any way the error could be triggered by the caller, anyway.
|
| | |
| | |
| | |
| | |
| | | |
I struggled to understand this comment. I hope the new wording is
clearer.
|
| | |
| | |
| | |
| | |
| | |
| | | |
"when using the API",
it "should create a new request from a POST",
AND IT DOES!
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
An authenticated API for public bodies. So far just one method
is implemented, which gives the details of a request in JSON
format.
|
| |/
| |
| |
| |
| |
| | |
URLs such as http://localhost:3000/en/request/106.json should
be redirected to the corresponding named URL, including the
.json on the end.
|
|/
|
|
| |
uploaded in the dry-run. Fixes #507
|
|
|
|
|
|
| |
Backslashes are interpreted twice inside backticks, once by Ruby
and a second time by the shell, so you need twice as many as you
think you do.
|
|
|
|
|
|
|
|
|
|
|
| |
> 10) admin debug (https://secure.mysociety.org/admin/foi/debug) - "you
> are" - sentence that isn't finished
>
> 11) admin debug (https://secure.mysociety.org/admin/foi/debug) -
> versioning incorrect & URLs to github malformed:
> Alaveteli version: 0.5.2-297-g4ec7f6e
> Alaveteli branch: (no
> Alaveteli commit: 4ec7f6edbf2c00abc8464eafc889047f43533f90
|
| |
|
|
|
|
| |
When a request is hidden by an admin, allow the subject line to be specified.
|
|
|
|
|
|
|
| |
Make the "report request" button submit a POST rather than a GET
request. Also restrict this action to logged-in users.
Fixes #501.
|
|
|
|
|
|
|
| |
It’s weird that there’s so much code here that implicitly
assumes File.dirname(__FILE__) is an absolute path, because
really in general it very much is not! This assumption was
invalidated by the recent bundler-awareness changes.
|
|
|
|
| |
browser language; and make the tests pass.
|
|
|
|
| |
HTTP_REFERER for subsequent redirect.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Change "email me about stuff" wording to "follow" throughout
* Introduce a new flag that the user can set, which controls if they get email alerts
* Add a new link to a "wall" for logged in users where they can see a feed of all the things they're following
|