does this restrict with a option to certain contenttypes ONLY ??
it would have to be i guess because you need an input field for the comment ???
EDIT: i looked at your site and i see that the subject ONLY is filled it ?? or is there an actual default comment that is filled in for the commenter to edit?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2008-10-06 comment_subject 6.x-2.x-dev.zip | 2.87 KB | arhak |
Comments
Comment #1
ahoeben commentedIt's purely about comment subjects, not the comments themselves. Like the name suggests...
Comment #2
arhak commentedsolving this and #318438: Support for other kind of default subjects, please test it and do some code clean up since I kept old code as comment blocks
new code is commented
Comment #3
ahoeben commentedIt's not that I don't appreciate your efforts, but I still think that all three of your use cases (numeric, author, date) can and should be implemented through theming. I am open to discussion though, so I will leave this issue open for now.
Comment #4
chasz commentedhi, themeing is great for the server admin but for the site admin is best to administer from the browser. and thats what CMS's are supposed to do
if you have been replying on the drupal.org forums, you would have noted that the first line of the reply is the line that goes on the comment title....i would prefer this than just rehashing the old title being replied to. when people realise that the first 300 characters make their title, they will gear an "abstract" to the title.
what i am interested in is in the textarea for the replies
eg reply template for bugtracking
Windows version:
CPU:
GPU:
RAM:
Problem description:
a "guided" reply template that users can add to and fill in, rather than generate more dropdowns from comment_CCK etc
Comment #5
arhak commented@chasz I like your idea of a guided reply template, but I think you should open a different issue with the title "guided reply template" (but probably will end up with a "won't fix" because this module's name is comment_subject, you really need a fresh new module for that purpose)
@chasz besides the above, I was replying this issue's title and original description
And the proposed patch solves that issue (meaning this issue thread).
Comment #6
arhak commented@ahoeben please, lets talk about the content type discrimination in this thread, as it's the original topic
review the proposed patch (which also does the other kind of default subject) and lets discuss the other matter in the other issue #318438: Support for other kind of default subjects
Comment #7
arhak commented@ahoeben please, lets talk about the content type discrimination in this thread, as it's the original topic
review the proposed patch (which also does the other kind of default subject) and lets discuss the other matter in the other issue #318438: Support for other kind of default subjects
Comment #8
ahoeben commented@chasz: That's just not what this module does, sorry. This module just fills in the comment subject line with a sensible value. It does not change the structure of comments, and it never will.
@arhak: For the current version of the module, there is no use to differentiate between different content types. So I am closing this issue. I have given the whole issue some more thought, and using token.module is going to be the way forward. So I am reopening that issue, and comments should go there: #318443: Integration with token (new branch request).