deviataz
Thu 12th Jul '07, 6:17pm
Hello,
I've done the following:
1) created a backup of a vb307 forum
2) restored that backup to new database
3) uploaded vbulletin vb367 to new dir and edited config to match new database
4) done the upgrade routine successfully
5) fixed the forum via tools.php and reset as much as I could to:
Now I got my forum vb367'ed, however it still has loads of traces of old vb3.0.7 hacks & modifications in it. I was hoping that uploading a clean vb367 package into a new directory would get rid of all 3.0.x hacks etc. But they still are present, for example in the settings menu I still see configuration menu's for those old hacks. I even see old profile fields used in vb3.0.7! Ah!!!
All I really want is a nice clean fabric vb367 with my vb307 (upgraded-to-vb367) database.
My question: how do I remove those vb3.0.x traces from my vb3.6.7 forum? vBulletin 367 is far too superior to have those vb307 traces in it!!!!
Thanks a lot for any help that makes my vb367 a true vb367!
Greets,
Deviataz.
I've done the following:
1) created a backup of a vb307 forum
2) restored that backup to new database
3) uploaded vbulletin vb367 to new dir and edited config to match new database
4) done the upgrade routine successfully
5) fixed the forum via tools.php and reset as much as I could to:
Now I got my forum vb367'ed, however it still has loads of traces of old vb3.0.7 hacks & modifications in it. I was hoping that uploading a clean vb367 package into a new directory would get rid of all 3.0.x hacks etc. But they still are present, for example in the settings menu I still see configuration menu's for those old hacks. I even see old profile fields used in vb3.0.7! Ah!!!
All I really want is a nice clean fabric vb367 with my vb307 (upgraded-to-vb367) database.
My question: how do I remove those vb3.0.x traces from my vb3.6.7 forum? vBulletin 367 is far too superior to have those vb307 traces in it!!!!
Thanks a lot for any help that makes my vb367 a true vb367!
Greets,
Deviataz.