Revolution install - mysql 5.0.51a

Hi,

I am trying to get the new beta 5 of revolution to install.

I have a vps.net server and have set it up with ubuntu 8.04 and initaly this comes with mysql 5.0.51, which modx displays as being incompatible due to bugs in the version when I run the setup.

So I found this

http://www.vps.net/forum/public-forums/tutorials-and-how-tos/1430-use-dotdeb-packages-for-php-and-mysql-etc

post which discusses upgrading php and mysql to newer versions.

I have run through the guide and seem to have everything setup and mysql has upgraded to 5.1.4 but as the guide describes, although mysql has been upgraded the mysql-client version number is not updated when checking though phpinfo.

The problem this causes is that although I am now running a version of mysql that should be compatible, because it reports it incorectly I can;t get past that stage of the install/setup.

Is there any way to disable this check so I can get to the next stage of the setup?

thanks

J

This likely means that php was improperly compiled against the 5.0.51 mysql libraries instead of the new ones.

thanks for the quick reply.

After re reading the post I linked to I had assumed what they were suggesting is that although mysql 5.1 is installed with all the functionality of 5.1 php just displays it as being the old version.

"some quirks from this though

in order to prevent against segfaults with apache the php5-mysql module has been compiled against the old mysql libraries this means that php will report your mysql client as 5.0.51a where it is actually 5.1.41 (at time of writing) this shouldnt cause any problems and i have only seen so far that phpmyadmin complains but doesnt have any problems."


are you suggesting that it looks like I have not managed to get mysql updated to 5.1?

I have been using modx for quite a few years and am always really happy with the 0.9.6 version I have installed and am keen to get a revolutions setup running but as of yet have not managed to get it installed.

Does anybody know if any of the linux distros that are available on vps.net can be used or updated to be used for modx revolution?

thanks

J

I understand this may not work but would really like to give it ago and at least see if it does or doesn;t work and be able to report it baack here if this is a dead end or not.

What I need to be able to do is turn off the mysql dependicies on the install. Does anyone know if this is possible and if so how its done?

thanks

J

MySQL 5.0.51 in any flavor will not work.

Quote from: jayzee808 at Jan 23, 2010, 01:49 PM

in order to prevent against segfaults with apache the php5-mysql module has been compiled against the old mysql libraries this means that php will report your mysql client as 5.0.51a where it is actually 5.1.41 (at time of writing) this shouldnt cause any problems and i have only seen so far that phpmyadmin complains but doesnt have any problems."

Who told you or where did you read this? Compiling against the proper mysql libraries is critical for a proper PHP/MySQL deployment and I’ve never heard of preventing Apache segfaults by running an older client API in PHP against a newer server. In fact, that typically causes problems in my experience, especially when PDO is being used (a la xPDO/MODx Revolution).

You can disable the MySQL client checks in the setup... see the function _checkMySQLClientVersion() in setup/includes/modinstalltest.class.php.

My host use mysql 5.0.51a as well and i can’t upgrade to Revo’s unless i disable the client check as you mentioned.

Now, my host said that they are using the MYSQL version from their Debian distrib and that it should be patched with backport of bugfixes from more newer version of the client if the Debian team judge them necessary.

How can i check if the necessary patches are applied on the shared server?

I also have a webhost that claims to use the debian stable packages >:(

It’s ludicrous to me that reputable hosting providers cannot keep up with the recent releases of MySQL (or PHP for that matter). This excuse of using the latest stable packages from some repository just means they are dependent on others to do their work. There are important bug fixes in these software releases and the fact that these folks are still calling 5.0.51 a stable package (originally released in November 2007) over two years after it’s release is nothing more than willful ignorance.

That said, if everyone wants this check taken out for those that really do have 5.0.51 with back ports of fixes from other releases (which is chaotic IMO), we can do that, and you can take the risk that if you do really have 5.0.51, queries will return incorrect results in some fairly ordinary cases. We’ll just turn it into a warning.