When someone with normal user permissions edits a comment, then the time stamp for the comment is changed and 'New' label is shown for other users.

When someone with elevated privileges (I don't know exactly which ones yet) updates a comment, the time stamp is NOT changed and no 'New' label shown.

Original report

For me case https://drupal.org/node/2068471#new has shown as New today, but not in past days and all other follow up comments are not new. This is date-wise impossible.

Screenshot: https://drupal.org/files/issues/2013-12-01_114347.png

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hass’s picture

Issue summary: View changes

Test save

tvn’s picture

This happens when the comment was edited. Not sure if we want to 'fix' this or leave as is. It might be helpful to notify people that the comment changed.

hass’s picture

Nope. The time and date is still the same. This means the comment was NOT edited by the user. That's why I reported it. Otherwise the comment would have a date 1. december, but it's not.

eliza411’s picture

FileSize
52.8 KB
51.13 KB

The date displayed on a comment is the Post date, and it doesn't change when an issue is edited. I'm not saying that's how it *should* work, since a "New" flag doesn't at all describe what's happened with the comment.

Before editing

After editing - date is unchanged

[edit: checking timestamp again]

hass’s picture

This is not correct. See my comment #1 that I just saved half a minute ago. The comment date will be updated to the last comment save timestamp. Aside I'm not talking about the issue date only zhe comment date as you can see in the screenshot, too.

eliza411’s picture

Testing "Posted" date on an edited comment when the comment is added using the full Issue update form. There is no issue summary change on this comment.

eliza411’s picture

Issue summary: View changes

This comment was generated December 8 at 4:28 because the issue summary was updated and so resembles Comment #1. I expect that the timestamp for this edit may get updated like Comment #1.

eliza411’s picture

I am also talking only about the comment date.

I can see that you're having a different experience than I am. Comment #1 DOES shows an updated time stamp exactly as you've described, but when I update comments, the time stamp is NOT updated.

Attempt 1 to get the timestamp of a comment to update

I posted the Comment #4 at December 8, 2013 at 3:27pm

December 8, 2013 at 4:19pm I clicked the edit link for comment #4, added the text [edit: checking timestamp] and clicked "Save"

Comment #4 was now flagged as "New" but continued to show the comment post time: 3:27, even after clearing the browser cache.

Attempt 2 to get the timestamp of a comment to update

I triggered an automatic comment creation by updating the main issue because that's the kind of comment I was seeing for Comment #1. When I updated the comment, it still didn't change the time stamp.

Next, I'm going to try to reproduce the updated time stamp behavior as a user with different permissions.

git-peon’s picture

Testing the behavior of the comment date as a different user.

This was originally posted by git-peon on December 8, 2013 at 4:44pm new

eliza411’s picture

When someone with normal user permissions updates a comment, then the time stamp IS changed.

Sure enough, when someone with elevated privileges (I don't know exactly which ones yet) updates a comment, the time stamp is NOT changed.

That explains the random appearance of "New" flags and why it's not as obvious.

hass’s picture

#4 has 9th december now... Maybe you have seen a caching delay that goes away after a few seconds... And than show the updated date?

tvn’s picture

Title: Comments intermittent marked as "New" » Comments marked as "New" when edited
Issue summary: View changes
Issue tags: +Drupal.org 7.1

Thanks for investigating, eliza411. Updated the summary per your last comment and added tag.

dokumori’s picture

Assigned: Unassigned » dokumori
tvn’s picture

dokumori’s picture

Status: Active » Closed (duplicate)

This is reported as a bug in the core #1374090: Editing a comment still changes creation date. Fixed for D8 and needs porting to D7