How do I upgrade??

[LeroyP]

These instructions make no sense to me. http://www.vbulletin.com/docs/html/upgrade
I am running 3.7.0 right now and downloaded the new 3.7.1
Where do I put this new one? Right over the top of the old one? Where is this upgrade.php the directions speak of?
Ive never done this before and none of it makes sense.

Also backing up. Admin panel says that the existing xxxxxx.sql is not a good sopt to backup because it can be downloaded by everyone and I should make my own??? Is this a folder? a database? Again the directions for this are in hebrew. please help.
thanks.

[Jase2]

First thing to do once downloaded, is extract the files. You will have two directories; "upload" and "do not upload", alongside other files, such as readme, license agreement, ect.

You only need the "upload" directory, which will contain all the vBulletin files. Now, connect to your FTP program, and login to your site - using your ftp login details. Now, find the directory where your forums are. Simply drag all the files and directories from the "upload" directory on your computer over your currently vBulletin files. One by one for each directory is better. You will most likely be prompted by the FTP client at this point to ask if you want to overwrite the existing files. You should confirm this prompt, telling the FTP client that yes, you do want to overwrite the existing files. If the prompt gives you the option to overwrite all existing files without prompting again, use this option.

Once all files have been overwrote, it's time to run the upgrade script!

Warning:

Certain browser plug-ins, most notably the popular Google Toolbar can have an adverse effect up the vBulletin installation and upgrade scripts. We recommend that all browser plugins be disabled while running install and upgrade scripts for vBulletin.

Next, point your web browser at http://www.example.com/forums/install/upgrade.php, replacing www.example.com/forums with the correct URL to your own vBulletin installation.


Once the page has loaded, you will be asked to enter your customer number. This is done to prevent other users from accidentally stumbling across your upgrade script and running it. Only you should know your customer number - you can find it in your email address when you purchased vBulletin.

When you have entered your customer number, hit the [Enter Upgrade System] button and you should be taken to the first step of the upgrade script. If after hitting the [Enter Upgrade System] button you are brought back to the customer number entry dialog, there was an error verifying your customer number. Please check for mistakes and try again.

As each step completes, a [Next Step] will appear at the bottom of the page. When the button appears, the step has completed successfully and clicking the button will advance you to the next step. Continue doing this until the upgrade tells you the upgrade has finished.

Warning:

Do not refresh/reload any page of the upgrade scripts. Doing so may cause database alterations to be applied twice, which can cause errors.

I hope you can understand these steps, as in all honestly, they are really easy to do once you know how.

[Lynne]

You put the new files right on top of the old files - you just replace them all. Then run the upgrade script (see Running the vBulletin Upgrade Script "To do this, point your web browser at http://www.example.com/forums/install/upgrade.php, replacing www.example.com/forums with the correct URL to your own vBulletin installation.")

The xxxx.sql is a file - a backup of your database. You do NOT want to put it in your public_hmtl directory because anyone can get to that. You want to put it above that, ie. if you path is actually /home/yoursite/public_html/ you want to put it in /home/yoursite/.

I'm not sure what you mean about the directions being in hebrew??? The online manual is in english.

edit: Jason beat me to it and his instructions are much better than mine!

[LeroyP]

Perfect Jase2.... a lot of stuff you said was left out of the directions, as if your supposed to know already.