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

[Lieva]

Originally Posted by bashy

OK just mad a single edit with a 4 word text edit
and the links only show the latest edit!!

You have to click view post history at least once ... or does it just show

View Edit History: 1

and not

View Edit History: 0 1

?

[Alex_]

From the hook on:

 ($hook = vBulletinHook::fetch_hook('showthread_postbit_create')) ? eval($hook) : false;

                $postbit_obj =& $postbit_factory->fetch_postbit($fetchtype);
                if ($fetchtype == 'post')
                {
                        $postbit_obj->highlight =& $replacewords;
                }
                $postbit_obj->cachable = $post_cachable;

                $post['islastshown'] = ($post['postid'] == $lastpostid);
                $post['attachments'] =& $postattach["$post[postid]"];

                $parsed_postcache = array('text' => '', 'images' => 1, 'skip' => false);

                $postbits .= $postbit_obj->construct_postbit($post);

Hmhm, I don't understand it... does the postbit constructer change something?!

---
Edit

The constructer does this

 $this->post['message'] = $this->bbcode_parser->parse($this->post['pagetext'], $this->forum['forumid'], $this->post['allowsmilie']);

So he does use the pagetext - *confused*

[Lieva]

Originally Posted by Alex_

From the hook on:

 ($hook = vBulletinHook::fetch_hook('showthread_postbit_create')) ? eval($hook) : false;

                $postbit_obj =& $postbit_factory->fetch_postbit($fetchtype);
                if ($fetchtype == 'post')
                {
                        $postbit_obj->highlight =& $replacewords;
                }
                $postbit_obj->cachable = $post_cachable;

                $post['islastshown'] = ($post['postid'] == $lastpostid);
                $post['attachments'] =& $postattach["$post[postid]"];

                $parsed_postcache = array('text' => '', 'images' => 1, 'skip' => false);

                $postbits .= $postbit_obj->construct_postbit($post);

Hmhm, I don't understand it... does the postbit constructer change something?!

It looks the same as mine. postbit_obj->construct_postbit($post) generates the actual code for the postbit.

Perhaps that has been changed.

In
includes/class_postbit.php

The postbit functions are defined.

There should be a section of code something like:

/**
* Parses the post for BB code.
*/
function parse_bbcode()
{
$this->post['message'] = $this->bbcode_parser->parse($this->post['pagetext'], $this->forum['forumid'], $this->post['allowsmilie']);
}

Maybe that refers to a different variable.

[Alex_]

I just edited
This is the same code as mine... I am confused...

[Lieva]

Originally Posted by Alex_

I just edited
This is the same code as mine... I am confused...

hard to debug without the files in front of me .

One other possibility is that there is a parse error in the plugin. This results in the server just ignoring it. You could add another plugin at the same hook with just $post['pagetext'] = "testing" and see if that modifies the message.

Also

showthread.php?p=68298&prev_postid=68298&prev_edit num=0#post68298

should show the original version of a given post (change 68298 to the postid of the post you want to check).

[Alex_]

I just did a $post['pagetext'] = "something" within the showthread.php to show _all_ posts with the same text but the they were still the same... so this couldn't be.
I opened another thread and now it showed the forced text.

I think this has something to do with post cache (not browser cache because I have two browsers showing the same).
So if you open the thread the posting gets cached... now you click on history version - the page reloads but the forum says - hey, I just showed you this thread, I'll load it from the cache...

This would mean I have to hook in on an earlier stage? I don't know how the cache system works but we do cache posts for 10 days I think...

[Lieva]

Originally Posted by Alex_

I just did a $post['pagetext'] = "something" within the showthread.php to show _all_ posts with the same text but the they were still the same... so this couldn't be.
I opened another thread and now it showed the forced text.

I think this has something to do with post cache (not browser cache because I have two browsers showing the same).
So if you open the thread the posting gets cached... now you click on history version - the page reloads but the forum says - hey, I just showed you this thread, I'll load it from the cache...

This would mean I have to hook in on an earlier stage? I don't know how the cache system works but we do cache posts for 10 days I think...

Sounds reasonably and might explain why Bashy was having some issues which fixed themselves.

One test that might be worth doing is to disable post caching and see if that fixes it.

[COBRAws]

leet

[Alex_]

Yes it did sound reasonably but setting it to zero doesn't change anything

[Lieva]

Originally Posted by Alex_

Yes it did sound reasonably but setting it to zero doesn't change anything

That's wierd. I set mine to 10 days and it broke it ... maybe it would take 10 days to clear the cache ...