ERROR: WordPress 2.7 requires MySQL 4.0.0 or higher

I checked the Database, MySQL 3.23.58 is running…

So, yes, no 4.0.0.0 but what’s the best thing I should do now?

Regards,
Ellen

wow – I can’t believe a host still has that old of mysql

I think you could go as high as 2.0.11 (that is still a supported and secure version as far as I know) with that old of a db

get on your host about upgrading – how can you have a secure wordpress if your host is not?

Wooo!!
Ask your web host to upgrade the service(Mysql) or the best advice is to change the hosting provider

hi

i have a similar problem while installing a wordpress blog version 2.7.

i am getting an error in installation step2 as “ERROR: WordPress 2.7 requires MySQL 4.0.0 or higher“.

i have checked my hosting company mysql version by running phpinfo().
i have founded the Client api version is 4.1.11

even though my version is 4.1.11 i am getting the above error while installing wordpress.

can you help me on this issue.

Regards,
Padmaja

OK, everybody, have a good laugh, but then please give me a point in an alternate direction.

I have a client which is a university department. Their webserver IS their ONLY option for hosting, and that webserver only allows db connections to the Uni dbase server, which runs mysql 3.23. Yes, I know. Yes, I know that, too. Uh-huh. Yep. Laugh it up. Those policies are all in the name of “security”, too, which adds to the comedy.

I developed the client’s CMS using WP 2.0.11, and cosntantly have to grab functions, javascripts, etc from WP2.7 and do some occasional custom scripting in order to get things working for them. Sometimes I rip code from XOOPS to do things that WP hadn’t implemented in 2.0. Imagine that for a moment. Needless to say, upgrade notices from WP Grand Central are ignored.

Spare me the glib “get another provider” “advice”. This is not an option for this client. Is a genuine professional-grade technical discussion of why the later version of MySQL is required? Are there specific 4.0+ features involved?

I’m considering switching the entire darn thing to XOOPs, but I really love WP. It’s beginning to seem to be less work to hack the install scripts to run 2.7 on 3.23 rather than continue the constant coding to enable plugin workarounds.

XOOPS I don’t love so much but that option looks sweeter all the time. One reason it’s so popular overseas is precisely b/c folks in less technically-fortunate countries often have to deal with legacy systems, and cannot mess with a system like WP where their decisions are made for them. “Upgrade yer provider, dude” is not an option.

I have other clients running WP 2.7.1 b/c they have modern hosts. But in this one case, the client is shelling out $20k a year, most of which is to pay me to constantly custom-code stuff like lightbox-2/templates/pagemash/etc which don’t want to work on the old WP. (wp_enqueue workarounds, anyone?) There is no way the Uni is going to upgrade their dbase in the forseeable future. I need the account, but I’d rather spend their budget making the site cooler instead of just getting basic stuff to work.

What’s a fella to do? Any suggestions? Anyone else chopping into the install script to work around the Micro$oftesque forced “wisdom” of the WP developers?

Curious to hear the thoughts out there.

Spare me the glib “get another provider” “advice”. This is not an option for this client. Is a genuine professional-grade technical discussion of why the later version of MySQL is required? Are there specific 4.0+ features involved?

It’s not glib when someone is presenting it straight up.

What’s a fella to do? Any suggestions? Anyone else chopping into the install script to work around the Micro$oftesque forced “wisdom” of the WP developers?

Nice Microsoft reference, for their “wisdom” you ought to ask WP for your money back (I kid, and Jan now sips more coffee. Honestly, that was a joke).

That’s a lot of work you’re doing and pulling in XOOPS code… wow.

Abstract answer is this: if you can’t meet the WordPress requirements, then either run something else or get the University (you or someone else) to review and modify the current version of WordPress to work with MySQL <4.0.

As you know already that’s not a trivial task and good luck with that. Getting the university to run a new or multiple versions of MySQL probably is easier, but you’ve said that’s not an option.

Good luck.