Prevent Doubleposting

When a User posts into a thread where he already has the lastpost, no new post will be added. The lastpost of him will be edited and the new text is put after his first message.
This will be done until the old post is older than 24 hours (you can change this timespan yourself)

Nothing more to say about that, it's the quite same as my vb3.0 version.

This Mod should run with 3.6 as well


** Please make sure you ENABLE this product after you install it - it is disabled by default. **

For vb 3.8 there are two alternative updates ;

https://vborg.vbsupport.ru/showthread.php?t=203705
https://vborg.vbsupport.ru/showthread.php?t=204177

[Smoothie]

Originally Posted by Err0r1

Is this working for anyone on 3.6.4?

I've installed, but nothing happens upon double posting.

Maybe it's because I've installed beebi's mod: https://vborg.vbsupport.ru/showpost....&postcount=618

It's working for me.

[TrIn@dOr]

Thanks, nice.

Where can i find the sentence, "Doublepost will be merged" ?, i need to translate it!

[Wild-Wing]

ok im confused whats with post var where theres no sql

[MeMySelfNi]

I was looking all over the place for this

*installed*

[Nik_s3]

Sorry... I'm using 3.6.4 versione. Is there someone that could explain to me what is the exact procedure to install this modification?

Thank you

[Nik_s3]

Up....

[SCRIPT3R]

Originally Posted by Nik_s3

Sorry... I'm using 3.6.4 versione. Is there someone that could explain to me what is the exact procedure to install this modification?

Thank you

Originally Posted by Nik_s3

Up....

Originally Posted by beebi

to get it work fine with 3.6.x
find

PHP Code:

    // we are here, so we may have a doublepost -> do more exact checkings
    $doublepost = $vbulletin->db->query_first("
        SELECT post.*
        FROM " . TABLE_PREFIX . "post AS post
        LEFT JOIN " . TABLE_PREFIX . "deletionlog AS deletionlog ON(deletionlog.primaryid = post.postid AND type = 'post')
        WHERE threadid = $threadinfo[threadid]
            AND dateline > " . (TIMENOW - $vbulletin->options['xen_dp_timespan'] * 60) . "
            AND visible = 1 AND deletionlog.primaryid IS NULL
            AND postid <> $post[postid]
        ORDER BY dateline DESC
        LIMIT 1
    "); 


replace it with

PHP Code:

        // we are here, so we may have a doublepost -> do more exact checkings
        $doublepost = $vbulletin->db->query_first("
                SELECT post.*
                FROM " . TABLE_PREFIX . "post AS post
                LEFT JOIN " . TABLE_PREFIX . "deletionlog AS deletionlog ON(deletionlog.primaryid = post.postid AND type = 'post')
                WHERE threadid = $threadinfo[threadid]
                        AND post.dateline > " . (TIMENOW - $vbulletin->options['dp_timespan'] * 60) . "
                        AND post.visible = 1 AND deletionlog.primaryid IS NULL
                        AND post.postid <> $post[postid]
                ORDER BY post.dateline DESC
        "); 


there ya go.

[Bubble #5]

Originally Posted by Xenon

PHP Code:

AND !in_array($vbulletin->userinfo['usergroupid'], array(5,6,7)) 


We added this to the 'conditionals' section of the hack, but we're getting a bunch of parsing errors and admins are still getting automerged

Parse error: syntax error, unexpected T_LOGICAL_AND in /home/imnotimk/public_html/forum/includes/functions_newpost.php(524) : eval()'d code(9) : eval()'d code on line 1

Is this a 3.6.4 problem, or did we add the wrong code to the conditionals section?

[Xenon]

remove the AND in front

that was in an old version iirc, regarding that the post is on page one ^^

[Bubble #5]

Thank you Xenon, I fully appreciate your help

One other quick question while I have your attention. At the beginning of the thread there is a post that makes this hack 3.6.x compatible. It basically just changed 'AND dateline' to 'AND post.dateline'. However now I see additional code being posted above in beebi post. In your opinion what is the advantage (if any) to using beebis code VS. just adding "AND post.dateline"?