Closed (duplicate)
Project:
Drupal core
Version:
6.x-dev
Component:
node system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2007 at 20:29 UTC
Updated:
4 Feb 2011 at 16:04 UTC
Jump to comment: Most recent file
Comments
Comment #1
arthurf commentedWoops, give this the wrong status
Comment #2
jlambert commentedSeems like a no brainer. Patch looks good without trying it.
Comment #3
dmitrig01 commentedthis needs to use the theme registry. Also, eaton is on the job (issue # not handy ATM) && features don't get into 5.1
Comment #4
panchoEaton's reworked node rendering is on #134478, but is scheduled for D7.
For D6 this Stop gaps measure is just right. I reworked the original patch:
Did some basic tests ensuring nothing is broken. Didn't test the themeability though. Maybe someone could do that...
Comment #5
panchoComment #6
pwolanin commentedwell, I'm in favor of this as a stop-gap, since the hard-coded behavior of appending the rendered comments is just wrong and inflexible.
Comment #7
moshe weitzman commented#350984: Kick comment rendering out of node module
Comment #8
spiffyd commentedAny documentation as to how one can reposition the comments and comments form after applying the patch?
Comment #9
j0rd commentedBOOOO. This sucks. Troll.
Sorry, just frustrated with this 3 year old "bug". Anyone have any reasonable solutions. or am I hacking core at this point?
Comment #10
arthurf commentedFYI, you can get around this issue by doing something like:
<?php
function custom_preprocess_node(&$vars, $hook) {
// You will need to set some conditions for when you want to do this
if ($vars['node']->comment) {
$vars['comments'] = comment_render($node);
// Now we unset the comments so that comment_render() is not called in node_show()
unset($node->comment);
}
}