New Posting Features - Doublepost Prevention

As of 24 Nov 2017 this modification has been withdrawn.

This is an updated version of the popular modification, previously released by Xenon. It is released with his kind permission.

Basically, if member posts in a thread where they were the previous last poster, then if the conditions are met, their new post will be auto-merged into the previous post instead of creating a new "double" post.

A number of options are provided ;

Time Limit - if more than xxx minutes have passed since the last post, no merge is done.

Timestamp Spacer - if enabled, a timestamped spacer is added between the old post text and the new post text.

Post Timestamp Update - if enabled the newly merged post will have its post time updated to the new time, otherwise it retains the time of the original post.

Spacer Colour - allows you to set the colour of the spacer between merged posts.

Usergroup exceptions - Allows you to exempt certain usergroups from the doublepost merges.

Forum exceptions - Allows you to exempt certain forums form the doublepost merges.

All settings are located in vBulletin Options > Doublepost Prevention.


To install just unzip the XML and import into vB using the ACP Product Manager.


History:

v3.8.001 : First Release for vB 3.8.
v3.8.002 : Phrased the post separater.
v3.8.003 : Added JS Template - removing need to edit quick reply javascript file.
v3.8.004 : Updated spacer options.
v3.8.005 : Updated timestamp spacer to fix issue with large merge times.

[Paul M]

If the date of the doublepost is different to the date of the original post, then the date will be added to the timestamp. If the date is the same, then only the time is added. All you have done is added the date when its the same as the previous post. Which is not necessary IMO.

[JoomlaCommunity]

This is true but only if you have set the option

Bump Thread
Update the timestamp of a doublepost. to NO,

It will trigger the phrase:

---------- Post added 6 september 2009 at 02:15 ----------

On top the original date and time is shown

We sure would go for that option but, as we tested, then the new post will not appear in the list unread posts. This will only happen if we set the option Update timestamp of a doublepost to YES.

If we choose this option, the phrase will show only the time of the new and the previous post like I posted before. I have tested this with older posts of a different date, there is no date shown in the phrase. Also tested it with a new install on a testforum, same result, no date is shown. Is there an option that I am missing?

------------------------EDIT----------------------

It seems to be a problem with the forum language that is set.
If the forum language is set to original english, the date is shown, our forum is set to Dutch.
Maybe somebody else recognizes this and can tell how to solve this?

----------------------EDIT-2--------------------------

It seems that if there is a locale set the date will not show in the phrase as I described before.
If I leave the locale empty and all date overrides it works like it should.

[phatguy88]

Sorry if this was asked already. When it automerges the doublepost the date it uses is the servertime. I am 7 hours behind. How do I get it to show based on my time settings?

[Paul M]

You dont, there is no timezone facility in the seperator functionality.

[phatguy88]

So I might as well delete this mod then. =/

Is there a similar mod with that feature?

[Paul M]

Your choice. There is no released mod that does it.
I think the only other DP mod does something like "Posted x days, hours, mins ago" rather than the actual date and time.

[TheChaosFactor]

That's awesome. Thank you.

[imported_silkroad]

Hi Paul.

Great mod, BTW.

We are running version 3.8.005 Prevent and plugin DoublePost 2 consistently causes a number of slow MySQL queries from this mod in the mysql-slow.log

We have been tracing a possible database deadlock issue and have been using the mysql-slow.log to look at our slow queries.

Did I miss any discussion about this in the thread?

Any thoughts?

[imported_silkroad]

FYI, Paul... here is an example slow query that we see in the logs:

# Query_time: 7  Lock_time: 0  Rows_sent: 1  Rows_examined: 26769
SELECT t.forumid, t.threadid, t.title, t.replycount, t.lastposter, t.lastpost
FROM thread AS t
LEFT JOIN deletionlog AS deletionlog ON(deletionlog.primaryid = t.threadid AND type = 'thread')
WHERE forumid = 30 AND lastpost > 1021388850 AND visible = 1 AND open <> 10
AND deletionlog.primaryid IS NULL
ORDER BY lastpost 
LIMIT 1;

[Paul M]

That query is not from this modification.