[Lieva]

Originally Posted by Djamil

I doubt it since this is already under consideration for a standard feature and Lieva was not online for over a month. Feel free to support all people at vb.com that expressed their needs in the thread. :-)

For the meantime I maybe will post in one of the help forums here since it should be no big deal to make this available to mods only. Should be a simple template conditional which I don't know how to place into the XML-file - somebody should be able to help if I find the time to post a proper request.

Djamil

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 ?