What if you need comment?
Michelle - August 10, 2007 - 00:32
| Project: | Node comments |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I was all ready to do a fivestar + nodecomments combo to replace userreview... Then I read the docs and how I have to disable the comment module. One problem with that:
Required by: Comment mover (enabled), Comment upload (enabled), Flat comments (enabled), Forum (enabled), Quote (enabled)
So am I out of luck? I can live without comment mover and comment upload is moot if I'm replacing them with nodes and flatcomment is probably not needed, either, if I'm using views to display the "comments". But I need forum and quote. Can those be made to work with this module?
Thanks,
Michelle

#1
This is the problem with the nodecomment approach. In the end, I'm pretty convinced that the only two solutions that make any sense are to make comments nodes at the Drupal core system level (unpopular amongst the core team), or to make tools like CCK, views, and fivestar work with with native comments. The nodecomment route, while very attractive for many reasons, will never be able to keep up with all of the tools available for normal comments. Now, fortunately, any of the tools you just mentioned can basically be ported to use nodecomment just by doing a search/replace on the tables (comments -> node_comments) and the functions (comment_render -> nodecomment_render as an example). So determined developers should be able to port comment mover and the others with little effort.
#2
It may just be a search and replace but I'd rather not go that route if I can do it without hacking core modules. I'm going to attempt to do it with cck, views, fivestar and some custom theming to glue it together. Wish me luck :)
Michelle
#3
I'll not only wish you luck... I'll help you out if I can =) I wanted to emphasize in my last comment, though, that nodecomments are not an easy road to walk, and might lead to a long-term dead end if the problem is solved in a drastically different manner. However, one can mitigate that risk by working towards confluence (as you've proposed).
#4
Help would be great :)
This really isn't a nodecomment issue anymore so I've created a new issue for it here: http://drupal.org/node/166509
Michelle
#5