I understand that scenario completely, which is the reason I removed the ability to edit without marking it as edited. (So whenever someone edits it always says, "Edited by . . .")
Don't think of this as arguing
I'm just trying to understand it a little better. Classic had a feature/hack that stored a copy of every post that was edited or deleted? Having never run classic this may be a dumb question, but it stored them where? Like in a forum that wasn't visible?
What I don't understand is this: the "delete" section of ubbt basically runs a mysql query to delete the row from the posts table, right? So if you changed this to not really delete, but copy it to a trashbin forum or something similar, how would you ever truly delete something other than manually? Or would it be set up like "delete" really executes a move of the post to the trashbin, and then "really delete" would actually remove the row from the mysql table.
Would it work to just remove the ability to delete from anyone other than an admin? Maybe have the button "delete" linked to something other than delete.php, where it would really just copy it to a trashbin. Then if an admin wanted to actually delete the post, they could go into the admin panel and use "expire threads".
Maybe I should just go back to wrapping presents.
