would it be possible / advantageous to show thread start date next to thread starter name
this would allow members to see that an old thread has been resurrected an choose whether to read or not
Printable View
would it be possible / advantageous to show thread start date next to thread starter name
this would allow members to see that an old thread has been resurrected an choose whether to read or not
did you get crypt-rolled (sucked into a thread more than a year old)?
I've had that happen to me. Sometimes the resurrection is valid... but more often than not, it isn't.
-tg
Changing the templates is usually not as problematic as changing the code but it may require an extra query, I could look deeper into it if needed, but then we still run into the same problem of complicated upgrades to redo the hack.
Perhaps a easier solution would be to close out threads after a certain time period has elapsed (policy period). If there is any additional need to reference the thread, a new thread with a reference link made back to the closed thread would be best.
I support that idea. If a thread hasn't had a post in 45 days (or however long), close it.Quote:
Originally Posted by RobDog888
I was looking at a plugin for this but to modify it to work for our needs will be too much of a resource drain because of the need to update threads that are past the time limit.
I did figure I could write a cron job to process threads on a nightly batch but still may not be low impact enough.
Finally the thrid option, which may not be a good user experience, is to autoclose the thread when they try to reply lol.
Pity, it can't be done for threads that have been resolved.Quote:
Originally Posted by RobDog888
It probably could but usually resolved threads may have additional info to add or stuff. The member wouldnt be able to reopen it. I think we thought about it when the hack was first discussed and decided against closing them.
I did think about just placing a message next to the reply box that could warn the member that the thread is old and would be closed. Then f they try to post a reply we use the postback to update the thread table with a update statement to close the thread. This way its on a per thread per post attempt basis. Least impact I can think of.
Still every modification need to really be eval'd to see if its worth the trouble managing.
Perhaps just the warning would be easiest as its a simple plugin adding a custom template to the replybox template dynamically. Up to the Admins if its worthy or not. Then if the members have enough desire for it maybe we can do it.
So you cant just have the DB run an update query on the Threads table when the date rolls to the next day? What type of database does this forum use? I'm pretty sure MySql supports DB Triggers for this type of thing and it wouldn't require a PHP forum change if done right. At least I don't think anyone would need to get into the forum code at all.
We've discussed the idea of closing older threads automatically and decided against it. Don't see any reason why a thread should be closed just because it's old. That doesn't necessarily mean it's no longer relevant.
Hey,
What about entries in the CodeBank's? Would/should they also get included in this auto-closure discussion? I would have thought not, that way, any new person with a question can legitimately ask it in an older thread.
Gary
How about just the warning part on old threads to help members realize its old and probably shoudnt be bumped?
Hey,
What sort of warning are we talking about? It would have to be something pretty obvious to prevent it from being bumped.
Gary
Just thinking of using a plugin to inject an additional template to the quick reply and advanced reply to add text stating its an old thread etc.
But guess maybe we could take this to the php forum perhaps as its getting kinda off topic
Edit: Look what I found. Like this! :D
That looks good, though 15 days is a little short I think 45 days or more (like 60) would be alright. Some people like myself don't get back to a thread I make for a few weeksQuote:
Originally Posted by RobDog888
Hey,
That looks promising!! But I agree with JuggaloBrotha, perhaps 15 days is a bit short.
Gary
Its just an example but at least spammers cant bump threads unless they check the box. Should break most webbots at least for a little while.
3 plugins, a couple of phrases and template.
When can we get it :)
It needs to be evaluated and approved by the developer admins and then if approved we may have a timeframe to estimate.
That's brilliant, Rob! I think we should install it. It's no code modifications is it?
That plug-in seems like a great addition to the forum.
1) I like the idea of autoclosing the thread after a specific period of time. This is what happens in most of the forums.
2) It would be a bad idea to autoclose Resolved threads, unless they have been inactive for a specific time. What if the user wants to 'UnResolve' it?
3) The first point if not difficult to implement will directly help users not getting 'sucked' into old threads as tg puts it :D (Well, even I have been a part of one or two)
Thanks PG. :) There is no code modifications at all. Complete plug-in and injecting the templates into the template cache. So its all done on the fly. this will need to be evaluated, tested and if accepted, scheduled for implementation. Any additional plugin is always a risk and needs to be thouroughly tested.Quote:
Originally Posted by penagate
@Sid, Autoclosing threads is just too much of a resource and risk. We have toyed around with this idea before and decided against it.