aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Specify sort on results to return in consistent order.Louise Crow2014-01-28-1/+1
|
* Send batch requests as a cron job.Louise Crow2013-12-04-0/+54
|
* Add a mailer method for sending a batch request notificationLouise Crow2013-12-04-0/+75
|
* Show public body list when batch has not been sent.Louise Crow2013-12-04-17/+53
|
* Update notices for offline sending.Louise Crow2013-12-04-25/+12
|
* Simplify return value, set sent_at in create_batch!Louise Crow2013-12-04-14/+43
|
* Display batch requests for user on 'my requests' pageLouise Crow2013-12-04-2/+34
| | | | This is the most rudimentary possible way to give them access to the batch request urls, pending #1239
* Refactor specs to make adding batch changes easier.Louise Crow2013-12-04-30/+63
|
* Use public bodies not requests in find_existingLouise Crow2013-12-04-10/+12
| | | | The requests may not have been created at this point.
* Split the creation of a batch and the associated requests.Louise Crow2013-12-04-32/+24
| | | | We're going to want to actually create and send the requests later.
* Add association between batches and public bodies.Louise Crow2013-12-04-0/+9
|
* Add list of bodies batch request will be sent to.Louise Crow2013-12-04-9/+54
|
* Javascript enhancements.Louise Crow2013-12-04-35/+156
| | | | Add or remove all buttons, ajax search as you type.
* Raise limit on results to 1000.Louise Crow2013-12-04-3/+3
| | | | | Seems like you have to specify a limit with xapian. We'll probably want to document the limit somewhere on this page.
* Add the specific salutations to each request.Louise Crow2013-12-04-25/+73
| | | | | | Also, wrap model creation in a transaction and do the message sending separately - we may ultimately want to do this outside the request cycle.
* Move creation of batch to InfoRequestBatch.Louise Crow2013-12-04-21/+28
|
* Add a rudimentary view for an info request batch.Louise Crow2013-12-04-2/+46
|
* Notices for success and errors.Louise Crow2013-12-04-23/+62
|
* Add check for double submission.Louise Crow2013-12-04-5/+95
|
* Make method names for finding existing objects clearerLouise Crow2013-12-04-12/+12
| | | | | They're not finding by the existing object, they're finding an existing object.
* Simple code for the happy pathLouise Crow2013-12-04-19/+52
| | | | | Create the batch and associate new requests with it, send the outgoing messages, and redirect to a page for the new batch.
* Use two bodies in specs.Louise Crow2013-12-04-3/+5
|
* Add InfoRequestBatch model.Louise Crow2013-12-04-0/+74
| | | | | Re-annotate models. Index InfoRequestBatches by user - we'll display the batches for a user when they view their own requests.
* Remove extra 'is invalid' error message.Louise Crow2013-12-04-2/+4
| | | | | | This duplicates what's done in the new action, but I can't currently think of a way of sharing functionality that doesn't seem overly complex and/or risky.
* Handle a banned user making batch requests.Louise Crow2013-12-04-1/+20
|
* Factor out common params for clarity.Louise Crow2013-12-04-18/+11
|
* Batch users don't have a daily limit.Louise Crow2013-12-04-2/+11
| | | | | | | It doesn't make logical sense that they would. However I am preserving the ability to make batch requests as a separate thing from not having a daily limit - I think batch sending requires a (perhaps marginally) bigger level of trust.
* Add some specs for existing exceeded_limit? behaviourLouise Crow2013-12-04-0/+24
|
* Pass public bodies list through forms.Louise Crow2013-12-04-3/+14
|
* Require at least one public body in the params.Louise Crow2013-12-04-5/+13
|
* Create template and outgoing messageLouise Crow2013-12-04-23/+102
| | | | | Add validation, preview as in single request creation. Add comments noting further work to be done in this action.
* Isolate code for preparing to display the compose interface.Louise Crow2013-12-04-51/+67
| | | | Reuse it for the batch request page.
* Create a placeholder salutation for a batch request template.Louise Crow2013-12-04-3/+17
|
* Handle the application of censor rules to a batch request template.Louise Crow2013-12-04-1/+10
|
* Add a batch_request_template flagLouise Crow2013-12-04-1/+19
| | | | | | A virtual attribute to use to customise some info request behaviours when we are using one request as a template for creating multiple requests.
* Add new_batch actionLouise Crow2013-12-04-72/+159
| | | | | | Give it basic access control, and add some conditionals to the 'new' template around bits that use @info_request.public_body so that they render something different if @batch is assigned.
* Add template for select_authoritiesLouise Crow2013-12-04-3/+145
| | | | Should retain a list of selected public bodies across searches.
* Handle not enabled, no user, unauthorised user.Louise Crow2013-12-04-15/+77
|
* Add a link to the select_authorities page.Louise Crow2013-12-04-0/+7
| | | | | Contingent on batch requests being allowed, and the session user being allowed to make them.
* Add a select_authorities action.Louise Crow2013-12-04-0/+13
|
* Add new config param - ALLOW_BATCH_REQUESTSLouise Crow2013-12-04-0/+7
|
* Add a can_make_batch_requests flag to user modelLouise Crow2013-12-04-2/+37
| | | | Make it updatable via the user admin page.
* Set enforce_available_locales to false.Louise Crow2013-12-04-0/+1
| | | | | This was the previous behaviour. Setting it explicitly avoids a deprecation warning.
* Upgrade Rails to 3.2.16 to get fixes for CVE-2013-6414, CVE-2013-4491, ↵Louise Crow2013-12-04-29/+29
| | | | CVE-2013-6417, CVE-2013-6415.
* Merge branch 'rails-3-develop' of ↵Louise Crow2013-12-03-9/+19
|\ | | | | | | ssh://git.mysociety.org/data/git/public/alaveteli into rails-3-develop
| * Merge branch 'theme-install-fixes' into rails-3-developMark Longair2013-12-03-9/+19
| |\ | | | | | | | | | | | | Conflicts: script/rails-post-deploy
| | * Try to uninstall the old theme from vendor/plugins and lib/themesMark Longair2013-12-03-8/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The theme install task would fail if there's an old theme present in vendor/plugins, since it doesn't try to uninstall the plugin from that location, only the new location. Then when the install.rb in the new plugin runs, it'll complain that there's a public/alavetelitheme symlink already present. This commit changes themes:install to try to uninstall the plugin from both locations.
| | * Precompile assets only for production.Louise Crow2013-12-03-1/+4
| | | | | | | | | | | | | | | Conflicts: script/rails-post-deploy
| | * Ensure that the lib/themes directory exists before installing to thereMark Longair2013-12-03-0/+1
| | | | | | | | | | | | | | | | | | (An alternative would have been to add an empty lib/themes/.gitkeep file to this directory, but that makes ignoring the installed themes more complicated.)
* | | Merge branch 'feature/1201-close-attachment-files-after-read' into ↵Louise Crow2013-12-03-2/+1
|\ \ \ | |/ / |/| | | | | rails-3-develop
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-03 03:36:26 +0000