topicKill - antibump of topic

[Coders Shack]

value. . . . . . . . Brought to you by
https://vborg.vbsupport.ru/
. . . http://www.Scriptasy.com

value
Installation Time: < 1 mins
Product: 1
File: 1
VB Version: 3.6.X


v1.01
fixed threads actually getting bumped when killed lol... Description: value
Gives you another option rather than deleting or closing you can kill the topic. Which will leave the topic there and open, but when someone responds to it, it will not bump the topic. So basically it just falls down the list.

Installation Instructions: value
Install Product
Upload thread_killed.gif to forums/images/statusiconsvalueIf you like then [Mark As Installed (https://vborg.vbsupport.ru/vborg_miscactions.php?do=installhack&threadid=150341)]
value

[Coders Shack]

also this is a edit free mod :D

[tcs]

Now this is the best idea and hack ever...

[Coders Shack]

im pretty sure i just fixed it, reinstall the product.

[Hornstar]

cool, looks like this may come in handy. nice work.

[shadowevil]

Nice work. *Installed*

[projectego]

Awesome! Great idea, CS! :D

[Cybertims]

doesnt work for me, a reply still bumps the thread to the top.

[deezelpope]

Yeah, same here.:( Bummer.

[Stoebi]

Hi

Really good idea. :)

I have installed a new unpatched 3.6.7PL1 vBulletin for testing this hack. I can't get this hack to work. I can kill the topic, but if any user answers, the topic get bumped to the top.


A question I have:
What happens if you do a counter update ( Rebuild Thread Information or Rebuild Forum Information )?


Regards,

Stoebi

[cheat-master30]

Does not seem to work for me either. Pity, because this is a modification that really, really needs to be around and working for many forums, simply because typical moron internet culture lets unintelligent spam get popular.

[deezelpope]

I agree! This is an extremely useful and necessary modification! Really helps for "cleaning house!":)

@ Stoebi: Have you tried that? The rebuilding, I mean.

[Coders Shack]

v1.01 - fixed the error that was letting topics still get bumped...

(lol didn't know that you couldn't use vbulletin settings in the postdata_postsave or the threaddata_start hooks)

[NFLfbJunkie]

Very nice and useful hack.

[Coders Shack]

Hi

Really good idea. :)

I have installed a new unpatched 3.6.7PL1 vBulletin for testing this hack. I can't get this hack to work. I can kill the topic, but if any user answers, the topic get bumped to the top.


A question I have:
What happens if you do a counter update ( Rebuild Thread Information or Rebuild Forum Information )?


Regards,

Stoebi
should work fine, all this does is keep the lastpost time before the thread was killed.

[deezelpope]

MUCH better!!:) Thank you, Coders Shack!!:up:

[Stoebi]

should work fine, all this does is keep the lastpost time before the thread was killed.
Hi

Thank you for the update, this update works fine. :)

If you are going to do a Rebuild Thread Information, the toptic goes to the top, if the last poster is the actual one of this topic, and all existing threads.

Another little bug:
The FORUMHOME displays this thread as actual if the poster answered to this topic, but the topic was killed before.


Regards, Stoebi

[sybakaos]

Could you make it a per section option (kill an entire section)? That would be a huge advtange on boards with daily announcements (news, daily image sets etc). Thay way newest threads stay on top!

[deezelpope]

<i>I did it that way using the moderator column.</i>

[sybakaos]

I did it that way using the moderator column.
Yes, but won't you have to edit each new thread and set it to 'kill"?

[Coders Shack]

Hi

Thank you for the update, this update works fine. :)

If you are going to do a Rebuild Thread Information, the toptic goes to the top, if the last poster is the actual one of this topic, and all existing threads.


Regards, Stoebi
Hmm, yea im not sure how i would fix that.

Could you make it a per section option (kill an entire section)? That would be a huge advtange on boards with daily announcements (news, daily image sets etc). Thay way newest threads stay on top!

you talking about the whole forum?

[FreshFroot]

very interesting! good stuff

[sybakaos]

Hmm, yea im not sure how i would fix that.



you talking about the whole forum?
No, just a subforum. But forumwide wouldn't be a bad idea either ;).

[Stoebi]

Hmm, yea im not sure how i would fix that.
Okay, IMHO it is not very important to fix this, because I do a rebuild after a vbulletin update only.

you talking about the whole forum?
Yes, in FORUMHOME where you see all last actual threads per forum. IMHO a killed topic should not display on FORUMHOME, if a poster answered to a killed topic.

Regards, Stoebi

[Coders Shack]

Okay, IMHO it is not very important to fix this, because I do a rebuild after a vbulletin update only.


Yes, in FORUMHOME where you see all last actual threads per forum. IMHO a killed topic should not display on FORUMHOME, if a poster answered to a killed topic.

Regards, Stoebi
oh... yea thats an easy fix.

when i have a few ill fix it.

No, just a subforum. But forumwide wouldn't be a bad idea either ;).

subforum is still a forum, it has a forumid.

[alessai]

testing it and also make it in another lang if it works.....

[cheat-master30]

