aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfrancis <francis>2009-07-28 11:50:41 +0000
committerfrancis <francis>2009-07-28 11:50:41 +0000
commit27fd1ba52231c685f430265007d6068b32f66f46 (patch)
tree3c917f538e927a5adc448b3d2c1663c2cf3baad3
parent54e05bbf92068a2e26aa61126af7478ab5e6fc7e (diff)
Tidying.
-rw-r--r--todo.txt11
1 files changed, 4 insertions, 7 deletions
diff --git a/todo.txt b/todo.txt
index 4f22be446..9d96e2b61 100644
--- a/todo.txt
+++ b/todo.txt
@@ -82,7 +82,10 @@ Then will help logged in users too.
Later
=====
-Test for duplicate followups, as we do requests.
+Let requesters view the uncensored versions of their correspondence (e.g. with
+emails in it). Let other people do so with a CAPTCHA?
+
+Test for duplicate followups, as we do for requests.
For followups, have radio button to say is it a new request or followup
Do by uncommenting the "new information" option when writing a followup, so
@@ -231,12 +234,6 @@ Test code for FOI officer upload
Test code for rendering lots of different attachments and filetypes
Test code for internal review submitting
-http://www.whatdotheyknow.com/list/successful - too many ombudsmans.
- Radical would be to group by user, regardless of subject; less radical to
- collate those with same/similar subject.
-http://www.whatdotheyknow.com/list?page=2 - too many monitoring officer
- reports - similar to above, I reckon.
-
Protect from CSRF with this in app controller (care it doesn't break anything):
# See ActionController::RequestForgeryProtection for details
# Uncomment the :secret if you're not using the cookie session store