Add "New" marker on new comments

I have this issue as well.

subscribe

And because comments became nodes using this module (and because new marker concerns only core comment module) this is definitely not a bug, but a feature request. And I second this request, because new marker gives comfort of finding and reading new comments.

Looking into the code of node-comment.tpl.php file it turns out that this feature was at least tried to be implemented:

  <div class="subject"><?php print l($node->title, $_GET['q'], NULL, NULL, "comment-$node->nid") . ' ' . theme('mark', $node->new); ?></div>

So since it does not work, then this is not a feature request, but a bug report. Sorry.

Subscribing.

May I mark this as critical so that the issue could get more attention of the developers? It is really uncomfortable to press a link showing a number of new comments on the first page (under the teasers) to get to a node page and start looking for any new updates among numerous comments. For active sites this is a very important issue.

This is not critical. Critical is used when a module is completely broken or is causing site crashes, not to get the attention of the developers, though it is a good way to make some devs mad ;)

Critical may also be the case when a bug or missing feature or design flaw means that the overall usefulness of the module is seriously hit.

(Provided that the issue in question is related to the modules' main function and purpose.)

This issue could well be regarded as in that category.

Sharing DanielTheViking's opinion taking the risk to change this to critical again. Common guys, this issue is crucial to start to use this module, isn't it? Imagine pages with frequently updated comments - how the users are supposed to follow discussions if #new target does not work?! This makes the use of the whole module meaningless.

sorry for bumping, but i can't change the issues' status to critical anymore. i would like to know if the maintainers are going to address the issue at all and if yes when approximately? because now i am building a new website and needed to decide which way to go with it. i really like to transfer to nodecomments, but if this issue will not be resolved soon, then i would have to stick with core comment module. it would be very nice of the modules' maintainers to give little feed back on their plans regarding this issue.

thank you very much!

Thank you Daniel. I hope this will help to turn attention of the gurus to this urgent problem. Without this little feature the use of the whole module is meaningless. I wish I could not only complain and ask, but sit over the code and find out where the problem is. I only could find the above code, but have no clue why it does not work.

After several months I am trying to once again bump the issue. We have been testing a new module on http://www.getnick.com, that enables for users to have multiple userpics per account. Everything is ready to go, but this issue prevents us to launch the project. I am ready to find some money for bounty to push solving this problem.

This is being fixed in #480360: Separate nodecomment.tpl.php templates.

Closing comments (spam)