Upgrading to 1.1.5 questions

[mjames]

Hi everyone,

Okay, here's the deal. I've had my vBulletin for about two months now and it has worked beautifully. I recently got the e-mail from Jelsoft about upgrading to the new 1.1.5 version to correct security holes. I currently run 1.1.4.

I want to know exactly to this upgrade process works. The way I understand it, I have to download the files from my member page and run the upgrade.php3 (I'm still on PHP3) file. Is this how it works? How does the upgrade.php3 file work? I've never upgraded before and want to assure this doesn't mess up my boards.

More questions: should I temporarily close my boards while I upgrade? Can I backup my templates and settings?

[John Harrison]

Close the board? Yes

You can pick to lose your templates or not.

My settings were not changed after the upgrade.

[Parker Trasborg]

I upgraded earlier today except it was regular PHP. I just uploaded all the files it had to where it said. I ran the upgrade and it worked fine. Only thing lost were hacks, all the templates stayed the same.

[JamesUS]

It's always a good idea to backup your database first, with phpMyAdmin or telnet. If you search the board there are some good instructions on that.

[mjames]

Thanks, guys - I took the chance and got the upgrade successfully done last tonight.

[CorvetteNH.com]

For some reason, I can't shut my board down. The option "bbactive" is set to NO and I submitted the changes. The board is still freely accessible. I went ahead and uploaded the newreply, newthread and member files as recommended for those of us that have installed hacks, but I have no way of knowing if my forums are now updated or not.

-Rob

[Mike Sullivan]

As an admin you can bypass the shutdown :)

[CorvetteNH.com]

That still doesn't make sense though. The number of users and guests is constantly changing on the boards. Users are logging in and out.

-Rob

[Mike Sullivan]

It still hits the session table.

[Martin]

the users will still show on the board even though they are not actively browsing the board. The session table reads the cookie as soon as they hit index.php, which the message replaces. It's just that they are trying to get onto the board, not they they are actually on it.