Hide Quickreply if Thread Older Than XX Days
 

Hi all,
I've got a request which I think is really useful for other board admins as well. Do you use the quickreply for (all) usergroups without the 'Click to active quickreply option'? Don't you just hate it when an ignorant user bumps a thread which is over 6 months / a year old (or even older)? Then you probably like this modification request.

The current solutions around seem to vary from just close threads after XX days or move older threads to an archive forum. Both of these solutions are not the solutions I want for my board. One of the biggest tech forums in Holland I visit has a very nice option to hide their quickreply after two weeks. They use React forumsoftware instead of vB, but the same functionality could be ported to vB by a skilled coder. I just don't know how to do this myself, hence this request :D

I've posted a screenshot to better explain my request. In this screenshot taken today you see the post date is Friday, 29th April 2005. This post is one month old compared to this post. Because if this, the quickreply is hidden in this thread, 'cos they have it configured to hide the quickreply box after a thread is two weeks old. They just print a warning 'This topic is more than two weeks old, as such the quickreply is hidden'. Users are still able to post to the thread by clicking the 'Post reply' button, but they have been warned about the older post date (and might even check how old the thread actually is).

What I'd like to see is an extension of the current quickreply options in AdminCP, preferably something like: 'Hide Quickreply in Threads Over XXX Days Old'

So .. can this be done in vB and who's up for the challenge?

thanks,
- djr

This is really easy to achieve, if you don't rely on having an ACP option to do so:

In Template SHOWTHREAD replace
with
Replace X with the number of days you like.

Thanks! Wow! That's a really easy solution actually. Minor drawback is that I have a JS error on the page if the quickreply is hidden because of the following function:
Can that be fixed?

Hmm, I don't use QR so ... :)

But try this:

Instead of

use

?

Sheer brilliance! Danke schön! (thnx alot)

You're wlecome :)