Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Using node_view to view large numbers of comments is obviously going to be a poor performer. Create a view that prints the body etc. This will require creating a 'links' field that tries to run hook_link on a faked up node, but the rest should not be too difficult.
This should create a specific style (node comment?) that tries to mimic node.tpl.php as much as possible so that the theme templates will be as interchangeable as we can make them.
Comments
Comment #1
merlinofchaos commentedComment #2
merlinofchaos commentedTagging
Comment #3
merlinofchaos commentedAn alternative to this may be to use caching by getting eaton's caching patch committed: http://drupal.org/node/468824
We could then write a caching plugin that caches comments per role and uses the 'updated' field of the node. we would need to ensure that whenever a comment node was updated, the parent node would also be marked updated. Then, we don't need to worry about dirtying the cache. The cache plugin can check the updated date of the node. If it is newer than the date on teh cache, dump the cache, render and re-cache.
This would only cache the comments view, not the node itself.
The only problem is that if there is user specific content in the comments (such as special hiliting for friends of the logged in user) but if that's the case, the caching can always be turned off. This strikes me as a lot less development work than using a fields type view, and will be much more compatible. Also, higher performing since cached comments will be even faster.
Comment #4
crea commentedClosing all issues. Please reopen if still relevant with Node Comments 6.x - 2.x