PDA

View Full Version : Typo in upgrade script


ToyotaDiesel
Sat 6th Dec '08, 5:18am
upgrade_370b2.php line 64. looks like a double comma.

Was upgrading from 3.6.4 directly to 3.8
Wayne Luke
Sat 6th Dec '08, 10:04am
Line 64 is a query.. What is the specific database error shown to you?
ToyotaDiesel
Sat 13th Dec '08, 10:46pm
It was giving a database error on upgrade, saying a problem on line 64. What I did to resolve it was upgrade from 3.6.4 to 3.7.(whatever the latest was) and then from that version to 3.8.0RC1. Something in that file is bad though. Sorry it wasnt worth trying to figure out, I needed to get the site back up. That issue will flare up again though if anyone is upgrading using the 3.8 script and running through that version upgrade file.
JamesAB
Sun 14th Dec '08, 2:49am
A couple others of us posted about this too. You can't seem to upgrade from 3.6 directly to 3.8

The only way I've gotten it to work on my test forum is to upgrade from 3.6 to the latest 3.7. Then upload the 3.8 files and finish the upgrade.

Thanks,
James
ToyotaDiesel
Sun 14th Dec '08, 3:26am
Yeah that's what I did to get around it. Just wanted to let someone know there was a problem.
Wayne Luke
Sun 14th Dec '08, 12:04pm
It was giving a database error on upgrade, saying a problem on line 64. What I did to resolve it was upgrade from 3.6.4 to 3.7.(whatever the latest was) and then from that version to 3.8.0RC1. Something in that file is bad though. Sorry it wasnt worth trying to figure out, I needed to get the site back up. That issue will flare up again though if anyone is upgrading using the 3.8 script and running through that version upgrade file.
Hopefully they will provide the exact error message so we can fix the issue so people don't have to do a work around.
ToyotaDiesel
Sun 14th Dec '08, 3:11pm
Wayne, if vBulletin offered a discount to those who would R&D the product then it might justify taking the time to cleanly report bugs. I paid full price for a working product. Granted I was knowingly installing a release candidate, I took it upon myself, knowing there is "no support" to get around the issue on my own means. So, don't take an attitude with me because I did not do enough to do someone else's job. I thought I was being kind enough to point out the EXACT file that has the problem.

Thank you.

-Ben
Zachery
Sun 14th Dec '08, 5:42pm
If you find a bug you should report it in the bug tracker so the developers can address it.
ToyotaDiesel
Mon 15th Dec '08, 10:46am
Thank you, Zachary. Where is this bug tracker?
Zachery
Mon 15th Dec '08, 10:54am
http://www.vbulletin.com/forum/project.php?do=issuelist&projectid=6&issuetypeid=bug&appliesversionid=g15 That would be specificly for 3.8.