It appears that editing a comment resets the timestamp back to 0

I can reproduce the bug when editing the comment as the uid=1 account, as well as the comment owner (non-privileged). The date shows up as correct in the preview, but saves into the database incorrectly (as 0)

Seems to be another case of "it wasn't in the form," so an unset value starts getting around.

The culprit seems to be this line:

        db_query("UPDATE {comments} SET status = '%s', timestamp = %d, subject = '%s', comment = '%s', format = '%s', uid = %d, name = '%s' WHERE cid = %d", $edit['status'], $edit['timestamp'], $edit['subject'], $edit['comment'], $edit['format'], $edit['uid'], $edit['name'], $edit['cid']);

In this case, I'm guessing that !issset($edit['timestamp']) holds true.

Out of all the $edit indices referred to in the update statement, 'status', 'timestamp', 'format' and 'name' aren't set by default.

Patch attached. This seems like a reasonable way to deal with the issue.

Reopening. See http://drupal.org/node/35726#comment-56652 for reasoning.

since been rolled into the patch 35726_1.patch on http://drupal.org/node/35726

and since re-split into a separate issue.

http://drupal.org/node/40762