summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2007-11-28 07:42:38 -0500
committerJoey Hess <joey@kitenet.net>2007-11-28 07:42:38 -0500
commitc629d790d81fff25b592db6dc17a5430e950da2d (patch)
treeeb5f4bd58e6e8eb16f39616569b55ed2b947a6f1 /doc
parenta1088212eeb2714723154f9f0988fbf59b45a2d2 (diff)
web commit by http://www.larted.org.uk/~dom/: add question
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
index 9382056da..132fecaa5 100644
--- a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
+++ b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
@@ -12,3 +12,9 @@ In our team internal wiki, we wish to impose a policy that all edits must have a
> BTW, it wuld probably be better to validate against a `comment_regexp`,
> so that when the evil admins notice that /.+/ is absurdly easy for users
> to get around (by using " "), they can tighten it down. --[[Joey]]
+
+> Sorry for being dense, but I don't see a way to modify the template from within
+> a plugin, without providing a whole new template for editform, which obviously
+> isn't a workable solution. If the template was modified to allow overriding the
+> portion of the message in question, then I agree that a plugin couuld do the rest.
+> Thoughts appreciated :) --[[Dom]] \ No newline at end of file