vBCron and Pruning

[allan grossman]

Thank you, Kirby - that's exactly what I needed.

edit: I also think if they incorporate this into vB 3.1 they should slip Kirby a couple hundred bucks for his trouble

[allan grossman]

Originally Posted by Limitter

Modyfication by Pogo

http://www.vbulletin-germany.com/for...&threadid=9253

Ich spreche kein Deutch

What does the mod do?

[Indy]

KirbyDE - Many Thanks!!

Haven't had a chance to apply your hack yet since I've been in the process of moving to a new server and all of the associated stuff that goes along with it.

I plan on doing so though!

Thanks again!
Indy

[RCK]

Yeah thanks for your help KirbyDE

[JoeWho]

Hi,

Will this work on 3.5.0.r3

I would like to use this if it would work?

JoeWho

[EricR]

Originally Posted by JoeWho

Hi,

Will this work on 3.5.0.r3

I would like to use this if it would work?

JoeWho

This does not work with 3.5+, but thankfully Andreas released a plugin which makes it oh-so-simple. For those of use who already had this on 3.0, here's the steps to complete your upgrade to 3.5+.

1. Grab the 3.5 plugin from Andreas's post here and install it. Overwrite can be left at the default "no".
2. If you made any custom changes to the prune.php file you'll need to make the same changes to the plugin. To do so, open the Plugin Manager and edit the plugin "Auto-Prune Threads". This is the new location for the code that was previously in prune.php. For example, to preserve Stickies (make them immune to auto-prune), change the following:
   Find this (appears only once)
   

   sticky IN (0,1)

   and change it to this
   

   sticky != 1

3. Delete your /includes/prune.php file, it is no longer needed.
4. Delete your "Prune" task (which used to call the prune.php file) from the Scheduled Task Manager, it is no longer needed.

For 3.5, auto-prune is part of the hourly cleanup #1 in case you ever want to run it manually.

Many many thanks to Andreas for writing this AND helping me thru the upgrade steps