September 25th, 2012, 11:26 AM
Closing "finished" threads
I've seen that threads are immediately closed when the original poster claims that his question has been answered. I don't find that a good idea.
Many users tend to claim victory far too early. The code itself may somehow "work", but there are still hidden bugs, security issues, better solutions or whatever. This thread is a good example: The user has "fixed" the error message, but his code is now open to SQL injections.
If the thread is already closed, there's no chance of notifying him (without sending private messages around). So it would be great if you'd leave the threads open at least for a while so that we can still reply.
September 25th, 2012, 12:14 PM
I think in most cases it's the original poster of the thread that closes it, as far as I know moderators do not normally close threads when the original poster claims to have found an answer, even in cases where the answer is correct.
September 25th, 2012, 01:38 PM
Oh, OK. I didn't know you can do that as a normal user.
In this case I suggest removing this option. There's a reason why most forums only let moderators close threads.
September 25th, 2012, 01:43 PM
I agree. There have been a few threads I have re-opened for such reason when a user hastily closes it. I don't know of any moderators that close threads just because of an answer. We do close them when they become targets for inanity or when they are often bounced to the top by spambots after years of inactivity.
Originally Posted by Jacques1
With the administrators more active these days I'm guessing someone in charge will see this and take the suggestion for consideration. We moderators ourselves cannot change this.
“Today you are You, that is truer than true. There is no one alive who is Youer than You.” - Dr. Seuss
October 23rd, 2012, 01:12 PM
Also, I agree. Sometimes as said before the provided solution is working but not failproof nor foolproof. And can become also buggy.
Originally Posted by medialint