1 austriaco Jan 30, 2008 14:39
3 austriaco Feb 05, 2008 22:35
Haven't upgraded yet. But as soon as I do, I'll report.
4 austriaco Feb 07, 2008 10:39
I've just upgraded to 2.4.0-RC1. The debugging bug still persists.
5 austriaco Feb 07, 2008 10:49
Additional info: My MySQL server is version 4.1.22 and TRADITIONAL mode was implemented in version 5.0.2:
The following special modes are provided as shorthand for combinations of mode values from the preceding list. All are available in MySQL 5.0 beginning with version 5.0.0, except for TRADITIONAL, which was implemented in MySQL 5.0.2.
So, we now know the source of the error. The solution would be to test versions before attempting to set sql_mode, but I don't know if that mode is required later. I'll leave it here to the experts to decide.
6 afwas Feb 07, 2008 11:51
/inc/_core/model/db/_db.class.php lines 414-417:
if( $debug )
{ // Force MySQL strict mode
$this->query( 'SET sql_mode = "TRADITIONAL"' );
}
If you want to change something, that's up to you ;)
Good luck
7 austriaco Feb 20, 2008 14:25
Well I did it and can now debug. I'm running 2.4.0rc2.
One thing I noted, tough, is that XML-RPC calls are not show in detail anymore. en 1.9.x I used to see the full XML sent when pinging services or sending trackbacks, that kind of stuff. Not anymore. IS this controled by any configuration variable I'm unaware of?
8 blueyed Mar 13, 2008 15:25
$debug_xmlrpc_logging (in conf/_advanced.php) should do the trick.
Have you been able to duplicate this in 2.4.0-RC1?
* Yeah a bug that shows up in debug mode only is funny :lol: