The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Upgrading - My understanding
Right here's my understanding of the upgrade process WITH hacks installed.
1. I know when i upgrade, i lose ALL PHP changes to my files. Hence any hack with php changes - is gone. 2. When i upgrade after overwriting all the php files, using the upgrade script - it changes the database. Will this alter tables and the like for hacks installed? If not, when i go about reinstalling the hacks - do i just leave the tables alone? Or do i need to back them up and overwrite them once the hacks is reinstalled? 3. Here's my assumption - from what i've picked up - Once upgraded, the upgrade DOES NOT ALTER ANY CUSTOM TEMPLATES. So custom templates are left well alone. HOWEVER - it does reset NORMAL templates, so any normal (header, footer etc) templates i've changed, need altered again. I'm sure there's nothing else, but if there can someone enlighten me. Sorry for having to go over this again - i just want it straight in my head before i go about this. Thanks for your time in advance. Chris. |
#2
|
||||
|
||||
1. Make a backup of your database (be sure its complete too, use ssh for a mysql dump) and back up your hacked vb files just in case something goes completely utterly horribly wrong.
2. Check out which files have changed between the vbulletin version your using now and the latest version available. One way of doing that is to read the announcements forum on vbulletin.com since they will tell you what files and templates have changed. 3. Download the latest vbulletin version if you havent already and unzip it to a new folder on your pc. 4. Use a file comparision tool like beyond compare, araxis merge, or winmerge (winmerge is free from sourceforge.net) to compare the the new files you just downloaded against your hacked files. You should only have to compare the files that changed between versions. 5. Take your time and look through the code. The differences will be highlighted. If you noted where your hacks begin and end, you shouldnt really have a problem seeing how to adapt the hack if in fact vb updated that segment of code. (if you havent noted where your hacks are in your files, then just compare your hacked vb files to the unhacked files for that same version to note it down) 6. Run the vb upgrade file. 7. Your basically done at that point but you may have to reinstall the templates from some hacks like ushop and cmps again. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|