Version: 0.4, by Keloran
Developer Last Online: Jun 2010
Category: New Posting Features -
Version: 3.6.8
Rating:
Released: 10-11-2007
Last Update: 01-07-2008
Installs: 31
DB Changes Uses Plugins
Re-useable Code
No support by the author.
This creates a new thread once a thead has reached a certain size and a user posts a new reply
NOTE
this does alter your thread table, it adds a new row (contnum) and a new index
it adds a new bbcode to your forum, so that the topic continue doesnt open a new window/tab
Install guide
when you install through the "manage products", a new set of options will appear in the vbulletin options->vbulletin options (defualt off)
this allows you to change the following settings:
userid of the post continuer - when a post is auto-closed a post is made that says it is closed, and a new thread is created with a post in it saying where the original is, this is posted auto by the user given (default 1)
reply count - the amount of posts before a thread is closed and split (default 500)
threadsplitter enabled - turn off/on the thread splitter (default off)
dont allow splits in X forums - add new forums by using ,. e.g 4,5 (default blank)
update subscriptions - update the users threadsubscriptions to the new thread if subscribed to the old one before split
unsticky old threads - unsticky the old threads after a continuation is made (default off)
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I got subscription updating to work. Product file is attached. It's been installed on vB 3.6.8 and 3.8.4 without any issues. You will still have to save the bbcode as described in my post above to get that working.
I got subscription updating to work. Product file is attached. It's been installed on vB 3.6.8 and 3.8.4 without any issues. You will still have to save the bbcode as described in my post above to get that working.
Awesome, thank you for your contribution, I will test it later on 3.8.5 :up:
Quick question, if I have 20 posts per page, what is the recommended amount of pages to have before a thread should be split, and does this help with performance? Thanks.
Awesome, thank you for your contribution, I will test it later on 3.8.5 :up:
Quick question, if I have 20 posts per page, what is the recommended amount of pages to have before a thread should be split, and does this help with performance? Thanks.
That will depend on your server specs and configuration. We use this solely for performance reasons and set it at 1000 replies to keep db queries from getting too long. In master-slave replication server configurations we experience replication lag and lost connections with higher reply counts. Performance hit is especially severe if post cache needs to be rebuilt.
Just one question if you don't mind, is there any way I can prevent it from posting the first post of the original thread? Much appreciated, thanks.
The second post of the new thread is the first post of the old thread so I'd try commenting out or removing this code in the plugins. It's found in both plugins.
Code:
//create the second post in the new thread
$newPostNTF = $db->query_write("INSERT INTO " . TABLE_PREFIX . "post (title, threadid, username, userid, dateline, pagetext, visible, parentid, showsignature) VALUES ('" . $db->escape_string($oldPostF['title']) . "', " . $newThreadId . ", '" . $db->escape_string($oldPostF['username']) . "', " . $oldPostF['userid'] . ", " . $newTime . ", '" . $db->escape_string($oldPostF['pagetext']) . "', 1, " . $newPostId . ", 1)");
$newPostNTFId = $db->insert_id();
The second post of the new thread is the first post of the old thread
Really sorry to bug you again. Is there any way we can make 'the second post of the new thread', the last post of the old thread? So when someone makes a post in the original thread, the post is posted, the thread is then closed and split and that last post is then posted again as the 2nd post in the new thread?
Would really appreciate your help on this, Thanks.