Posted by ceardach on December 28, 2009 at 6:57am
4 followers
Jump to:
| Project: | Comments in a View |
| Version: | 6.x-1.0 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
What is the difference between using this module, and replicating the behaviour with Views Attach?
Comments
#1
I haven't looked closer at this new module yet. But if I understand things correct, the same behavior could (in some cases) be accomplished with Comment Block. That module removes the default comment listing from nodes and creates a default view with a block display that can be placed anywhere on the page. It also places the comment form in a block.
#2
dixon_, you might be right on that count -- I had done some cursory hunting but hadn't spotted Comment Block, and so whipped this module up to provide just the feature I needed -- zero-configuration switching of comments to Views.
It might be worth nuking this module and just moving to comment_block. Does it REQUIRE that the comment posting form be migrated to a block, or can it remain 'in place' as it is by default?
#3
Actually, I just looked -- unless I'm mistaken Comment Block uses views_attach to do the heavy lifting, which means that there is no easy way to position the comments and the comment form below a node's links without doing some heavy theming. Perhaps I'm missing something?
#4
If you can merge the 2 projects together that would be ideal; the less fragmented the better IMHO. If you do end up merging I would still want to look into loading of comments via an ajax callback. See #668542: AJAX loading of this view?