aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Make handle-mail-replies tests pass againRobin Houston2012-06-07-3/+3
|
* Update tests to reflect code changesRobin Houston2012-06-07-0/+23
| | | | | Since users must now be logged-in to report requests, the tests need to reflect this.
* Update test for e3cfe550fe835c68b25d693abd40aedd954913b3Robin Houston2012-06-07-1/+1
| | | | | The wording that was changed by e3cfe550fe835c68b25d693abd40aedd954913b3 turns out to be relied on by one of the tests.
* Add missing </p>Robin Houston2012-06-07-1/+1
|
* Renumber clashing migrationRobin Houston2012-06-07-0/+0
|
* Remove duplicate from Gemfile.lockRobin Houston2012-06-07-1/+0
| | | | I think this was a bad merge during the recent rebase of this branch (feature/public-body-api)
* Don’t try to send alerts to external usersRobin Houston2012-06-06-1/+6
|
* Non-logged-in users can create requestsRobin Houston2012-06-06-3/+3
| | | | | Make the info_request validation a bit more forgiving, so that non- logged-in users may create requests.
* Fix user links for external usersRobin Houston2012-06-06-4/+11
|
* Fix indexing of info_request_eventsRobin Houston2012-06-06-1/+14
| | | | | Even external requests need to be indexed, for which we need a slug representing the user.
* PublicBodyVersion doesn’t have api_key eitherRobin Houston2012-06-06-1/+1
|
* Handle external usersRobin Houston2012-06-06-1/+9
| | | | Requests may now have been made by an external user.
* Initialise API key in the modelRobin Houston2012-06-06-2/+6
|
* Use our xapian-full from rubygemsRobin Houston2012-06-06-7/+1
| | | | As in the develop branch.
* WIP attachment uploading via APIRobin Houston2012-06-06-5/+41
|
* Test for attaching a file via the APIRobin Houston2012-06-06-0/+36
| | | | Not yet implemented, so the test fails.
* Correct comment\Robin Houston2012-06-06-1/+1
|
* Use a fixture for the external requestRobin Houston2012-06-06-4/+39
|
* Fix typo in fixture yamlRobin Houston2012-06-06-2/+2
| | | | | I’m sure created_at should not have been there twice. Presumably the second one was supposed to be updated_at.
* API: Some testing of show_requestRobin Houston2012-06-06-0/+14
|
* API: test also for refusal conditionsRobin Houston2012-06-06-0/+39
| | | | | | The API must not allow people to update requests that they shouldn’t, i.e. only requests that were created by the same public body, using the API, can be added to using the API.
* API: add followup to requestRobin Houston2012-06-06-13/+61
| | | | You can add a followup to a request using the API.
* API: we can add a response to a requestRobin Houston2012-06-06-1/+150
|
* Fail less bafflinglyRobin Houston2012-06-06-1/+9
| | | | | | Fail in a less baffling way if the raw email is associated with an incoming message or an info request that has not yet been saved to the database.
* Remove obsolete commentRobin Houston2012-06-06-5/+0
| | | | That comment makes precisely no sense whatever, any more.
* more commentsRobin Houston2012-06-06-0/+3
|
* Just include all the error messagesRobin Houston2012-06-06-5/+1
| | | | I can’t see any way the error could be triggered by the caller, anyway.
* Improve explanationRobin Houston2012-06-06-2/+4
| | | | | I struggled to understand this comment. I hope the new wording is clearer.
* API create_request method is workingRobin Houston2012-06-06-21/+44
| | | | | | "when using the API", it "should create a new request from a POST", AND IT DOES!
* Work in progress on getting new APIController test to pass. They don't, yet!Seb Bacon2012-06-06-1/+21
|
* Fix test and fixtures so they only fail due to missing business logic ↵Seb Bacon2012-06-06-4/+11
| | | | (corrected typo, added missing fixture data, etc)
* Test for creating a new request via the APIRobin Houston2012-06-06-0/+33
| | | | This is not yet implemented. Test first!
* Reorder methodsRobin Houston2012-06-06-4/+4
|
* Authenticated APIRobin Houston2012-06-06-0/+54
| | | | | | An authenticated API for public bodies. So far just one method is implemented, which gives the details of a request in JSON format.
* Redirect numeric request URLs in JSON mode tooRobin Houston2012-06-06-1/+1
| | | | | | URLs such as http://localhost:3000/en/request/106.json should be redirected to the corresponding named URL, including the .json on the end.
* External requestsRobin Houston2012-06-06-1/+39
| | | | | Add data model support for “external” requests, i.e. requests added via the API rather than made using the site.
* Correct syntax for making column NOT NULLRobin Houston2012-06-06-1/+1
|
* Generate an API key for each public bodyRobin Houston2012-06-06-1/+20
|
* Add the annotate gemRobin Houston2012-06-06-2/+8
|
* Remove gem spec from environmentRobin Houston2012-06-06-2/+0
| | | | This was causing me strange errors, and we think is not needed.
* Switch to robinhouston/xapian-full temporarilyRobin Houston2012-06-06-1/+7
| | | | | It just has a small fix for Mac compatibility. This can be reverted when Seb has merged the fix back to his fork.
* Merge branch 'wdtk' into developRobin Houston2012-06-05-9/+13
|\
| * Multi-theme support for custom routesRobin Houston2012-06-05-2/+8
| | | | | | | | | | A simple mechanism for allowing multiple themes to register custom routes.
| * Let everyone know, not just usRobin Houston2012-06-05-1/+1
| |
| * Silly syntax bugRobin Houston2012-06-04-2/+2
| | | | | | | | | | | | 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.
| * Fix admin debug methodRobin Houston2012-06-04-6/+4
| | | | | | | | | | | | | | | | | | | | | | > 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
* | Remove WDTK-specific config variablesRobin Houston2012-06-04-5/+0
|/
* Log an event when a request is hiddenRobin Houston2012-06-04-1/+12
|
* trailing whitespaceRobin Houston2012-06-03-1/+1
|
* Copy the admin team on messages sent to usersRobin Houston2012-06-03-0/+1
| | | | | When a user is notified of a request having been hidden, BCC the site admin team.