≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #671

Bug #671: "last post" info wrong for anonymous comments?

Kind bug
Product wincent.dev
When Created 2008-04-18T06:09:34Z, updated 2008-04-21T16:32:32Z
Status closed
Reporter Greg Hurrell
Tags no tags

Description

Not sure if this is a bug yet as I only just saw it for the first time; will have to monitor it and see if it happens again.

Look at the Synergy forum:

http://wincent.dev/forums/synergy

The "last post" info for the latest topic:

http://wincent.dev/forums/synergy/topics/250

Read as "mikej 4 hours ago"

There was a comment awaiting moderation, posted 4 hours ago, but when I went to moderate it it turned out to be anonymous, not my user mikej.

So I marked it as "ham" and it was made public. The "last post" info did not change, but this is normal (merely marking something as ham/spam doesn't trigger any updates in the database, it just toggles a single column value on one row).

Looking at the topic, mikej was the original poster and has participated in the discussion, but he definitely isn't the last poster.

Looks to me like perhaps the identification of the "last poster" is wrong when the last commenter is both anonymous and awaiting moderation (although it could be either of those attributes rather than both); will investigate further.

Comments

  1. Greg Hurrell 2008-04-18T08:09:17Z

    Definitely seems to be a reproducible issue: just had another anonymous comment queued for moderation and the "last post" info was updated to "mikej 27 minutes ago". So the timestamp gets updated but the appropriate username does not.

  2. Greg Hurrell 2008-04-21T07:53:55Z

    Ok, I believe I've fixed this. Fix will go live with the next deploy, so marking this as CLOSED.

  3. Greg Hurrell 2008-04-21T16:32:32Z

    Just deployed the new code and the "last post" information definitely looks to be correct.

Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets