ID: 41350 Comment by: chris at crgs dot co dot uk Reported By: graham at directhostinguk dot com Status: Assigned Bug Type: MySQL related Operating System: Windows 2003 PHP Version: 5.2.2 Assigned To: georg New Comment:
Re short_open_tag option I have tested on my server with short_open_tag set to both 'on' and 'off' and get this problem whatever happens with PHP 5.2.3. The error occurs even with this page: <?php phpinfo(); ?> Previous Comments: ------------------------------------------------------------------------ [2007-06-18 19:33:57] curthenderson at hotmail dot com I have found that this error will come up if you are using short php opening tags <? and do not have that option turned on in your php.ini. ------------------------------------------------------------------------ [2007-06-15 04:19:50] louis at steelbytes dot com see http://bugs.mysql.com/bug.php?id=25621 for mysql bug report on same prob ------------------------------------------------------------------------ [2007-06-12 16:31:54] chris at crgs dot co dot uk Still a problem on PHP 5.2.3 under Windows Server 2003 / IIS 6 / MySQL 5.0.41. Can be fixed by copying libmysql.dll from PHP 5.2.1. Seems as if neither side wants to take ownership of the bug. MySQL people seem to say it's a PHP issue (see http://bugs.mysql.com/bug.php?id=25621), but not much seems to be happening here. Can someone please fix this bug before the next release of PHP? ------------------------------------------------------------------------ [2007-05-31 08:15:58] louis at steelbytes dot com repro on win2k3. reverting libmysql.dll to 5.2.1 fixes it. ------------------------------------------------------------------------ [2007-05-29 17:04:40] php at stock-consulting dot com I receive the message as well, when running PHP 5.2.2 from the command line, so definitely no IIS-related issue. The php_mysql.dll is loaded as an extension, but no functions from the library are called by the application, so most likely no MySQL issue. The message appeared after the PHP version update; no MySQL update was performed. A clear indication, IMHO, the something went wrong on the PHP side. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/41350 -- Edit this bug report at http://bugs.php.net/?id=41350&edit=1
