Posted by gusaus on February 24, 2007 at 10:58pm
Enabled sitewide
36% (27 votes)
Disabled sitewide
28% (21 votes)
Let each group admin decide
35% (26 votes)
Total votes: 74
Should comments on Wiki pages be enabled or disabled by default?
Group organizers
Hot content this week
-
1 day 19 hours ago
-
3 days 48 min ago
Comments
Wikis with long tails?
The reason I would go for a wiki for certain types of content is to avoid scrolling through a long tail of comments. Any changes in a wiki would be edited in or out and saved in history, not added as a series of comments. Otherwise, why don't we just use the regular forum format if we want comments?
Agreed
I'd much rather see the "talk" or "comment" pages on a separate tab of the wiki-type node. It gives people the opportunity to discuss the article and changes/revisions without cluttering the actual content it self. I like the idea of a forum-style "talk" page.
Definitly a tab w/a view of new content
+1 on the removal of personal info on wiki pages... perhaps a list of users who have contributed to the page on a block would make more sense, since it's still nice to get credit.
You could make a view for nodes, using CCK + nodereference... where the url would be node/$arg/talk, the view would look just like a forum, (or any other view layout). This would really allow for diverse discussion, almost like drupal's issue tracker... we could even add a vocabulary with something like Type: Question, Idea, Discussion, Random. Add this vocab as a field in the view, add an exposed filter for type, and you have yourselves a talk page for each node with neat filters to switch between questions, discussions, etc.
Of course for it to be easy, you have to have an "Add" link, which you can put in the header of a view. With a little form themeing, you can pass a $_GET var to the nodereference field, and make it a value.... something like this:
l('Add Topic', 'node/add/topic?field_node=234', array(), drupal_get_destination());
$form['field_node']['#type'] = 'value';
$form['field_node']['#value'] = $_GET['field_node'];
Jon Pugh
Founder & CEO
THINKDROP
open source consulting
http://thinkdrop.net
This is a great idea, and
This is a great idea, and definitely one that I did not realize was possible. I'm still learning the plumbing of Drupal here. How would you suggest adding a tab to the node so people could access the talk page?
Figured it out!
Basically just took Tschannen's module (http://drupal.tschannen.net/fileview/files/archives/23/files/talk/talk.m...) and commented out all modules except for talk_menu and talk_form_alter. This works quite nicely, and the URL points to the "talk" view I created, which works almost like an "issue" tracker.
Ok, so you don't actually
Ok, so you don't actually need a separate module to add that "talk" tab. Turns out there's a menu option in Views to add a tab to the page, and it works quite nicely. Just posting this comment here in case anyone comes across my earlier post so they're aware there's a more streamlined way to accomplish this.
Brad
Nice module but I have to
Nice module but I have to modify it to adapt it to my layout because I don't use the tabs on the website I'm working on.
I'm looking for a way to replace the permalink (the titles of the comments) with a direct link to edit them but I don't find where these permalinks are created...
Do you know the solution please ?
Thank you.
I'm with glendac on the long tails issue
I voted no on this, because I think that 42 comments trailing the bottom edge of a wiki page cause that page not to get changed or updated. It's my feeling that people would rather leave a comment on someone's wiki simply because they're afraid to "put words into" the O.P.'s mouth. If we removed the personal info from the node.tpl on wikis, I think many more people would hit that edit button rather than posting a comment.
Comments are necessary for Handbook pages, so people can clarify a point, ask a more in-depth question, or leave spam for sepeck to sweep up. Comments on forum posts are what creates, well, a forum. Comments on wikis are nothing more than a p.i.t.a. (Not to be confused with p.e.t.a., the group that mercilessly slaughters animals for black-market profits...)
Let's not enable comments by default. If a site maintainer needs to turn on comments for a particular wiki, then so be it. Group creator/owners seem to have the power to enable comments for their own wiki posts, which is good if they need to solicit feedback about a particular chunk of code which must also be edited by that group. The rest of us need to dive into a wiki page, and be willing to modify a few pronouns here and there.
Joel Farris | my 'certified to rock' score
Transparatech
http://transparatech.com
619.717.2805
Actually...
I think you're exactly right about this. It feels like you're editing someone's personal blog entry or something, and no matter how much you say stuff like, "REALLY! Be BOLD!! Edit the crap out of me!!" people will always lean towards posting a comment instead.
what about notifications of changes?
I agree with what you are saying and perhaps I'm missing something, but from where i stand a drawback of not having comments is also losing a notification that something has changed.
Or has this issue been put to rest in another thread?
--
mike stewart { twitter: @MediaDoneRight | IRC nick: mike stewart }
sometimes you want to
sometimes you want to discuss changes or the content of a wiki page, and doing the discussion inside content sucks.
the trade off is that some people use comments to add information instead of editing the wiki page, but it's not such a big deal since anyone can copy the info from the comment and paste it inside the wiki page.
I'd love to see comments enabled on g.d.o wiki pages ASAP, it's quite limiting this way.
Talk pages
I also like talk pages for wikis, thus I wrote a small module which lets you decide per node type if you want to display the comments on a talk page:
The module: http://drupal.tschannen.net/wiki/talk
A demo: http://test.tschannen.net/wiki/talk_pages
Maybe this can be enabled on the wiki node type.
nice module
nice module. i would consider using that. i wonder though how well it will work in practice because lots of modules link directly to comments on the node page. won't those links break? seems like we might need to rewrite those outbound urls using a custom_url_rewrite() implementation. see http://api.drupal.org/api/HEAD/function/drupal_get_path_alias
i wrote a core patch for this 'comments as tab' but it was never quite polished enough - http://drupal.org/node/24804
You are right, the comment
You are right, the comment links get broken. Didn't think about that, but I will look at the url rewrite function.
This would actually fit better into core since I rely (again) on a dirty trick to get it working ;)
The comment module could handle this a lot nicer.
custom_url_rewrite
I looked at custom_url_rewrite but the problem is that it only addresses the path of a link. The comment part '#comment-123' is added as a fragment to the link and the custom_url_rewrite never sees this part. So I don't think that the problem can be solved in this way. A reason more to take a deeper look at your core patch ;)
core patch
thanks for investigating ... one quick way to address that is to let custom_url_rewrite() mangle the whole url, including fragment. would be a smaller patch.
last roadblock removed?
my patch was just accepted into HEAD. we now have custom_url_rewrite_outbound() where we can rewrite those comment links.
Nice feature, but...
This is a very nice feature, and would work well for small discussions. However, what if the discussion becomes pretty long or unwieldy? Your module was actually very helpful (see my comment further down) in helping me figure out how to implement a "case tracker"-style system in which people can post a concern or discussion topic which others can comment on. Once the topic has been resolved, it can be closed (and thus removed from the normal view of the talk page) so users can focus on existing discussions.
duplicate module
I just stumbled on this comment here and I must say I was a bit cursing myself. I just developed a similar module: http://cvs.drupal.org/viewcvs/drupal/contributions/modules/comment_tab/
The discussion started here in this thread: http://drupal.org/node/102379
I too hit the comment link problem and tried to solve it with custom_url_rewrite based on Moshes advice.
I'll check out your code first and then decide what to do. Anyhow, you have one more person to help on that core patch.
enhancing the talk module
@rötzi
I have taken the liberty to submit your talk module in my drupal sandbox: http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/toemaz/talk/
You will notice that I enhanced the module a little with a function to redirect to the talk page after posting a comment.
Something about the 'comment urls': as I just recently started my wiki, I don't have links yet on my my website linking to the standard comment url node/$nid#comment-$cid. But besides this, there is also a the problem with the in core 'recent comments' block or views. The output is also the wrong url. The solution for this might be to provide a new block or view.
Last idea: there is someone who posted another option for creating talk pages. Make a shadow forum topic for the wiki page (http://drupal.org/node/122839). If we will not be able to solve this current comment url issue, then this might be the next test.
Disabling the permalinks
Is it possible to simply disable these permalinks and replace them by "edit" links ?
rewrite patch
both of those issues can be solved if this patch gets in: http://drupal.org/node/150049. please review it if possible.
hoping this discussion can continue
Looks like the patch got in, so what now?
rename "talk" to "discussion"
I like the talk tab at the top of the wiki page. But I would rename the "talk" tab to "Discussion". I think this would be more clear to a new user, and it also matches up with the way wikipedia/mediawiki does it.
I would enable comments by default, and I would have them displayed on the "Talk (discussion)" page, not at the bottom
Cheers! Ricco
I prefer "Discussion" as well
I prefer "Discussion" as well and have been using the locale module to rename the Talk module's "Talk" tab. Presumably the "very fast t()" method described at http://drupal.org/node/131061 could be used as well.
Wikipedia does use that word in the tabs but still refers to the discussions as Talk Pages.