Upgrade instructions? More...

[Limey]

The upgrade instructions for beta 4 say upload the new files...which files?

Upload all .php files? Everyone of them? Nothing will be affected?
What about hack preservation?

According to the announcement only template files were changed?

And then run the query through phpMyAdmin for example?

I don't want to screw anything up....thanks

[Kier]

Okay, here goes:

If you haven't upgraded to beta 4 yet, download the latest version (beta 4.1) from the members area.

You will need to upload the entire contents of the Upload folder (in the vbulletin2.zip) to your forums directory.

Any hacks that have altered the original PHP files will need to be re-applied.

Your customized templates will NOT be affected, but you should check to see that your custom versions contain all the necessary variables for any new functionality we may have added.

[klisis]

4.1's out already?

[Limey]

I get this error when running the upgrade script

We have detected that you have already tried to run the upgrade script. You will not be able to proceed unless you
revert to a vB 1.1.5 database.

[netspark]

My installation got hung up on step 9... I rechecked my config file to make sure everything was correct.. now when I try to reinstall I get the following message:

It appears that you have already run this script or made the changes by hand. You will not be able to continue until you remove these
additions

What additions do I need to remove to proceed?
Thanks!
Mike

[klisis]

Also, to update your templates, import the vbulletin.style file from the ZIP, using your control panel. As usual, this will not overwrite any customized templates.

How can I import vulletin.style from Control Panel?

[Kier]

To make my life easier, when you post a question about upgrading, please post the following info:

• what version of vBulletin you are currently running
• what script you are trying to run to install beta 4.1

thanks.

[Wayne Luke]

Originally posted by klisis


How can I import vulletin.style from Control Panel?

Click on "Upload/Download Style".

Then follow the form for uploading from a file on your server (the bottom one).

[klisis]

Ver 4.0

I am not trying to run any install or upgrade script.
As John posted, I am trying to import the newest style file but I don't know how.

[Brent]

I just posted this in annoucement discussions but i think he's got the same question i got

Upgrading from Beta 4.0 ---> 4.1

you say in the annoucemnts page only upload the 'new files'

how do we know which files are the new files?

so all that i will have to do is just upload them to the server and then that's it? no script to run or anything?

[klisis]

No need to run any upgrade script, it appears. Just upload the whole php files and that's it , I think.

[Kier]

That's correct. To upgrade beta 4 to beta 4.1, just upload all the files from the upload folder in the zip, then run the query John mentioned in the announcent. You can run the query through phpmyadmin if you have it.

[netspark]

I was upgrading from 2.0 Beta 3 to Beta 4 and my installation got hung up on step 9... I rechecked my config file to make sure everything was correct.. now when I try to reinstall I get the following message:

It appears that you have already run this script or made the changes by hand. You will not be able to continue until you remove these additions


What additions do I need to remove to proceed?
Thanks!
Mike

[netspark]

I'm sorry,
My post above should actually read:

I was upgrading from vBulletin 2.0 Beta 3 to Beta 4.1 and my installation got hung up on step 9... I rechecked my config file to make sure everything was correct.. now when I try to reinstall I get the following message:


It appears that you have already run this script or made the changes by hand. You will not be able to continue until you remove these additions


What additions do I need to remove to proceed?
Thanks!
Mike

[Limey]

Where do you run the query in phpMyAdmin or should I say how? When I put the query in the box it just hangs there.

Do we replace our admin/*.php files as well?