Thanks for the update, as this seems to finally work now.

[alessai]

*Installed*
by the way i translated it, and i hope you dont mind (DiDNT DELETE ANY THING only change the lang)

[Coders Shack]

*Installed*
by the way i translated it, and i hope you dont mind (DiDNT DELETE ANY THING only change the lang)
as with all my work you are free to change and distribute it only in the release thread.

[cheat-master30]

I thought this would have been an option for a user, like when a user posts, he/she can choose whether or not that post bumps the thread or not.

That's what a member at my forum asked when I tested this out and explained why the topic would not be bumped up the topic list. And I think you should try and make that idea, the idea of giving users the choice to allow their post to count or not count in bumping the topic they're posting in. It would be great for those to then reply to topics they don't agree with and not end up raising the topic.

[popowich]

# Upload thread_killed.gif to forums/images/statusicons

Where is the GIF?

I don't see it as a download in this thread.

-Raymond

[popowich]

Nevermind, just noticed that it was part of the screen shots.

-Raymond

[RMS-Chef]

Thanks for the hack.
I think a useful addition/addon/option would be to have a cron/scheduled task auto-kill based on either date of post or last reply after "X" days. Meaning lets say that a thread that has not had a reply after 30 days would be auto-killed and any further replies would not bump. But before that point would behave like normal. Right now I use an auto close hack that closes threads after 30 days of no replies but this would be better.

Thanks again.

[bitHacker]

Thanks for the hack.
I think a useful addition/addon/option would be to have a cron/scheduled task auto-kill based on either date of post or last reply after "X" days. Meaning lets say that a thread that has not had a reply after 30 days would be auto-killed and any further replies would not bump. But before that point would behave like normal. Right now I use an auto close hack that closes threads after 30 days of no replies but this would be better.

Thanks again.

Me say Thanks Too...

I do this the same way... auto close after 30 days... auto kill will be better...
Also, if it would be possible to make the thread become moderated after X days.... so only if mod approve the reply it will bump the thread, othewise mod makes it a kill thread...

great idea

[Coders Shack]

wouldn't that be a bit hard on your mods?

like every response on a past thread the mod gets a message to approve.

currently the only thing i have in mind is to make a whole forum/sub-forum killed. (everything else seems like too much work lol)

[alessai]

huge problem (will with me)

i killed a thred and there are about 17 post in the thred.....
after 10 post there is a new page :confused: the problem is i cant see the second page....

[Coders Shack]

huge problem (will with me)

i killed a thred and there are about 17 post in the thred.....
after 10 post there is a new page :confused: the problem is i cant see the second page....
im pretty sure this doesnt have to do with this mod.

[alessai]

im pretty sure this doesnt have to do with this mod.

i tried it in other forum (appserv) its shows me there is 3 pages in the forumdisplay but when i go inside it there are only 2 pages!!!!!

[foundnyc]

thanks for the great mod.

one thing i noticed is that anytime anyone posts to a killed thread, the thread still shows up on the forums homepage as the most recent thread. any chance this could be resolved in your next update?

thanks again.

[AWJunkies]

Very interested in mod and its development keep it up!

[coffee]

Installed here.

What to change to use thread[dateline] instead of thread[lastpost] ?

[Gigavol]

Great mod. I found that this version of it caused an error in my quick replies and posts, though. Specifically the hook variable in class_dm_threadpost begins with an extra }. I guess it is a conflict with some other things I have installed: passiveVid, MiserableUser, IPInfo, Members Who Have Visited, and randomImages (passiveVid being the most recent).

After posting, here is the error displayed briefly by vB:
Parse error: syntax error, unexpected '}' in /home/abc/public_html/forums/includes/class_dm_threadpost.php(829) : eval()'d code on line 1
The line dealt with $hoof, so I printed it out right before the error and this is what was printed:
}if ($this->info['thread']['killed'] == TRUE) { $this->post_save_each_post($doquery); $thread->set('lastpost', $this->info['thread']['lastpost']); $thread->save();

I hope this is of some value.

Cheers!

[YLP1]

AWESOME mod!!!

[dknelson]

Has anybody tried this on 3.7? I'm getting ready to upgrade and am trying to figure out which of my installed mods will work.

[KEKforce]

Works perfectly with 3.7.x (3.7.2)

[MDK-Indy]

Works perfectly with 3.7.x (3.7.2)

No, work not perfektly...

It Works, but with many errors...

[inciarco]

Coders Shack, is it possible for you to provide us the Changes on Plugins "topicKill - Show Killed Icon" and "topicKill - Template Edits" that can Work on vB 3.7.3? :confused:

I've seen that the Mod Works but Don't Display the Icon and also Don't Display the Changes threadbit "Las Post by", both of this Changes made by the 2 Mentioned Plugins. (The Topic Gets Killed, doesn't Update the Date of the Thread, but those 2 Small Details that Show the Thread as Killed don't Display). (In my Tests the rest of the Features work Well on vB 3.7.3).

I'd appreciate that a Lot, I like a lot this Mod and would like to Continue Using it on vB 3.7.3.

My Best Regards.

:)

