Failed update to Beta 4, now 3.8.4 has bugs.
 

I had someone that I help with a vbulletin install try to go to beta without backing up the database. :( We just moved to a new server so haven't done a new backup myself, as I had the old server until just recently.

Anyway, there were problems and we are getting a few errors. Vbulletin is saying a reinstall, but there seems to have to be another way, since we can see all the posts and everything.

Looking for some options and ideas if anyone has any.

Here is what we are getting in the admin panel initial screen. All the other pages within it work. Below is when trying to edit large posts or go to some of them. The site is zefron.com/forum

Here is what we are getting in large threads or when we edit large threads

I'd ask this 1st, why are you trying to run a BETA version on a live production site?

It's called a BETA for a reason.

If the columns are missing, i would view the upgrade php files starting with the one after your old version 3.8.4, view each php upgrade script from that point on in a editor and search for those keywords, see what queries were supposed to be run and compare them to your db, most likely 1/2 of the upgrade queries weren't ran.

They did it without my knowledge. I wondered the same thing :)

What you describes seems above what I know how to do. I was just posting tonsee if there was something that could save the site. I didn't know if anyone would mind trying to try this if people think this would work. Thanks!

There is no reason it can't be saved, the errors appear to be simply missing columns in the table.

I assume you also inspected the currently upload php files and they are all for the beta version and not for 3.8.4?

Did you check the two tables above and confirm that those tables don't actually exist?

They might have put the vB4 files on the server, but they didn't run the upgrade.php file because you can see the database has not been upgraded at all (it says 3.8.4).

They ran the upgrade then went back to 3.8.4. Would that be why?

What exactly do you mean by "then went back to 3.8.4" ?

She said she tried the upgrade and it failed so ran the 3.8.4 install again.

You can't do that. The database won't suddenly downgrade to 3.8.4 again. Either she ran the upgrade and the database was changed, or she didn't run it and the database was left as a 3.8.4 database. Or, and I'm not sure about this, she started to run it and only some of the database was changed except the version number was not yet changed.

Snakes 1100 is going to take a look at it. Thanks for all the ideas. We'll post results here, for future problems with others.