Author: thatguyfromthatshow
Description:
"Force comment" for edits is extremely useful even for old-school editors.
There are javascript solutions for this so that a popup appears if an editor
hasn't added a comment when SAVING an edited page.
I suggest that in user preferences that "force comment" notifications be the
default selection.
Thanks for your time ~~~~
Version: unspecified
Severity: enhancement
avarab wrote:
There's a very good reason for why we don't do this, having no comment at all is
better than having "asdfasdrtawer" because that's what you're going to get when
you force users to enter something.
robchur wrote:
(In reply to comment #1)
I'd imagine some users would find it useful to be able to force themselves to
enter one. I disagreed with the original suggestion to have it on by default.
thatguyfromthatshow wrote:
(In reply to comment #1)
There's a very good reason for why we don't do this, having no comment at all is
better than having "asdfasdrtawer" because that's what you're going to get when
you force users to enter something.
Yes, but then they'll get TALK comments about why they shouldn't do that sort of
thing instead the larger amount of "comment foo!" comments that currently get
posted.
robchur wrote:
Added in CVS HEAD. Simple enough; if the preference is switched on (defaults to
not) then a user leaving an edit summary blank (totally blank, I haven't coded
round the automatic bit yet) will be bounced back to their edit form with a
reminder to enter one. This bounce happens once only, so if the user doesn't
want to provide one for a one-off edit, they aren't going to enter a vicious cycle.