Tutorial: how to easily Upgrade your vBulletin using the Hack Tracking Log:
 

If you use Hack Tracking Log-exclusive hacks (and, all things considered, why wouldn't you?), you can upgrade your vB3 easily.

1. Go to the List All Modifications page, and decide whether you want to list ALL modifications at once, or work off the list on a one-hack-at-a-time basis.

2. Make sure to keep this page open in a tab or browser window that you're not using for the upgrading process. Overwrite all files with their newer vB3 equivalents.

3. Perform the upgrade as usual, ie. go to yoursite.com/forum/install/upgrade.php and follow the on-screen instructions. After upgrading, go back to your tab/window from the Hack Tracking Log.

4. Now work off the list of file- and template edits for each hack.


Voil?, you are done. Upgraded your vB and it didn't take any figuring out or file-comparisons programs or utilities. Just the HTL. :)



During step 4:
Should a line number be different due to the new version of vBulletin, you might want to inform the Hack Author of that. Should a certain modification become impossible because code has changed too radically, you really really should inform the Hack Author right away. :)

so what is the advancetage when using HTL for upgrading ?
I see it just adds in the HTL list that an upgrading process has been done

nice Kura :)

Actually:

http://everythingvb.com/faq.php?faq=...ils_advantages
and
http://everythingvb.com/faq.php?faq=...faq_whyhtlonly


The above is just a tutorial on how you can easily upgrade your vBulletin if you have only installed HTL-hacks. So there's a huge benefit for you if you only install HTL-compatible hacks, cos then upgrading your vB has never been easier (except for unhacked boards, of course :D)

Incredible! :)

What if you don't use FTP to upload the vb files, but rather Cpanel and extract them. Won't it overwrite HTL's files as well?

See step #2 - you keep the page open in a browser tab / window, so that you can safely overwrite all files, including the ones that you modified for the HTL.

If it overwrites hacklog.php (for instance) you need to contact your host, cos it shouldn't do that, and if it does your server is highly unstable :)

The only reason that this makes the process easier is that all file changes are documented. But either way the user only has to load the text file and re-apply the file/template edits again. The advantage here is minimal.

I find it to be quite better than having to go through all of my txt and install files and do each one over again

btw, does the HTL automatically do all of the other stuff it does with a .htl file after the upgrade? such as queries, new templates, phrases, etc.?

MGM out

<a href="https://vborg.vbsupport.ru/showthread.php?t=62508" target="_blank">https://vborg.vbsupport.ru/showthread.php?t=62508</a>

Any idea what's causing that error?