Emails containing a comment's contents, such as those listhandler sends, are particularly unfriendly because the default subject line, which is often not changed, is quite arbitrary. Using 'Re: parent's subject' is a bit better.

I did a bit of code cleanup around the lines I changed as well.

CommentFileSizeAuthor
comment.module_11.diff3.9 KBdrumm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Steven’s picture

I thought the consensus was that Re subjects were evil? "Re" serves to indicate which message replies to what in emails. With threaded support in mail clients that's now becoming obsolete too, but in Drupal I see no need whatsoever to imitate this bad practice.

This line:
$edit['subject'] = truncate_utf8(decode_entities(strip_tags(check_output($edit['comment'], $edit['format']))), 29, TRUE);

is the result of a long discussion about comment subject autogeneration. In light of various input formats, mandatory / disallowed subjects, this seemed like the best idea.

factoryjoe’s picture

I think I want to +1 this, but I also think that the extra clutter in the web UI would be distracting. I think that comment titles should be optional -- and the email notifications that go out w/o a subject should grab the parent's subject like Drumm has done. So the real difference that I'm suggesting here is to allow for titleless comments, since people often write title-less comments anyway. Forcing a title only helps w/ email integration.

Chris

killes@www.drop.org’s picture

Project: Drupal core » Listhandler
Component: comment.module » User interface

This should be somehow handled by listhandler. Preferably by educating users to use proper MUAs which acn do threading without Re:s in subjects.

When in doubt use a bigger club.

killes@www.drop.org’s picture

Or get a consultant to implement your feature wishes. Done. Will be uplaoded later today.

Anonymous’s picture

Anonymous’s picture

drumm’s picture

Status: Fixed » Closed (fixed)