The title is fairly self-explanatory. Essentially, any comment posted to a blog entry will show that it was submitted by the blog post author, NOT the comment author. Ownership and author displayed during editing appears to be correct. I have not verified if there are any issues with database records regarding this bug.
The code in painted/comment.tpl.php causing the bug is:
<div class="submitted">
<?php echo t('!date by !name', array('!date' =>
format_date($comment->timestamp, 'medium'), '!name' => theme('username',
$node))); ?>
</div>
The same template from the bluemarine theme provides working code for comment author attribution. A very simple fix to the above using code from bluemarine is:
<div class="submitted">
<!-- <?php echo t('!date by !name', array('!date' =>
format_date($comment->timestamp, 'medium'), '!name' => theme('username',
$node))); ?> -->
<?php print $submitted; ?>
</div>
Comments
Comment #1
Anonymous (not verified) commentedCool, I totally overlooked that detail.
I'll commit the fix asap
Comment #2
evilalien commentedOh, it's in 1.3 too, just confirmed :)
Comment #3
Anonymous (not verified) commentedfix commited to dev
Comment #5
herculesksp commentedI dont believe that is really a fix. That is just a workaround. You are removing the theming by commenting out that code. Oh and it is still not fixed in the latest 6.x-1.3 release.
Anyway, I spent some time with this today and I found a solution. A different one if you may please.
In the part of the code, in line 13, that towards the end, says
theme('username', $node)
the $node returns the name of the author. Instead replace this with the code snippet
theme('username', $comment)
As simple as that. $comment contains the author name of that comment itself. And this will be extracted and is themed appropriately.
Now if someone can either release a patch or fix this in the future releases, it would be great. At least until I read about creating patches and how to do bug fixes, if someone else can do it instead.
Many thanks,
Prashanth.
Comment #6
Anonymous (not verified) commentedThe fix is in the dev version, submited in december, but there is no official version yet.
Use the dev version, it is stable.