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

[silurius]

This is awesome. Been looking for this for a while. It covers about half of a request I put out.

Would you mind establishing a wishlist for this thread and adding version comparison & revert capability to that list? (Even if you can't get to such features yourself, at least they'd be noted somewhere central).

Will definitely install when it matures a bit. Thank you!!!

[Alex_]

But I like the cache feature...
I tried it with $post_cachable = false within the plugin without success... there must be point when the forum decides to use the cached version.

[Lieva]

Originally Posted by Alex_

But I like the cache feature...
I tried it with $post_cachable = false within the plugin without success... there must be point when the forum decides to use the cached version.

It seems that if

$post['pagetext_html'] exists then it uses that instead of $postbit['pagetext'].

Adding:

$post['pagetext_html'] = "";

to the end of the plugin fixed it for me.

If this solves your problem, I will update the two XML files.

[Lieva]

Originally Posted by silurius

This is awesome. Been looking for this for a while. It covers about half of a request I put out.

Would you mind establishing a wishlist for this thread and adding version comparison & revert capability to that list? (Even if you can't get to such features yourself, at least they'd be noted somewhere central).

Will definitely install when it matures a bit. Thank you!!!

Is there a wishlist function or something (or do you just mean that I would add a wishlist section in the original post ) ?

[Alex_]

Originally Posted by Lieva

It seems that if

$post['pagetext_html'] exists then it uses that instead of $postbit['pagetext'].

Adding:

$post['pagetext_html'] = "";

to the end of the plugin fixed it for me.

If this solves your problem, I will update the two XML files.

Not yet...

[Lieva]

Originally Posted by Alex_

Not yet...

It had no effect ?

[Lieva]

Originally Posted by Lieva

It had no effect ?

Try adding:

$post_cachable = 0

too. I assumed that that wasn't needed.

[silurius]

Originally Posted by Lieva

Is there a wishlist function or something (or do you just mean that I would add a wishlist section in the original post ) ?

Wherever, doesn't really matter to me, just so long as it's somewhere visible.

[Alex_]

Originally Posted by Lieva

Try adding:

$post_cachable = 0

too. I assumed that that wasn't needed.

Argh, I'm sorry - while testing I tried several other hooks - I forgot to switch back.
It is working now, great work.

[Lieva]

Originally Posted by Alex_

Argh, I'm sorry - while testing I tried several other hooks - I forgot to switch back.
It is working now, great work.

great, hopefully it stays working .