[DJA]

I love this product. Thanks.

Is there a way to make it 'stealth'? It would be great if I could kill a thread, but no indication would appear; no one would know. The post would just silently slip down the queue.

So, I'd need to change the code so that there would be no 'kill' icon and no 'last post'. It would appear to look like any other thread.

Is that possible?

[inciarco]

I can see on vB 3.7.3 that somehow the Field "Kill" is created on the "thread" table, and that the Mod allows the User to Stablish the Status Killed (1) or Revived (0) for that Field for each Thread.

But somehow in the Plugin "topicKill - Show Killed Icon" that corresponds to a "threadbit_process", the Code

// show killed folder?
if (($thread['killed']) && ($vbulletin->options['topicKill_enabled'])) {
$thread['statusicon'] = '_killed';
}

don't detects the field $thread['killed'], not even by using it directly on the threadbit Template; what is wrong in that sentence that vB 3.7.3 don't read the Field "Killed" of the Table "thread" for the respective Thread? :confused:

I think the logic of the Sentence is right but it beats me why vB373 don't read the value of the field "killed" from the table "thread".

Perhaps this same thing is happening on the Plugin "topicKill - Template Edits" on the Code lines,

$vbulletin->templatecache['threadbit'] = preg_replace('#\$thread\[lastpostdate\] \"\.\(\(\!\$show\[\'detailedtime\'\]\) \? \(\"<span class=\\\"time\\\">\$thread\[lastposttime\]</span>\"\) : \(\"\"\)\)\.\"<br />#i', '".(($thread[killed] == FALSE) ? ("$thread[lastpostdate] " . ((!$show[\'detailedtime\']) ? ("<span class=\"time\">$thread[lastposttime]</span>") : ("")) . "<br />") : ("last post<br />"))."', $vbulletin->templatecache['threadbit']);
}

somehow seems like the Code isn't detecting the Condition "$thread[killed] == FALSE" and always assigns it a False Value (0) or perhaps Nothing, so it always displays the default Code without the Changes when Killed = 1 (TRUE). :confused:

I hope Coders Shack or other Forumer with Experience can give us the Solution. :o

:)

[ravenscape]

I'm interested in a hack/plug-in with this functionality. Does this actually work with 3.7.x? Is there another hack/plug-in with this functionality that works with 3.7?

[inciarco]

I'm interested in a hack/plug-in with this functionality. Does this actually work with 3.7.x? Is there another hack/plug-in with this functionality that works with 3.7?

The Mod on vB373, but has the Bug that don't Change on the Thread's List of ForumDisplay (Threadbit Template) the Icon of the Thread Changed for the Killed Icon of the Mod (https://vborg.vbsupport.ru/external/2011/07/109.jpg).

I've tried by myself to do that Change in various ways (my knowledge is limited) and Haven't been able to do it.

Coders Shack, could you please point us into a Solution to be able to see the Killed Thread's Icon on the Threadbits? :confused:

Everything Else Works Fine, that's the Only Detail, and is Important to see which Thread's are Killed and Revive them if wanted to, otherwise it'd be very Hard to Remember and Locate those Killed Threads. We Appreciate Your Help Coders Shack. ;)

My Best Regards.

:)

[fishmaster]

Any other similar mods to this one out there?

[Mont]

I installed it and it works great for my classifieds ad section to keep users from bumping posts only to get them up top. Thanks for a great mod!

[inciarco]

The Mod on vB373, but has the Bug that don't Change on the Thread's List of ForumDisplay (Threadbit Template) the Icon of the Thread Changed for the Killed Icon of the Mod (https://vborg.vbsupport.ru/attachment.php?attachmentid=65912&stc=1&d=1182482222).

I've tried by myself to do that Change in various ways (my knowledge is limited) and Haven't been able to do it.

Coders Shack, could you please point us into a Solution to be able to see the Killed Thread's Icon on the Threadbits? :confused:

Everything Else Works Fine, that's the Only Detail, and is Important to see which Thread's are Killed and Revive them if wanted to, otherwise it'd be very Hard to Remember and Locate those Killed Threads. We Appreciate Your Help Coders Shack. ;)

My Best Regards.

:)

For the Icon to Display on threadbit at vB38x, is necessary to Change the Following Plugin "topicKill - Show Killed Icon" to:

// show killed folder?

$var_killed = $vbulletin->db->query_read("
SELECT killed
FROM " . TABLE_PREFIX . "thread
WHERE threadid = " . intval($thread['threadid']) . "
");
$var_killed = $vbulletin->db->fetch_array($var_killed);
$var_killed = $var_killed['killed'];

if ($var_killed == 1 AND $vbulletin->options['topicKill_enabled']) {
$thread['statusicon'] = '_killed';
}

For some reason the threadbit_process don't Detect the $thread['killed'] so is necessary to Search those Values with the $vbulletin->db->query_read and the $vbulletin->db->fetch_array and the $var_killed['killed'].

Perhaps You Know what to do for the the $thread['killed'] be Used at the threadbit_process Hook Location.

My Best Regards.

:)