function _abuse_set_status($type, $oid, $status) {
...
db_query("UPDATE {node} SET changed=%d WHERE nid=%d", time(), $nid);

So far as I can tell, comment.module does not molest the node's "changed" timestamp when a comment is added or removed, so why does abuse.module do so?

The VERY unwanted side effect is that removing an abusive post causes a node to bubble to the top of every node View that sorts by "changed."

Comments

locomo’s picture

locomo commented

subscribe

btmash’s picture

btmash commented

I'll definetly take a look into it. I remember there was a reason I did it from a long time ago though it may no longer be relevant.

On a secondary note, the issue could have been brought up in a nicer way. The 'molesting' was not intentional by any means.

yelvington’s picture

yelvington commented

Well, I didn't mean "molest" as in a Jethro Tull song. :-)

We've been using this module for awhile, but our recent deployment on chronicle.augusta.com is our first experience with the D6 version in a very high-volume setting. We're getting a post about every 120 seconds on average during the day, and the site has a history of (unfortunately) allowing some unacceptable behavior, so there are quite a few abuse reports.

We may wind up generating some patches to implement features being requested by the moderation team, if you're open to that.