|
|
« Reply #735 on: August 28, 2011, 01:09:12 PM » |
|
Well, I think generally nercroposters, double posters, etc are usually new to the forum and/or forums in general. Yeah, they're still to blame for not reading the rules, but you can't expect everyone to be familiar with how a forum works.
If they put themelves in danger of necroposting, they get a big red warning saying : Warning: this topic has not been posted in for at least 21 days. Unless you're sure you want to reply, please consider starting a new topic. I think it's pretty clear and straightforward. Honestly, there's nothing more we can do for them, unless someone feels very confident and want to code a little SMF mod for us that locks topics after a certain time, while of course leaving the permission to unlock it for the author.
|
|
|
Logged
|
Round and round the signature goes ~ ~ where it stops, nobody knows.
|
|
|
|
|
|
« Reply #736 on: August 28, 2011, 01:16:30 PM » |
|
If they put themelves in danger of necroposting, they get a big red warning Not if they use Quick Reply. We'd have to turn off QR in order to use that justification.
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #737 on: August 29, 2011, 01:30:51 AM » |
|
Isn't there a way a thread can automatically get locked after 3 weeks have passed?
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #738 on: August 29, 2011, 01:51:06 AM » |
|
Isn't there a way a thread can automatically get locked after 3 weeks have passed?
Yes there is.
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #739 on: August 29, 2011, 01:58:45 AM » |
|
Sounds like a good idea to test on kcmm-e to me
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #740 on: August 29, 2011, 02:39:04 AM » |
|
Once again, that mod you guys are talking about doesn't seem to offer any options to let the author of the thread unlock his own topic. So far, you could only unlock your topic if you were the one to lock it. Sooo ... I'm not sure how this will work, or how compatibility issues will go. But yeah sure, give it a try on KCMM-E. But we will not install a mod that will force hackers out of their own hacking threads if they don't update in 3 weeks.
|
|
|
Logged
|
Round and round the signature goes ~ ~ where it stops, nobody knows.
|
|
|
|
|
|
« Reply #741 on: August 29, 2011, 02:55:03 AM » |
|
Once again, that mod you guys are talking about doesn't seem to offer any options to let the author of the thread unlock his own topic. So far, you could only unlock your topic if you were the one to lock it. Sooo ... I'm not sure how this will work, or how compatibility issues will go. But yeah sure, give it a try on KCMM-E. But we will not install a mod that will force hackers out of their own hacking threads if they don't update in 3 weeks. I can understand that yeah, it wouldn't be useful if the creator can't even unlock it.. I hope there's a way to fix that by testing it on kcmm-e
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #742 on: August 29, 2011, 03:24:26 AM » |
|
Once again, that mod you guys are talking about doesn't seem to offer any options to let the author of the thread unlock his own topic. So far, you could only unlock your topic if you were the one to lock it. Sooo ... I'm not sure how this will work, or how compatibility issues will go. But yeah sure, give it a try on KCMM-E. But we will not install a mod that will force hackers out of their own hacking threads if they don't update in 3 weeks. According to that plug in, you can speccify what boards have the ability to auto-lock or not, and even how long it takes before a long will happen. I'll try it out on KcMm-E if the mods really are interested in such a system.
edit: Wait never mind. It's for smf 2.0+
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #743 on: August 29, 2011, 03:29:36 AM » |
|
According to that plug in, you can speccify what boards have the ability to auto-lock or not, and even how long it takes before a long will happen. I'll try it out on KcMm-E if the mods really are interested in such a system.
edit: Wait never mind. It's for smf 2.0+
Crud and KCMM runs on 1.1.11 :\
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #744 on: August 29, 2011, 03:59:47 AM » |
|
According to that plug in, you can speccify what boards have the ability to auto-lock or not, and even how long it takes before a long will happen. I'll try it out on KcMm-E if the mods really are interested in such a system. Problem is : most necroposts happen in boards where projects CAN get revived (like the PSA boards) so yeah, it's a bit meh ... edit: Wait never mind. It's for smf 2.0+ That's why I mentionned compatibility issues ... >w>
|
|
|
Logged
|
Round and round the signature goes ~ ~ where it stops, nobody knows.
|
|
|
|
|
|
« Reply #745 on: August 29, 2011, 04:02:12 AM » |
|
That's why I mentionned compatibility issues ... >w> Maybe a stupid question but why isn't KCMM running on 2.0 by now?
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #746 on: August 29, 2011, 04:37:04 AM » |
|
2.0+ has lots of issues from what I've read. 1.1.11+ has been the most stable SMF by far. Why SMF still update it along with 2.0+
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #747 on: August 29, 2011, 05:02:18 AM » |
|
Maybe a stupid question but why isn't KCMM running on 2.0 by now?
What Kit said. Also, I guess we could update it to better 1.1.XX versions, but do remember that we're kinda short on Tech staff. Picano is in control, but mostly busy, and other admins either have limited or no knowledge in coding and broken-stuff-fixing. So far, what we need to do is update our database to fix alot of glitches (like for our reports, and possibly our pagination errors), and find a way to automatize some of the awards.
|
|
« Last Edit: August 29, 2011, 05:03:21 AM by Miacis Ballard »
|
Logged
|
Round and round the signature goes ~ ~ where it stops, nobody knows.
|
|
|
|
|
|
« Reply #748 on: August 29, 2011, 05:53:45 AM » |
|
I could be kind of a techy~techy for ya'll but honestly, I don't know much about php and it's system. using KcMm-E helps a ton in most cases though so we could dink with it while having this forum untouched. Also, Y U NO MSN ME?!
|
|
|
Logged
|
|
|
|
|
|
|
« Reply #749 on: August 29, 2011, 06:46:38 AM » |
|
Do the logs that smf generates in the db have any other purpose than to just tell what errors occurred when and what activity goes on in the vault? Stripping some of those could save space and unclog the db, at least a little bit.
I'm pretty good with php and sql. I wrote two [simple] websites using them (and slightly customized a smf 2.0 on the second site). Only if you want me back, though...
|
|
|
Logged
|
|
|
|
|
|