web commit by http://www.larted.org.uk/~dom/: add question

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 9382056da8aaf981dcc2b5d43ad514b46e65a074..132fecaa5c53a6cabc295c3b7b0b2dfead694c0d 100644 (file)
--- 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]]
 > 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