9 replies to this topic

[.oisyn]

Let's start off with an example: http://www.devmaster...ead.php?t=12007

Scenario: a user uses the search, finds an old thread and starts reading, sees a post that demands his reaction, forgets he was reading an old thread and thus kicks the thread into oblivion. The thread is now on top of the recent posts list and other people start to reply, unaware of the fact that the thread was accidentally kicked and that most posts are old and outdated.

A dutch IT-related forum I frequently visit has the feature that it hides the quickreply box under a thread when a thread is older than a certain threshold. Replying is still possible, but it is just that quick reminder that the thread is old that prevents people from accidentally kicking it.

Perhaps devmaster should do that too, along with a javascript alert when clicking the quote button underneath the post. Just a reminder, such as "Warning - this is an old post. Are you sure you want to reply? (Yes/No)".

It's not that big of a problem really, but the fix is technically very simple and can avoid a lot of confusion

[monjardin]

I'll second that idea if the staff has time to implement it. ;)

[Dia]

That's a good idea. It's now implemented

[onyxthedog]

Nice!

[.oisyn]

Great . But I think you should also show the message when you press the button on the right side of a reply. And perhaps you should hide the button, as that doesn't really do anything anymore without a visible quickreply box

[Prey]

Nice addition :)

[Dia]

Good point, .oisyn
I've added it for those buttons too.

Note that the cut-off time is 15-days, which I think is reasonable.

[.oisyn]

:yes:

[onyxthedog]

15 days after no one has post in it, or 15 days after its making?

[.oisyn]

The former, of course.

However, it only seems to be looking at the last post date of the thread, not the date of the post you are trying to quote.