Edit report at http://bugs.php.net/bug.php?id=49476&edit=1
ID: 49476 Updated by: tony2...@php.net Reported by: elmu at gmx dot de Summary: $_ENV does not work -Status: Open +Status: Feedback Type: Bug Package: Variables related Operating System: Windows PHP Version: 6SVN-2009-09-05 (snap) New Comment: Please try using this snapshot: http://snaps.php.net/php-trunk-latest.tar.gz For Windows: http://windows.php.net/snapshots/ Previous Comments: ------------------------------------------------------------------------ [2009-09-22 21:19:57] elmue at gmx dot de Hello In version 22 sep 2009 it is even worse: print_r($_FILES); throws: Failed to decode _FILES array The last time I tested on PHP6 this did work. Now its broken. ------------------------------------------------------------------------ [2009-09-22 21:03:52] elmue at gmx dot de I repeated the test on build from 22 sep 2009 and the result is the same $_ENV["OS"] $_ENV["PROCESSOR_IDENTIFIER"] $_ENV["COMPUTERNAME"] are empty. Even a print_r($_ENV) shows: Array ( ) This cannot be caused by input encoding because these variables have no special characters in them. On PHP5 the same array has plenty content! ------------------------------------------------------------------------ [2009-09-06 20:31:59] paj...@php.net ENV works just fine here. But there are changes about input encoding that have not been test at all. And all in all, the current status of php6 is not tested at all, unstable and needs heavy work to get to something usable (usable != stable). ------------------------------------------------------------------------ [2009-09-06 19:48:16] elmu at gmx dot de Note: It seems that the current PHP 6 has not yet been tested on Windows. All the bugs I found are related to filesystem or operation system. ------------------------------------------------------------------------ [2009-09-05 23:57:06] elmu at gmx dot de Sorry I wanted to say $_SERVER["SERVER_SIGNATURE"] works on both. ------------------------------------------------------------------------ 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=49476 -- Edit this bug report at http://bugs.php.net/bug.php?id=49476&edit=1
