A little help upgrading to VB3 from a hacked VB2?
 

Hi,

I am planning on upgrading to VB3 soon, but I am worried about how everything will work out since I have added quite a bit to my database (i.e. tables, rows, etc). I'm not worried about my hacks working on the new version, but I definately would like to be able to port over all the user information, and threads. Some user fields are custom fields that I have added as well...

It would also be convenient if styles could be ported, although not as important as the other things I mentioned...

What is the best way to go about doing this? Thanks for any help in advance. :)

~006

IIRC there was a tool downloadable at vb.com which will check out your DB if you can upgrade to vb3 without problems

Yes there was such a tool @ vb.com, written by Steve methinks, but it didnt work too good :D

u can upgrade to vb3 from a running vb2 board - but most of the hacks wont work though
just run upgrade2.php

here is how i did mine

first of all i made a new sql databse - i then took the databse from my v2 board
then i uploaded gold to my server and ran upgrade2.php (NOT INSTALL.PHP) and i made sure the config file pointed to the same databse as i had just upped the v2 databse 2 (just incase mistakes happened i never wanted to touch the main board)

anyway after going though endless prompts (about 46 in all) then loads more lke 1/9 etc it worked fine - every post - user etc was in vb3.
Also dont count on your styles working cause none of mine did.

The styles didnt work because the style system changed totally :P

I amnt sure, having not upgraded, but wouldn't added/altered tables pose a problem?

http://www.vbulletin.com/forum/showt...threadid=73163
(Just spent half-an-hour looking for that:()

Well I copied my database and I am going to test some things on the second one. (Password protected for those concerned..). If all goes well I will do the real thing shortly.. Might have to kill the forums for a few days though. :(


42 steps... Well it will be a long time until I know if this works I guess. Too bad i'll have to do this twice. :(

Shoot. I had a database error on step 19 (custom fields step) so I skipped it figuring it might not be a huge problem. Apparently VB3 doesn't like something about my user fields:

Database error in vBulletin 3.0.1:

Invalid SQL: SELECT profilefieldid,type,data,optional FROM profilefield
mysql error: Unknown column 'data' in 'field list'

mysql error number: 1054

Is this going to be hard to fix? :(

Ok then when I try to log in I get this:

Database error in vBulletin 3.0.1:

Invalid SQL:
SELECT profilefieldid, required, title, type, data, def, height
FROM profilefield
WHERE form = 0
ORDER BY displayorder

mysql error: Unknown column 'data' in 'field list'

mysql error number: 1054


Please help if you can anyone. Thanks. :)

The data column doesn't exist. Which page are you getting the error on? Try searching for the query and remove data, from it and see if that works? Jsut a suggestion, but I could be in the wrong on this one. :o

I get that error in the admin cp when searching for users, when trying to log in on the forum home, and on step 19 of the upgrade process. :(

I got this too when changing styles on the dropdown menu on forum home:

Invalid SQL: SELECT templatesetid,replacementsetid,userselect FROM style WHERE
styleid='2'
mysql error: Unknown column 'templatesetid' in 'field list'

mysql error number: 1054

i got an error when upgrading from one v2 to vb3 but all i did was change the step in the url and continue - it aint come back to haunt me yet :)

That's what I did... It's haunting me already.. :(

Any ideas anyone? Has this happened to anyone else? :(

Sorry to bump, but I am at a dead end here. Just trying to get this seen my someone who has been in my shoes hopefully. Thanks. I haven't dealt with the VB3 database at all yet.

Well I got it working just fine now. I've now upgraded to VB3 without any problems. :) Thanks for that link assassin. That's what I ended up using to find the problem. I just had one column in one table to rename and then everything worked fine.

Thanks :)