Version: 1.00, by Lieva
Developer Last Online: Mar 2008
Version: 3.5.1
Rating:
Released: 01-21-2006
Last Update: 11-06-2006
Installs: 46
DB Changes Uses Plugins
Is in Beta Stage
No support by the author.
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.
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
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I don't have prefixes but the same problem... several edits (not just re-save) but all versions show the same text. Looking at the database I see the old version but it won't show up in the thread...
I don't have prefixes but the same problem... several edits (not just re-save) but all versions show the same text. Looking at the database I see the old version but it won't show up in the thread...
Which version of vbulletin are you using and also which version of the plugin are you using?
The original version should be a little more reliable as it doesn't do any checks before reverting to an older version.
I edited it now 8 times without success...
I tested the can_moderate condition (filled in some debug output in the showtread plugin) - this is working - I also printed out the history post as plain text on the page - this is also working.
So I guess it's a problem with this line
$post['pagetext'] = $post_temp['message'];
It seems that $post[pagetext] is not the place where my vB reads the post? Or it does overwrite it or something like that...
---
Edit:
Ok in post[pagetext] is the text of the post - I can read it out, it matches... but when I change it within the plugin the post itself doesn't change - so it seems to me that the forum takes the post text not from this var - but from where?
I just had to do an official edit on my own post, i forgot to
add an attachment and also had to edit again to include
more text, but again it only shows the latest edit even though
theres 4 links 0 to 3
I am going to try a single edit on another post...
I edited it now 8 times without success...
I tested the can_moderate condition (filled in some debug output in the showtread plugin) - this is working - I also printed out the history post as plain text on the page - this is also working.
So I guess it's a problem with this line
$post['pagetext'] = $post_temp['message'];
It seems that $post[pagetext] is not the place where my vB reads the post? Or it does overwrite it or something like that...
---
Edit:
Ok in post[pagetext] is the text of the post - I can read it out, it matches... but when I change it within the plugin the post itself doesn't change - so it seems to me that the forum takes the post text not from this var - but from where?
Maybe showthread.php was modified in 3.5.3.
If you set $post['pagetext'] to some string, then that would indicate if $post['pagetext'] is being used. It would only modify the post that you are viewing page history for.
Because your plugin does a
$post['pagetext'] = 'matched change post';
I can answer your question already - no it is not used by showthread... I'm trying to find the correct var it reads out
Because your plugin does a
$post['pagetext'] = 'matched change post';
I can answer your question already - no it is not used by showthread... I'm trying to find the correct var it reads out
Ahh ok. In 3.5.1 (and it seems 3.5.2), that variable is used for the message.
Is this section of code the same in 3.5.3 ? (are we allowed post code snippets as long as they are in [ code ] tags ? )