Post Edit History Importer
 

What is this?

The Post Edit History Importer (PEHI) is just that; an importer script. For those of us who were using Surviver's Post Edit History (PEH) hack, we are now pleased to see this functionality included in the default vBulletin package with the introduction of 3.7.0.

However, the hack's and vBulletin's way of logging post edit histories are somewhat different. So, thus, the need for this importer script arose. In a nutshell, it will import your past edit histories into vBulletin's new system.

What, exactly, does it do?

This script is a seamless import of the edit histories from the PEH hack into vB's system.

There are several key differences between vB's system and the hack's, among which are:

• vB stores iconid edits, the hack didn't
• The hack stored edits by comparing them in each record, while vB instead stores the original post once and subsequently all edits in a separate record

This importer will correct any mishaps between the two systems; it will assign postedithistoryids in the exact same order as they would have been if vB had inserted them, it will store original posts in the same way that vB does, it will assign iconids to make up for the missing ones that the hack never logged, and many other things.

If you're truly interested in checking out everything this importer does to make it "vB standard," you can read the code. I've commented enough that it should be discernible. ;)

Anticipated FAQ
Q: Can I use this importer if I already have edit histories in vB's new system?
A: Yes! This importer was designed to import everything seamlessly. After it is done organizing the old histories correctly, it will process new histories before clearing them altogether in order to rearrange them correctly. So, yes, you can.

Q: Which version(s) of the PEH hack is this importer intended for?
A: The importer has only be tested with PEH version 1.2.5. Since I haven't used the new beta version, I do not know the database structure and therefore this importer might not work on that version.

Q: How long does the importer take to do everything?
A: Not very long at all, I promise. But really, it depends on how many histories you have. Personally, I had 21,075 histories from the hack. After inserting the originals (14,033 of them), I ended up with 35,108 records total. How long did it take the importer to do all of that? 2 minutes.

(More to come later if need be...)

Using the importer
To use the importer, just download the .zip file attached, unzip it, and open the 'readme' file. Instructions are included there.

Afterward
After you've used the importer, feel free to post your stats here! I'd love to hear how it worked out for you. :)

Enjoy! :D

Nice, Thank you very much. But I don't like the new post history, becaus the edit is only saved if you entere a edit reason.

As far as I can tell, you don't have to enter a reason. But it will only save the edit if the "Last edited by" message is shown. :p

(which yes, I dislike as well ;))

i installed . working hard. thank for upgrade

I can't really help if you don't post the database error. ;)

How do you feel this hack will load the system if you have several million posts? Is it very intensive to search this out?

Thanks,
David

My forum had about 35,000 stored edits when I ran the importer and everything went smoothly.

However, I would suggest you run the importer on a copy of your database, not your live website, first, just to be sure. :)

I runned the script perfectly, I choose to remove the tables, but once I tried to uninstall the old product from the product page on admincp, I got this error:

Ack. I didn't realize that the tables are removed by the uninstall script. Did it uninstall the product okay for you? This isn't going to cause a major problem, I just want to make sure you can uninstall it correctly.

However, I will remove the tables option from the script and just add a message to uninstall the product. :)

No bro, I couldn't uninstall the product right.
Any way you can help me out?