config.php instructions in eva2000's upgrade instructions?

[arossphoto]

I'm working on an upgrade from 3.5.4 using eva2000's upgrade instructions, but I'm confused about what to do with the config.php file.

The instructions say:

5...Upload all the vBulletin files except the images/ folder and config.php.new to temp directory.

6. edit upgrade file's config.php in new temp directory's /includes/config.php folder and point the databasename to the new empty databasename you created in step 3.

It's not clearly stated, but am I supposed to copy the config.php from my original installation into the temp directory and then edit it to point to the new database?

He also says not to upload the images folder. How can the new board possibly run without the images? Did he (or she) just forget to say that you should upload the images folder in binary?

I'm also confused about the instructions regarding hacks, but I searched here and found some rather terse responses to people who asked for clarification about that part.

I don't want to elicit the same reaction, and I actually want to start fresh with a clean board with no hacks. So I was thinking about disabling all hacks on the upgraded board by adding define('DISABLE_HOOKS', true); to config.phpuntil I get things sorted out.

Is this a good idea?

Thanks,

Andrew

[eva2000]

you're meant to work with vB 3.6.x's config.php.new and rename to config.php which is an implied step and edit config.php

The images folder statement is for same version upgrades within vB 3.5.x.. of course moving to a new version up 3.6.x upload the images :)

Yes it's a good idea to disable plugins/hacks before upgrading if you follow my method you'd be only disabling hacks on a copy of your live database anyway.

[arossphoto]

you're meant to work with vB 3.6.x's config.php.new and rename to config.php which is an implied step and edit config.php


Thanks for your response and for posting your upgrade method. I think it's a great procedure, but I really hope you will consider updating it to clarify some of the points that are "implied".

I went ahead with the upgrade last night, and tried my best to fill in the blanks. I compared your method to the manual and realized the images folder was obviously required, so I uploaded the folder from the downloaded 3.6 vB zip file.

However, based on my understanding of your instructions I copied the config.php folder from my old 3.5.4 installation into the new 3.6.3 folder and pointed it to the new database. The upgrade seems to have gone all right, so I hope I don't have anything to worry about.

I also could not figure out what you were suggesting when you said "It's at this stage if you have hacks on your database, you can remove them from this test duplicate copy of your database". I interpreted this suggestion to remove something from the database as meaning I should drop tables that were installed by hacks. What else could it mean?

I realize now that was a mistake because when I try to uninstall those hacks from within the vb admin I get an error because the tables are missing.

I searched these forums for clarification about this advice before I did it, but as I mentioned in my first post several other people have asked the same question and received blunt advice to ask somewhere else.

However, the advice was posted and pinned here as a recommended alternative upgrade procedure. So I think it's only fair to ask for clarification here. I realize specific questions about specific hacks should be asked at vb.org, but the advice you're offering here really should be clarified.

Sorry for being so long winded and I really do appreciate your advice. I just think it could be much better and more easily understood with a couple extra sentences for clarification.

Thanks again,

Andrew

[eva2000]

Thanks for the feedback, i've updated the sticky but the remove hacks on database is meant to mean remove hacks from duplicate vB install since not all hacks are database alterations, some can be php file edits or plugins.

so logically you remove hacks the same way they were installed, plugins removed via plugin system, php file edits via php file edits or just use upgrade vB files etc

The whole purpose of the sticky thread of mine is so even if you do stuff up the upgrade you only stuff up a copy of the actual database, leaving the original untouched :)

[arossphoto]

so logically you remove hacks the same way they were installed, plugins removed via plugin system, php file edits via php file edits or just use upgrade vB files etc


Thanks. I know what you're saying and I hate to be a pain, but at the point in your instructions where you advise removing the hacks all you've done is imported the database and uploaded the new installation files. You haven't renamed config.php.new, run the upgrade, or entered your customer number. So you have no access to the admin panel or the plugin system to "remove hacks the same way they were installed".

So shouldn't you remove hacks after step 8 in your instructions?

Thanks again and I really do appreciate your advice.

Cheers,

Andrew

[eva2000]

Guess more updates to the sticky are needed :)

[deep_blue]

Hi

I think you mean to say that i shall install fresh copy of vbulleting latest version in anew folder. migrate existing data there and then delete the older one. is that correct.

[arossphoto]

Hi

I think you mean to say that i shall install fresh copy of vbulleting latest version in anew folder. migrate existing data there and then delete the older one. is that correct.

I took me awhile to get my head around this as well, but the key to eva2000's upgrade procedure is the creation of a second database that contains an exact copy of your existing vBulletin database. I didn't have the ability to do this myself, so I had to ask my server for help creating a new database and importing the data from the old one into the new one.

Then you install the new vB files in a new folder and point it to the new database. Once you're happy with the new installation you follow the instructions to rename the folders and delete the old installation.

If you read eva2000's procedure, as well as the manual, a few times it will start to make sense, but as I mentioned here I think the instructions to remove hacks are out of order.

Cheers,

Andrew

[Gary Fischman]

I'm also a bit confused about the "Remove Hacks" statement. (Sorry, but its a complicated subject.) Since the temp directory only contains a fresh copy of the latest uploaded version, there would be no hacks in the code.

Or do you mean that any templates that have been customized need to be "reverted"? And if so, they wouldn't be revertable until after the upgrade.

Can you clarify?

[Gary Fischman]

Bump.

[arossphoto]

Check out eva2000's original pinned instructions, they have been updated and make more sense now. Once you finish the upgrade and log-in to the admin you will be prompted to revert any templates that are causing conflicts. That's what happened to me anyway.

I also recommened turning off all hacks on your existing board before you start this and to be extra safe add define('DISABLE_HOOKS', true); to your new config.php file. This will ensure that no hacks are running. Once you've got the default board running okay, you can remove the disable_hooks line and turn your hacks back on one at a time.

Good luck,

Andrew