Don’t know as yet, will be grabbing the new XAMPP with the latest versions later tonight and after install, I’ll have a better idea what to tweak and where.
It would seem removing STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION from the sql_mode fixes all the issues, or atleast the ones I found.
It also works on my wordpress.
PHP = 5.0.5 apache2handler
Server = Apache/2.0.54 (Win32) PHP/5.0.5
Database = mysql 5.0.13-rc-nt-max
Yeah works fine with me.
You need to disable Strict Mode in MySQL 5. If you have already installed MySQL 5 goto Start–>MySQL–>Server Config Wizard. Follow through the detailed config steps and deselect ‘Enable Strict Mode’.
I’m getting the similar error
WordPress database error: [Out of range value adjusted for column ‘user_Id’ at row 1]
I tried deselecting ‘Enable Strict Mode’, not working. 🙁
Anymore suggestions?
I disabled strict, and still get this error on the homepage (though I get no errors on install):
WordPress database error: [Unknown column ‘publish’ in ‘where clause’]
SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND post_date_gmt <= ‘2005-12-09 14:33:59’ AND (post_status = “publish” OR post_author = 1 AND post_status != ‘draft’ AND post_status != ‘static’) GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 0, 10
Any ideas?
This might be a gentler solution to disabling strict for the entire MySQL5 server, which might not be appropriate in all situations …
http://wordpress.org/support/topic/48940#post-283862
I can’t get WordPress to connect to the database using WP v2.0.2, MySQL 5.0.19-nt, PHP 5.1.2, and Apache 2.0.55.
I get the wordpress error page “Error establishing a database connection” when trying to run the install script.
I can connect to the wordpress database using the exact username and pw from the config through the mysql command line client and through a test script using the mysqli functions:
$mysqli = new mysqli('localhost','wordpress','wordpress');
$mysqli->select_db('wordpress');
$result = $mysqli->query("SELECT * FROM mytest");
I have also tried disabling mysql strict mode with no effect.
I don’t see any errors in the apache 2 error log.
Any suggestions?