#50581 [NEW]: php.ini inconsitency
From: stevenmartin99 at gmail dot com Operating system: windows PHP version: 5.3SVN-2009-12-26 (snap) PHP Bug Type: Feature/Change Request Bug description: php.ini inconsitency Description: in the php.ini with php5.3.0 there is 6lines that are not consistant with the layout of the ini file these two line below have comments written on the same line.the stand is before them [967] => ;extension=php_oci8.dll ; Use with Oracle 10gR2 Instant Client [968] => ;extension=php_oci8_11g.dll ; Use with Oracle 11g Instant Client these line below have now whitespace after the ; as all comment lines have [1040] => ;PCRE library recursion limit. 1041] => ;Please note that if you set this value to a high number you may consume all [1042] => ;the available process stack and eventually crash PHP (due to reaching the [1043] => ;stack size limit imposed by the Operating System). Expected result: I am trying to make a php.ini gui interface and these lines are messing it up ..i presume its just a mistake in the php.ini thanks -- Edit bug report at http://bugs.php.net/?id=50581&edit=1 -- Try a snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=50581&r=trysnapshot52 Try a snapshot (PHP 5.3): http://bugs.php.net/fix.php?id=50581&r=trysnapshot53 Try a snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=50581&r=trysnapshot60 Fixed in SVN: http://bugs.php.net/fix.php?id=50581&r=fixed Fixed in SVN and need be documented: http://bugs.php.net/fix.php?id=50581&r=needdocs Fixed in release: http://bugs.php.net/fix.php?id=50581&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=50581&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=50581&r=needscript Try newer version: http://bugs.php.net/fix.php?id=50581&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=50581&r=support Expected behavior: http://bugs.php.net/fix.php?id=50581&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=50581&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=50581&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=50581&r=globals PHP 4 support discontinued: http://bugs.php.net/fix.php?id=50581&r=php4 Daylight Savings:http://bugs.php.net/fix.php?id=50581&r=dst IIS Stability: http://bugs.php.net/fix.php?id=50581&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=50581&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=50581&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=50581&r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=50581&r=mysqlcfg
Req #48082 [Com]: mysql_connect does not work with named pipes
Edit report at http://bugs.php.net/bug.php?id=48082&edit=1 ID: 48082 Comment by: stevenmartin99 at gmail dot com Reported by:andrew dot answer at gmail dot com Summary:mysql_connect does not work with named pipes Status: Closed Type: Feature/Change Request Package:MySQL related Operating System: win32 only - Windows XP PHP Version:5.3.0RC1 Assigned To:mysql Block user comment: N Private report: N New Comment: how many 5.3.x will there be? you can be serious carrying this issue on futher? iv extensivly tested this and php5.3.0 works php5.3.1 doesnt php5.3.2 doesnt php5.3.3 doesnt please fix in php5.3.4 - this is a huge issue as i see it. Previous Comments: [2010-09-28 15:50:58] peaceable_whale at hotmail dot com I do not agree that supporting named pipe is a new feature. Named pipe allows MySQL Server in Windows to operate without TCP/IP and the MySQL Client Library has been supporting it. mysqlnd should have been able to connect MySQL Server via named pipe since its intrduction. The patch just added the missing feature back. Since there is no timeframe for the next minor PHP version, it is quite unfair to ask those relying on named pipe to wait for that. Please add support to named pipe in 5.3.x. [2010-09-22 17:16:39] and...@php.net Support will be in the next minor PHP version, be it 5.4 or something else. 5.3.x won't get this, as this is classified as new feature. [2010-09-22 17:14:05] and...@php.net Automatic comment from SVN on behalf of andrey Revision: http://svn.php.net/viewvc/?view=revision&revision=303679 Log: Fix for Request #48082 mysql_connect does not work with named pipes [2010-08-20 12:24:54] and...@php.net A patch is being worked on [2010-05-18 20:31:05] dex_is_cool at loopmod dot com I can't get named pipes working. It _always_ falls back to TCP, and fails if it can't get TCP connection. Windows XP sp3 IIS 5.1 FastCGI php-5.3.2-nts-Win32-VC9-x86 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/bug.php?id=48082 -- Edit this bug report at http://bugs.php.net/bug.php?id=48082&edit=1
Req #48082 [Com]: mysql_connect does not work with named pipes
Edit report at http://bugs.php.net/bug.php?id=48082&edit=1 ID: 48082 Comment by: stevenmartin99 at gmail dot com Reported by:andrew dot answer at gmail dot com Summary:mysql_connect does not work with named pipes Status: Closed Type: Feature/Change Request Package:MySQL related Operating System: win32 only - Windows XP PHP Version:5.3.0RC1 Assigned To:mysql Block user comment: N Private report: N New Comment: SORRY forgot to mention the test i used. download WampServer2.0i with php5.3.0 (using http://localhost) test phpmyadmin - works install addon php5.3.1 -> test phpmyadmin - doesnt work (blank page) install addon php5.3.2 -> test phpmyadmin - doesnt work (blank page) install addon php5.3.3 -> test phpmyadmin - doesnt work (blank page) (mysql version never changed in test) - change the hosts file not to include ::1 localhost and then phpmyadmin works PS - This is not a solution in my eyes.. cant you just have it working until the mysql issue is fixed reading the hosts file? why carry this issue on longer? - Previous Comments: [2010-12-02 00:00:55] stevenmartin99 at gmail dot com how many 5.3.x will there be? you can be serious carrying this issue on futher? iv extensivly tested this and php5.3.0 works php5.3.1 doesnt php5.3.2 doesnt php5.3.3 doesnt please fix in php5.3.4 - this is a huge issue as i see it. [2010-09-28 15:50:58] peaceable_whale at hotmail dot com I do not agree that supporting named pipe is a new feature. Named pipe allows MySQL Server in Windows to operate without TCP/IP and the MySQL Client Library has been supporting it. mysqlnd should have been able to connect MySQL Server via named pipe since its intrduction. The patch just added the missing feature back. Since there is no timeframe for the next minor PHP version, it is quite unfair to ask those relying on named pipe to wait for that. Please add support to named pipe in 5.3.x. [2010-09-22 17:16:39] and...@php.net Support will be in the next minor PHP version, be it 5.4 or something else. 5.3.x won't get this, as this is classified as new feature. [2010-09-22 17:14:05] and...@php.net Automatic comment from SVN on behalf of andrey Revision: http://svn.php.net/viewvc/?view=revision&revision=303679 Log: Fix for Request #48082 mysql_connect does not work with named pipes [2010-08-20 12:24:54] and...@php.net A patch is being worked on 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/bug.php?id=48082 -- Edit this bug report at http://bugs.php.net/bug.php?id=48082&edit=1
[PHP-BUG] Req #54308 [NEW]: You named the new version 5.3.6 and not 5.4.0
From: Operating system: Windows PHP version: 5.3.6 Package: *General Issues Bug Type: Feature/Change Request Bug description:You named the new version 5.3.6 and not 5.4.0 Description: You have released the new version of php as PHP5.3.6 from PHP5.3.5 To a windows user this means a small security update... When in fact you have rendered every single Apache sever useless if they upgrade. How can this kind of update be in the n.n.X class of number versioning when if should be AT LEAST in the n.X.n Range. Telling people in a small note that you no longer support APACHE ON WINDOWS is not acceptable when you only change the version number by 0.0.1 Telling people to use an unoffical build of Apache when previously a PHP X.X.-1 compatiable official Build was ok is not Acceptable. You really need to think about this very carefully, 5.4.0 should have been released. Expected result: change the version number to PHP5.4.0 -- Edit bug report at http://bugs.php.net/bug.php?id=54308&edit=1 -- Try a snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=54308&r=trysnapshot52 Try a snapshot (PHP 5.3): http://bugs.php.net/fix.php?id=54308&r=trysnapshot53 Try a snapshot (trunk): http://bugs.php.net/fix.php?id=54308&r=trysnapshottrunk Fixed in SVN: http://bugs.php.net/fix.php?id=54308&r=fixed Fixed in SVN and need be documented: http://bugs.php.net/fix.php?id=54308&r=needdocs Fixed in release: http://bugs.php.net/fix.php?id=54308&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=54308&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=54308&r=needscript Try newer version: http://bugs.php.net/fix.php?id=54308&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=54308&r=support Expected behavior: http://bugs.php.net/fix.php?id=54308&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=54308&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=54308&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=54308&r=globals PHP 4 support discontinued: http://bugs.php.net/fix.php?id=54308&r=php4 Daylight Savings:http://bugs.php.net/fix.php?id=54308&r=dst IIS Stability: http://bugs.php.net/fix.php?id=54308&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=54308&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=54308&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=54308&r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=54308&r=mysqlcfg
Req #54308 [Com]: You named the new version 5.3.6 and not 5.4.0
Edit report at http://bugs.php.net/bug.php?id=54308&edit=1 ID: 54308 Comment by: stevenmartin99 at gmail dot com Reported by:stevenmartin99 at gmail dot com Summary:You named the new version 5.3.6 and not 5.4.0 Status: Bogus Type: Feature/Change Request Package:*General Issues Operating System: Windows PHP Version:5.3.6 Block user comment: N Private report: N New Comment: Sorry but this is not BOGUS.. Where else can this issue be brought up? Please provide a link to somewhere else or change the status back to open Previous Comments: [2011-03-18 13:03:53] paj...@php.net . [2011-03-18 12:57:26] stevenmartin99 at gmail dot com Description: You have released the new version of php as PHP5.3.6 from PHP5.3.5 To a windows user this means a small security update... When in fact you have rendered every single Apache sever useless if they upgrade. How can this kind of update be in the n.n.X class of number versioning when if should be AT LEAST in the n.X.n Range. Telling people in a small note that you no longer support APACHE ON WINDOWS is not acceptable when you only change the version number by 0.0.1 Telling people to use an unoffical build of Apache when previously a PHP X.X.-1 compatiable official Build was ok is not Acceptable. You really need to think about this very carefully, 5.4.0 should have been released. Expected result: change the version number to PHP5.4.0 -- Edit this bug report at http://bugs.php.net/bug.php?id=54308&edit=1
Req #54308 [Com]: You named the new version 5.3.6 and not 5.4.0
Edit report at http://bugs.php.net/bug.php?id=54308&edit=1 ID: 54308 Comment by: stevenmartin99 at gmail dot com Reported by:stevenmartin99 at gmail dot com Summary:You named the new version 5.3.6 and not 5.4.0 Status: Bogus Type: Feature/Change Request Package:*General Issues Operating System: Windows PHP Version:5.3.6 Block user comment: N Private report: N New Comment: I did mention this...Its not Offical. Who is ApacheLounge? Who is Steffen Land? You are now making the Security of People Servers rest on one person by telling everyone , to be secure use the latest PHP version but you must use it with an unoffical version of Apache built by one person.. (Doesnt sound so secure to me) Please reopen open my issue as you failed to understand it correctly. This was not my bug issue you replied about. My issue is with the number versioning to let people know of the SERIOUS UPDATE. You changed the numbering by 0.0.1 which people will see as a security update.. When in fact they will be creating an extremly unstable Server if you update PHP to 5.3.6. And if you follow PHP'S recommendation by using ApacheLounges(Steffen Land) VC9 Apache build you are saying this is safe. Previous Comments: [2011-03-18 13:19:44] der...@php.net We support Apache on Windows just fine. Just not with the antiquated Visual Studio 6 builds that apache.org provides. You can use Apache from ApacheLounge just fine. [2011-03-18 13:13:26] stevenmartin99 at gmail dot com Sorry but this is not BOGUS.. Where else can this issue be brought up? Please provide a link to somewhere else or change the status back to open [2011-03-18 13:03:53] paj...@php.net . [2011-03-18 12:57:26] stevenmartin99 at gmail dot com Description: You have released the new version of php as PHP5.3.6 from PHP5.3.5 To a windows user this means a small security update... When in fact you have rendered every single Apache sever useless if they upgrade. How can this kind of update be in the n.n.X class of number versioning when if should be AT LEAST in the n.X.n Range. Telling people in a small note that you no longer support APACHE ON WINDOWS is not acceptable when you only change the version number by 0.0.1 Telling people to use an unoffical build of Apache when previously a PHP X.X.-1 compatiable official Build was ok is not Acceptable. You really need to think about this very carefully, 5.4.0 should have been released. Expected result: change the version number to PHP5.4.0 -- Edit this bug report at http://bugs.php.net/bug.php?id=54308&edit=1
