SERVER ISSUES UPDATE 5-1-23

[Kestryll]

I've been chasing these oddities we've been having ever since the server move and frankly I ran out of things to try.

I reached out to vBulletin staff and I think we have the answer.

Most if not all of the issues are related to the database and that seems to be where the problem is. Our old server ran an older version of MySQL which worked with vB 3.8.11. When we moved I knew the later versions of PHP were going to be a problem so I paid to have our server temporarily set up with a legacy version of PHP. I hadn't realized nor considered that the later version of MySQL would have it's own problems. Every reported bug I'd seen had been related to PHP versions.

Apparently in MySQL 8.0.x certain words were reclassified as 'reserved'. Since they were not classed as such in the earlier version this is causing problems on the forum since the new server is running 8.0.32.

So, there are two options to address this, one really because the other is incredibly impractical.
The first would be to go through the database finding each and every usage of these words and encase them in backticks, this is the insanely impractical option.
The second is to update the forum to vB 5.7.4. The 5.7.x series of softwares has coding in it to account for these reserved words.

In the very near future I will be contracting with vBulletin to have them handle the update from 3.8.11 to 5.7.4 since it's such a significant leap in versions. If something goes wrong they can figure it out since it's their coding.

Unfortunately this means there will be some 'losses'. The Blog hasn't been supported as an add on in years so we will likely lose whatever blog posts have been made.
iTrader is old enough to buy alcohol and has been unsupported long enough to vote. I doubt it will work but I'll try to reinstall it after the update.
I suspect there will be a few other things that will have to be looked at for compatibility as well. We'll find out after the vB engineers look at the install.

We'll probably be down for a couple of days from what I've read, hopefully less but it all depends on how we arrange the chicken bones and feathers and how good vB's voodoo is.

Once I have an idea on the dates I'll post them up.

[Rorge Retson]

Makes sense, thanks for the update.

Really unhappy if iTrader doesn't get moved. Now that the IRS is for sure implementing reporting for $600 or more by 3rd party payment platforms, it is more important than ever to have marketplaces where transactions can happen easily. iTrader ratings are an excellent system for evaluating the reliability and legitimacy of prospective buyers and sellers. It would be a great loss if it went away.

[the_tunaman]

Thanks for the update Kes, for all that you and the gang are doing, and best of luck with the update!

[Bralowe]

Appreciate all the work!

[FJ40 CRUZR]

Thanks for all the hard work…

[sealocan]

Thank you Kestryll for this update and all the work you're putting into the move on top of your normal everyday stuff.

Even if you can't save every aspect of the i-trader rating system, with all of its comments and it's ability to link to the post of the deal that was rated, I think the most important thing would be keeping everyone's current I-trader positive, neutrals and negatives total score.

Then maybe establish a new type of similar rating system if the old one has gone beyond it's usable age.

I'll also say that you don't have to rush or feel pressured. The systems seem (to me) to be working good enough for us to get by in the meantime.

Thanks again!

[LBDamned]

Am I overly cynical to translate 'a couple days' to a couple of weeks?...

Under promise and over deliver... I'm planning on a week. That's the optimist in me

[SilveradoColt21]

Thanks for all of the hard work Kes! This is the update on things that we had all been waiting for, glad to see things are slowly and possibly getting fixed soon!

[joefrank64k]

Please save iTrader, or at least post our ?legacy? scores/ratings going forward, if possible.

iTrader has saved me so much grief.

[Sydwaiz]

I better not lose my join date!

Seriously though, thanks for all the hard work and headaches you've put into it.

[SWalt]

Thanks Kes!

[FatCity67]

Let us know when it's go time to start sacrificing virgins.

By sacrificing I mean partying.

By virgins I mean females 18+.

[Http404]

Just rip the band-aid off and get it upgraded and then keep current on releases.

[Empaque]

Thank you for the hard work! It's nice to know there is light at the end of the tunnel.

[rdfact]

So, there are two options to address this, one really because the other is incredibly impractical.
The first would be to go through the database finding each and every usage of these words and encase them in backticks, this is the insanely impractical option.

Kes, I work with Microsoft SQL but MySQL has a lot of similarities. Doing a find/replace on the entire database should not be that big of an issue. I have done this when customers want to recode part numbers, customers/vendors, GL accounts etc.