Beta 7 to gamma...DB error on step 2

[Mike Sullivan]

Good to hear! Have fun! (Thanks for the help too, BTW.)

[Codeman05]

wooooohoooooo
Great job!
Works like a charm!!!
Even my styles/hacks are working like normal.

Keep up the great work guys

[Codeman05]

excellent, your the man Mike. About to try the fix right now

[ManagerJosh]

New Files: http://www.vbulletin.com/forum/showp...18&postcount=5

[Mike Sullivan]

Fixed scripts are available in that thread now. Let me know how they work for you.

[Codeman05]

See Mike Sullivan's post in the Announcement Forum.

Yea I did, I just wanted to answer your response

Can't wait to get the "fixed" script

[ManagerJosh]

See Mike Sullivan's post in the Announcement Forum.

[Codeman05]

go through phpMyAdmin and add "title" as an index, then rerun the upgrade

Right, I did that and now get

Database error in vBulletin 3.0.0 Beta 7:

Invalid SQL: ALTER TABLE template ADD UNIQUE title (title, styleid)
mysql error: Duplicate entry 'footer-1' for key 2

mysql error number: 1062

Date: Friday 05th of December 2003 12:55:04 AM

[ManagerJosh]

go through phpMyAdmin and add "title" as an index, then rerun the upgrade

[Codeman05]

Interesting, now I'm getting this error on step 1

Database error in vBulletin 3.0.0 Beta 7:

Invalid SQL: ALTER TABLE template DROP INDEX title
mysql error: Can't DROP 'title'. Check that column/key exists

mysql error number: 1091

Date: Friday 05th of December 2003 12:00:47 AM

[ReveX]

Actually, here is the db error I am getting:

Database error in vBulletin 3.0.0 Beta 7:

Invalid SQL: ALTER TABLE template ADD UNIQUE title (title, styleid)
mysql error: Duplicate entry 'header-1' for key 2
mysql error number: 1062

[Codeman05]

glad I'm not the only one lol

[ReveX]

Same here

[Donnie Darko]

I got the same error

[Codeman05]

Hi guys, trying to upgrade from VB3 Beta 7 to VB3 gamma. Keep getting this error on step 2 though. I ran the table repair in the AdminCP and it said all was fine. Any ideas??
thanks

*Dropping index on template table


There seems to have been a slight problem with the Wrangler-Forums.net Bulletin Board database.
Please try again by pressing the refresh button in your browser.

An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.

We apologise for any inconvenience.