I checked the thread but from it seems that this feature will not be available in 3.6 so I guess it will take long time to wait for it frm vb.com.
Furthermore I guess that there might be more usefull option for this than vb.com will include in official release.
To me it can be used for common knowleadge base - aka wiki.

Glad to see it has been useful for some peeople. I did this for our own forum, so it's sorta hard coded to what I wanted but I thought it would be nice to share :). It isn't actually that complex so adding the extra features would make it (somewhat) more complex. (There is also a slight problem in that I have somehow killed my local copy of vbulletin that I use for testing changes and haven't got around to figuring out how I broke it :) ).

Anyway, for those who are looking at the XML, there is mainly 2 parts:

The hookpoint: parse_templates

This is basically:

$insert_point = "blah";
$insert_point2 = "blah2";
$new_text = "new text";

Then a few commands do a search and replace on the templates. This is why there is no need to manually update the templates. The problem is that the required insert_point is different from version to version, that's why there is 2 insert_points.

Also, the text required here is the text of the template after some processing, rather than just copy/paste the template from admincp ... so hard to get it to match for different versions. It is also hard to read :).

The check code is
( \$post['numedits'] != 0 ) && ( \$post['editlink'] )

This means that it displays the edit history options as long as there is more than 0 edits and the user is permitted to edit the post.

Any variables that are available to the postbit can be used. I am not sure if usergroup settings are available.

I think that replacing

( \$post['editlink'] )

with

( \$show['inlinemod'] )

in the XML before uploading should make it so only mods can see the controls for viewing older versions. (This assumes that you are using inline mods)

The 2nd hookpoint is
showthread_postbit_create

This is less complex. It is where the post is actually modified so that it looks at the old post. Also, it checks permissions. This is the only part that needs to be updated if you don't mind users seeing the edit history options as long as they can't use the options.

The check is:

( can_moderate($thread['forumid']) || ($post['userid'] == $vbulletin->userinfo['userid'] ) )

The 1st term is the one that allows moderators to view the post history and the second term is for the user themselves.

Changing it to:

( can_moderate($thread['forumid']) )

would mean that only moderators can use the feature.

So, making those 2 chances to the XML (just requires a text editor) should make it so that only mods can see/use the edit history system. I don't have a "scratch" version of 3.5.1 atm, so I can't confirm that.

Btw, have people tried this out on other 3.5.x versions? It would probably be worth a yes/no question for each version. Also, posting the default postbit (and postbit_legacy) for those versions would help if they aren't working.

Getting it to work for the other versions (if they don't work), should just be a matter of adding more $insert_pointx strings.

Also, I haven't actually looked, but is the 3.6.x plugin system compatible with 3.5.x or have they redone everything again ?

Thank you very much for clarifying this, I will check if this will do it.

BTW, I have "post hist mods only.xml" installed on a 3.5.4 forum and it works as you have designed it. If I manage to change it to work only for mods with your info I will owe you one ... :-)

Djamil

Great job, but I was wondering if there was any way to extend the information? (basically, i want to know who did the edit as well as view the history!)

Is this possible?

Lieva please let us know wheter you are interested to continue development of this hack or do you agree to pick this up by somebody else.

I willing to pay for this hack!

Thank you

Can anyone help fix this error :(

I have no idea what it means or how to fix it. It only appears when you go to thread's you've posted in or your pressing edit, it seems :confused:


please please please help

*waited 24 hours as the rules says*

anyone, please? I would really like this hack to work.

anyone *bumps again*

Can you please post the templates edits it would need since the plugin version doesnt work for me as the line it looks for isnt there anymore.....it has all ben changed.

Cheers.

Ack it seems this broke in 3.6. Just went to use it on my board and the buttons don't show in the template anymore ugh. Anyone got an idea how to fix this in 3.6? I'm assuming this is what Cybertims was enquiring about.

This really ought to be a standard feature in vB... I can't see why you wouldn't want this and if anything you could turn it off...

Anyone have a link to the thread that was aforementioned for support of this as a feature in vB?