I tried to override text field in comments and i figured out:
Text shows "field nme: current state >> new state" instead of "field nme: old state >> new state"
so, all comments look like changing curent value to their own, like that:
field one: bar >> foo
field one: bar >> bar
field one: bar >> foo
field one: bar >> buzz
where last comment sets field to "bar" again and initial value is not shown at all.
I suppose
field one: test >> foo
field one: foo >> bar
field one: bar >> foo
field one: foo >> buzz
wil be much more useful.
Comments
Comment #1
fasdalf@fasdalf.ru commentedI figured out that function comment_cck_comment(&$comment, $op) has a line #120
But $previous_vid variable was not initialised in this function before, so previous revision ID becomes zero. This makes drupal to load current revision.
Comment #2
fasdalf@fasdalf.ru commentedi've added a line
just before line 120 and now module works well for new comments.
Comment #3
fasdalf@fasdalf.ru commentedI'm not sure if i should assign it to myself since i can't apply changes to CVS
Comment #4
aren cambre commentedComment #5
Hiroaki commentedthanks for the help, im adding the line, this module seems to be bugged a lot :P
Comment #6
Hiroaki commentedThis works like magic.
It even fixed the status history showing up on wrong comments. (the one right above!!!)
Comment #7
Azol commentedBefore adding this SELECT to the module I'd advise you to have a look at stable module version (1.0 beta2). It seems to me the author (or the maintainer rather) has rewritten a part of the module without paying much attention to the original text of this function:
Basically what happened is
$previous_vid = $node->vid;was completely dropped from newer version, breaking it functionality.Alternative solution would be just reverting this change (using the snippet I have provided). And we're keeping DB engine happy!
Comment #8
Azol commentedChanging this back to Needs work, because I still believe just adding another SELECT is not the best way to fix this problem (esp. performance-wise).
This module is very useful, but I am not sure if original author is watching it. Any undertakers?
I can assemble a new version of this module, incorporating some of the fixes, but I do not think I will have time to check it into CVS or maintain it.
Comment #9
aren cambre commentedFollowing #8: #725704: Comment CCK seems abandoned
Comment #10
Azol commentedapplied to dev. branch