Post Edit History Viewer

When someone edits a post, the old message is stored in another table before the new one overwrites the old message.

Posts that have been edited will have "view edit history" displayed below the post count in the postbit.

Clicking "view edit history" allows previous versions of a post to be seen.

The postbit and postbit_legacy templates are altered using a similar method to the one used in the vbshout extension by Zero Tolerance, i.e. a search and replace. This means that no manual alterations to these templates are required.

Normally, everyone can see the post history for all the posts, however, the XML file post_hist_mods_only.xml restricts it to mods only (and the poster themselves). (Both versions should not be installed at the same time).

--------------------------------

Updated:

use post-hist_1_1b.zip

Changes

- Enable/Disable by forum
-- On/Off by forum

- Enable/Disable by usergroup
-- Can see own history: Yes/No
-- Can see everyone's history: Yes/No

- Indicates who made the edit (if it wasn't the original author)

- Workaround for unknown templates
-- Insert <<Insert Post History>> into postbit and postbit_legacy templates
-- (This is only for templates where the auto-match doesn't work)

The options are controlled by admincp.

By default, nobody can see any of the histories. At minimum, you should set the admin usergroup to see all histories.

Request

I don't know how 3.6.x products work, but if someone tries it on 3.6.x and it works, that would be good to know. I don't actually have 3.6 on our own forums, so can't test it.

Also, if you find out any bugs for < 3.6, that would be good to know too.

Install Info

The zip file contains:

bit_field_post_hist.xml -> XML for permissions
post_hist_1_1.xml -> product file

To install:

copy bit_field_post_hist.xml to /includes/xml

and install the product.

In theory, this should work as an upgrade to the previous version. However, I haven't tested that.

If you uninstall the old version and install the new version, you will lose any saved post histories.

Troubleshooting

bitfield cache
You might have to open:

yourserver.com/admincp/index.php?do=buildbitfields

This re-calculates the bitfields that have been altered. On some versions, the product installer will automatically do it.

Moderators
The postbits determine if a post is a person's own post by seeing if they have permission to edit the post. This means that if you give mods the rights to see their own post histories, then they will be able to click to see everyone elses post histories as they have the rights to edit all posts. However, the link won't have any effect as the actual viewer is restricted based on actual poster.

Usage

The XML file should add 2 options that can be set when setting up a usergroup and 1 new option for each forum.

New options for each usergroup:

Can See Post History (Yes/No)
---- Allows members of this usergroup to see all post histories

Can See Own Post History (Yes/No)
---- Allows members of this usergroup to see their own post history

New option for each forum:

Post History Displayed (Yes/No)
---- Shows post history for every post in this forum

[Alex_]

I added the cachable just to be sure... without there seem to come up some side effects when using the cache.

[Lieva]

Originally Posted by Alex_

I added the cachable just to be sure... without there seem to come up some side effects when using the cache.

Yeah, seems that it sometimes caches one of the older versions of the post.

Anyway, have updated both versions of the XML.

[Alex_]

Just another question

I guess can_administer is not a function like can_moderate?
Is it possible to restrict it to administrator only? I don't want my moderators to be able to view the history

[SnickersTK]

Wait, if your running 3.5.2 and you install the mod one, it should work now right?

I am scared of all the replies in this mod to install it :-(

[Lieva]

Originally Posted by SnickersTK

Wait, if your running 3.5.2 and you install the mod one, it should work now right?

I am scared of all the replies in this mod to install it :-(

Well, the worst that will happen is that it won't do anything. Also, the uninstall function will undo any database edit. The problems in this thread were pretty minor and don't represent a risk of damaging the database or anything.

The changes necessary for 3.5.2 operation are already included.

[Lieva]

Originally Posted by Alex_

Just another question

I guess can_administer is not a function like can_moderate?
Is it possible to restrict it to administrator only? I don't want my moderators to be able to view the history

You would have to check the person's main usergroup.

Something like ( $vbulletin->userinfo['usergroupid'] == 6 )

6 is the default admin usergroup, so you may need to change that.

[Alex_]

Originally Posted by SnickersTK

Wait, if your running 3.5.2 and you install the mod one, it should work now right?

I am scared of all the replies in this mod to install it :-(

You shouldn't be scared... IMO there are some problems with caching - after going around the vB post cache and testing it for a while my browser does cache some sites not showing then up right. But that's a browser thing...

I restricted now to a userid and I'm happy with it

[Alex_]

One last thing for me today... you should add the if condition to the postbit modifier as well so users who cannot view the history don't get the 'View History' link.

[Lieva]

Originally Posted by Alex_

One last thing for me today... you should add the if condition to the postbit modifier as well so users who cannot view the history don't get the 'View History' link.

The mod to the postbit should already mean that only those with rights to see the text can see it.

[Alex_]

Sure?
I don't see the according code... it's just a simple str_replace, isn't it?
When I restricted it to one user only this one could view the history but the link showed up for others as wellg giving them always the same version on every number...

My code looks now like

if ( $vbulletin->userinfo['usergroupid'] == 6 ) {

$vbulletin->templatecache['postbit'] =  str_replace( $insert_point,  $insert_point . $new_text , $vbulletin->templatecache['postbit'] );

$vbulletin->templatecache['postbit_legacy'] =  str_replace( $insert_point,  $insert_point . $new_text , $vbulletin->templatecache['postbit_legacy'] );

$vbulletin->templatecache['postbit'] =  str_replace( $insert_point2,  $insert_point2 . $new_text , $vbulletin->templatecache['postbit'] );

$vbulletin->templatecache['postbit_legacy'] =  str_replace( $insert_point2,  $insert_point2 . $new_text , $vbulletin->templatecache['postbit_legacy'] );
}