| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
Allow the same params (since_event_id, since_date) for both formats.
There doesn't seem to be a particular reason not to treat them the same.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
includes various code layout fixes
|
| |
| |
| |
| | |
operation
|
| |
| |
| |
| | |
Filters; more 403s, fewer 500s; added logging; less duplication
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
In render calls, that's now deprecated in favour of using the :formats
option.
|
|
|
|
| |
Set to 'waiting_response' on creation, to match the displayed state.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Gemfile
Gemfile.lock
app/controllers/admin_request_controller.rb
app/controllers/admin_track_controller.rb
app/controllers/request_controller.rb
app/controllers/services_controller.rb
app/helpers/link_to_helper.rb
app/mailers/request_mailer.rb
app/models/application_mailer.rb
app/models/info_request.rb
app/views/admin_censor_rule/edit.html.erb
app/views/admin_censor_rule/new.html.erb
app/views/admin_public_body/_form.html.erb
app/views/admin_public_body/_locale_selector.html.erb
app/views/admin_public_body/_one_list.html.erb
app/views/admin_public_body/edit.html.erb
app/views/admin_public_body/list.html.erb
app/views/admin_public_body/new.html.erb
app/views/admin_request/_incoming_message_actions.html.erb
app/views/admin_request/edit.html.erb
app/views/admin_request/edit_comment.html.erb
app/views/admin_request/edit_outgoing.html.erb
app/views/admin_request/list.html.erb
app/views/admin_request/list_old_unclassified.html.erb
app/views/admin_request/show.html.erb
app/views/admin_track/_some_tracks.html.erb
app/views/admin_track/list.html.erb
app/views/admin_user/edit.html.erb
app/views/admin_user/list.html.erb
app/views/admin_user/show.html.erb
app/views/general/_footer.html.erb
app/views/general/exception_caught.html.erb
app/views/help/contact.html.erb
app/views/layouts/default.html.erb
app/views/public_body/_alphabet.html.erb
app/views/request/_request_listing_single.html.erb
app/views/request/_sidebar.html.erb
app/views/request/new.html.erb
app/views/request/show.html.erb
app/views/request_mailer/external_response.rhtml
app/views/request_mailer/fake_response.rhtml
config/environment.rb
config/environments/production.rb
config/routes.rb
spec/controllers/admin_censor_rule_controller_spec.rb
spec/controllers/request_controller_spec.rb
spec/controllers/track_controller_spec.rb
spec/helpers/link_to_helper_spec.rb
spec/mailers/request_mailer_spec.rb
spec/models/info_request_spec.rb
spec/spec_helper.rb
spec/views/public_body/show.html.erb_spec.rb
spec/views/request/show.html.erb_spec.rb
vendor/plugins/rails_xss/lib/rails_xss/erubis.rb
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
actionmailer uses mail under the hood
|
|/ |
|
|
|
|
| |
error, so that notification emails don't get sent.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The API was returning Rails (HTML) errors for certain error
conditions, which is inconvenient because it makes it difficult
for the client to extract the error message.
This patch changes add_correspondence to return JSON errors
(still with suitable HTTP status codes) for two common exceptional
conditions, and adds tests.
|
|
|
|
|
|
| |
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.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I can’t see any way the error could be triggered by the caller, anyway.
|
|
|
|
|
|
| |
"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.
|