I have played around with adding some hacks to vBulletin (private messaging, polls, etc...), and I really think that I have a good feel for doing this now. However, when I used to hack UBB, I would modify the cgi scripts on my laptop, test, maybe add some more hacks, test, then upload everything to my server when I was happy.

However, I wanted to ask how people usually handle testing vBulletin hacks and then installing them. I ask since it's not just a matter of copying/upload new scripts, but quite a few hacks also involve database schema changes and changes to some template records... what is the easiest way to port these from a test board to a production board?

Thanks,
-Chris

For me, it's basically the same as installing a UBB hack. The only difference is that you might have to change the structure of the database.

To install a UBB hack:
1. Edit scripts
2. Test
3. Upload to release board

To install a vB hack:
1. Edit scripts and structure
2. Test
3. Edit structure of release board
4. Upload to release board

So, the only real difference is editing the structure. And if that is done correctly, you should be able to basically remove the hack's code, but leave the extra tables.

Thanks Mike.

I know it's not too much different. I was just wondering if there was a way to dump all the structure changes I made in test and apply just that batch of changes into production. For example if I am installing a few hacks at once. But I guess the best approach is to just take them one at a time.

Thanks,
-Chris

well, php is much easier for people to add hacks, the code is simpler. Best is one hack at a time, so you can find any bugs (or paste errors) easier.

Ok sounds like good advice, I'll just do them one at a time... I am just so eager to install a bunch of great hacks that are here :)

Thanks,
-Chris