Beta-5 Could not detect MySQL server version!

Quote from: mattcdavis1 at Nov 17, 2009, 10:04 AM

What’s the process for keeping up to date with latest SVN without doing a fresh install each time?

Basically, just run svn update. I have my /modx/ dir actually using the checkout.

If you need to do more, we’ll specify more instructions in the commit message - the 2 we usually do are:

* [LEXICON RELOAD REQUIRED] - which you can do by going to Lexicon Management, and clicking "Reload Core Entries from Base" on the bottom of the grid
* [REBUILD/UPGRADE REQUIRED] - if we put this, that means you need to run the transport.core.php script, and run setup/ again. This happens infrequently, but if you dont do it when the commit says to, you’ll find things may be broken.

Ok, I figured out how to do use the update function. When you refer to the "commit message," where does this show up? Will I see it in the update dialog box?

Quote from: mattcdavis1 at Nov 17, 2009, 11:02 AM

Ok, I figured out how to do use the update function. When you refer to the "commit message," where does this show up? Will I see it in the update dialog box?

Depends on your SVN client. You can always follow SVN commits here:

http://svn.modxcms.com/crucible/changelog/modx

This is NOT the modx’s issue, but the MySQL upgrade.

This is an old thread, but STILL working solution.
I just tried it.

Stop the webserver and copy the file libmysql.dll (it’s in MySQL’s /lib/opt directory) of MySQL 5.0.12 into the Windows\system32 directory. When you restart the webserver, the Client API should be 5.0.12 (that’s something I was also looking for quite a long time, but recently found the solution ;-)).

Markus

--
Markus Popp
Web Developer

Sun Microsystems Ges.m.b.H.
Wienerbergstraße 3/VII, 1100 Wien, Austria

Phone: +43 650 2328670
Email: [email protected]

Handelsgericht Wien, Firmenbuch-Nr. FN 186250 y