[PHP-DOC] #37486 [Opn]: Docs do not reflect E_STRICT warning
ID: 37486 Updated by: [EMAIL PROTECTED] Reported By: brianm-phpbugs at dealnews dot com Status: Open Bug Type: Documentation problem Operating System: Linux PHP Version: Irrelevant New Comment: We need a script to check all of php-src (and PECL) for what functions may emits errors, and document accordingly. E_STRICT and E_WARNING especially. In fact, it should check return types too. And compare prototypes. Sounds like a large task so we can simply add E_STRICT info to strftime() for now :) Previous Comments: [2006-05-18 04:00:11] brianm-phpbugs at dealnews dot com Description: Enabling E_STRICT and using strtotime() yields this error: Strict Standards: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /www/dev.phorum/phorum5-dev/include/format_functions.php on line 157 However, the docs at http://us3.php.net/function.strftime/ make no mention of this. I believe if you are going to throw warnings for things in E_STRICT, it should at least be documented. Reproduce code: --- use strtotime() without setting a timezone in php.ini Expected result: Documentation would have headed this warning. Actual result: -- No docs about this being a possible problem. -- Edit this bug report at http://bugs.php.net/?id=37486&edit=1
[PHP-DOC] cvs: phpdoc /en/reference/memcache ini.xml reference.xml
miklThu May 18 05:38:16 2006 UTC Added files: /phpdoc/en/reference/memcache ini.xml Modified files: /phpdoc/en/reference/memcache reference.xml Log: Added documentation of INI directives http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/memcache/reference.xml?r1=1.7&r2=1.8&diff_format=u Index: phpdoc/en/reference/memcache/reference.xml diff -u phpdoc/en/reference/memcache/reference.xml:1.7 phpdoc/en/reference/memcache/reference.xml:1.8 --- phpdoc/en/reference/memcache/reference.xml:1.7 Fri Dec 23 16:17:38 2005 +++ phpdoc/en/reference/memcache/reference.xml Thu May 18 05:38:15 2006 @@ -1,5 +1,5 @@ - + @@ -34,12 +34,7 @@ &reference.memcache.configure; - &reference.memcache.constants; - - -&reftitle.runtime; -&no.config; - + &reference.memcache.ini; &reftitle.resources; @@ -49,6 +44,8 @@ + &reference.memcache.constants; + &reftitle.examples; http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/memcache/ini.xml?view=markup&rev=1.1 Index: phpdoc/en/reference/memcache/ini.xml +++ phpdoc/en/reference/memcache/ini.xml &reftitle.runtime; &extension.runtime; Memcache Configuration Options Name Default Changeable Changelog memcache.allow_failover "1" PHP_INI_ALL Available since Memcache 2.0.2 memcache.chunk_size "8192" PHP_INI_ALL Available since Memcache 2.0.2 memcache.default_port "11211" PHP_INI_ALL Available since Memcache 2.0.2 &ini.php.constants; &ini.descriptions.title; memcache.allow_failover boolean Whether to transparently failover to other servers on errors. memcache.chunk_size integer Data will be transfered in chunks of this size, setting the value lower requires more network writes. Try increasing this value to 32768 if noticing otherwise inexplicable slowdowns. memcache.default_port string The default TCP port number to use when connecting to the memcached server if no other port is specified.
[PHP-DOC] #37486 [NEW]: Docs do not reflect E_STRICT warning
From: brianm-phpbugs at dealnews dot com Operating system: Linux PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Docs do not reflect E_STRICT warning Description: Enabling E_STRICT and using strtotime() yields this error: Strict Standards: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /www/dev.phorum/phorum5-dev/include/format_functions.php on line 157 However, the docs at http://us3.php.net/function.strftime/ make no mention of this. I believe if you are going to throw warnings for things in E_STRICT, it should at least be documented. Reproduce code: --- use strtotime() without setting a timezone in php.ini Expected result: Documentation would have headed this warning. Actual result: -- No docs about this being a possible problem. -- Edit bug report at http://bugs.php.net/?id=37486&edit=1 -- Try a CVS snapshot (PHP 4.4): http://bugs.php.net/fix.php?id=37486&r=trysnapshot44 Try a CVS snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=37486&r=trysnapshot52 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=37486&r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=37486&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=37486&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=37486&r=needtrace Need Reproduce Script:http://bugs.php.net/fix.php?id=37486&r=needscript Try newer version:http://bugs.php.net/fix.php?id=37486&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=37486&r=support Expected behavior:http://bugs.php.net/fix.php?id=37486&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=37486&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=37486&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=37486&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=37486&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=37486&r=dst IIS Stability:http://bugs.php.net/fix.php?id=37486&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=37486&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=37486&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=37486&r=nozend MySQL Configuration Error:http://bugs.php.net/fix.php?id=37486&r=mysqlcfg
[PHP-DOC] #37343 [Opn]: Apache 2.2.X vs 2.0.X docs
ID: 37343 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type:Documentation problem PHP Version: Irrelevant New Comment: Added this temp fix/note to the Windows apache2.xml: Users of Apache 2.2.x may use the documentation below except the appropriate DLL files are instead named php4apache2_2.dll and php5apache2_2.dll. These exist in the PHP distribution as of PHP 5.2.0. See also snaps.php.net. Previous Comments: [2006-05-07 00:36:13] [EMAIL PROTECTED] Description: Currently we document Apache 2.0.X for both Linux and Windows. Apache 2.2.X is out now and there are some differences, and our docs need an update. Windows: phpXapache2.dll will not work with 2.2.X but as of PHP 5.2.0 phpXapache2_2.dll will exist for this. See bug #37338 for details. Linux: Unsure. The main question here is do the docs need additional Apache2 sections or should we change our 2.0.X title to 2.X.X and include some 2.2.X specific notes within. We'll need to research differences and decide if they're worthy of a new section. I'm guessing not but am unsure at this point. -- Edit this bug report at http://bugs.php.net/?id=37343&edit=1
[PHP-DOC] cvs: phpdoc /en/install/windows apache2.xml
philip Thu May 18 03:29:11 2006 UTC Modified files: /phpdoc/en/install/windows apache2.xml Log: A temp fix for bug #37343, info for Apache 2.2.x users. http://cvs.php.net/viewcvs.cgi/phpdoc/en/install/windows/apache2.xml?r1=1.13&r2=1.14&diff_format=u Index: phpdoc/en/install/windows/apache2.xml diff -u phpdoc/en/install/windows/apache2.xml:1.13 phpdoc/en/install/windows/apache2.xml:1.14 --- phpdoc/en/install/windows/apache2.xml:1.13 Wed Jul 27 14:35:59 2005 +++ phpdoc/en/install/windows/apache2.xml Thu May 18 03:29:11 2006 @@ -1,5 +1,5 @@ - + Apache 2.0.x on Microsoft Windows @@ -14,6 +14,15 @@ installation steps first! + + + Users of Apache 2.2.x may use the documentation below except the + appropriate DLL files are instead named php4apache2_2.dll + and php5apache2_2.dll. These exist in the PHP + distribution as of PHP 5.2.0. + See also &url.php.snapshots; + + &warn.apache2.compat;
[PHP-DOC] #35755 [Opn->Asn]: the document of session_module_name() is incomplete
ID: 35755
Updated by: [EMAIL PROTECTED]
Reported By: songchao1234 at yeah dot net
-Status: Open
+Status: Assigned
Bug Type: Documentation problem
Operating System: redhat 7.3
PHP Version: Irrelevant
Assigned To: ramsey
Previous Comments:
[2006-05-16 15:45:44] [EMAIL PROTECTED]
session_module_name("mm") doesn't work because you don't have the mm
libs compiled into PHP. I'll add documentation on each of the session
modules and what PHP requires to use mm.
[2005-12-21 03:16:01] songchao1234 at yeah dot net
Description:
session_module_name() needs some examples for its document,
Bug #5121 said that it has been fixed , but actually it is not
Reproduce code:
---
Expected result:
mm
Actual result:
--
Fatal error: session_module_name(): Cannot find named PHP session
module (mm)
--
Edit this bug report at http://bugs.php.net/?id=35755&edit=1
[PHP-DOC] #37484 [Opn->Asn]: Need a more clearer documenation on session's save_handler w/ shared memory.
ID: 37484
Updated by: [EMAIL PROTECTED]
Reported By: scott at abcoa dot com
-Status: Open
+Status: Assigned
Bug Type:Documentation problem
PHP Version: Irrelevant
Assigned To: ramsey
Previous Comments:
[2006-05-18 01:28:18] [EMAIL PROTECTED]
See bug #35755. I'm going to take on the task of updating the session
docs to describe the different storage modules and how PHP needs to be
configured in order to use the "mm" module.
[2006-05-17 21:49:26] scott at abcoa dot com
HOw come there are two related documentation on session. See one at
http://www.php.net/manual/en/ref.session.php
[2006-05-17 21:32:39] scott at abcoa dot com
Description:
Documentation's URL: http://www.php.net/manual/en/ref.session.php
Problem: Some confusion and hard to read on the use of "mm" or shared
memory. I discovered that there are 3 options which are "files", "mm"
and "users" to be used with the sessions.save_handler but the
documentation didn't mentioned that. I had spend quite some time
looking for more information that would shed some lights about those.
Solution: Update the
--snip--
session.save_handler string
session.save_handler defines the name of the handler which is used
for storing and retrieving data associated with a session. Defaults to
files. See also session_set_save_handler().
--snip--
section to include the 3 options and explain the purpose of the 3
options. Example of it can be found at
http://www.zend.com/zend/tut/session.php#storage . Good example would
be
--snip--
Storage Modules
To read and save session data, PHP uses storage modules, thus
abstracting the back end of the library. There are currently three
storage modules available:
* Files. By default, PHP uses the files module to save the session
data to disk. It creates a text file named after the session ID in
/tmp. You probably won't ever need to access this file directly. In the
example of the session counter, the content of this file would look like
this, which is a serialized representation of the variable:
counter|i:4;
* mm. If you need higher performance, the mm module is a viable
alternative; it stores the data in shared memory and is therefore not
limited by the hardware I/O system.
* User. Used internally to realize user-level callback functions
that you define with session_set_save_handler().
The real power lies in the capacity to specify user callbacks as
storage modules. Because you can write your functions to handle
sessions while still being able to rely on the standardized PHP API,
you can store sessions wherever and however you want: in a database
like MySQL, XML files, on a remote FTP server (an FTP server is
unlikely, but you get the idea).
The function session_set_save_handler() takes six strings as arguments,
which must be your callback functions.
The syntax of the function is as follows:
void session_set_save_handler(string open, string close, string read,
string write, string destroy, string gc);
Tip
To leave out one argument, pass an empty string ("") to
session_set_save_handler().
--snip--
We would also need to explain that session_set_save_handler() that
contain up to 6 arguements are not the same things as setting the
session.save_handler that is either 1 of the 3 following options,
"files", "mm", and "users". Another confusion here...
Might be a good idea to mention that compiling with the shared memory
module may be needed for "mm" option to work as specified in the
"Installation" section of this php.net's session documentation.
--
Edit this bug report at http://bugs.php.net/?id=37484&edit=1
[PHP-DOC] #37484 [Opn]: Need a more clearer documenation on session's save_handler w/ shared memory.
ID: 37484
Updated by: [EMAIL PROTECTED]
Reported By: scott at abcoa dot com
Status: Open
Bug Type:Documentation problem
PHP Version: Irrelevant
-Assigned To:
+Assigned To: ramsey
New Comment:
See bug #35755. I'm going to take on the task of updating the session
docs to describe the different storage modules and how PHP needs to be
configured in order to use the "mm" module.
Previous Comments:
[2006-05-17 21:49:26] scott at abcoa dot com
HOw come there are two related documentation on session. See one at
http://www.php.net/manual/en/ref.session.php
[2006-05-17 21:32:39] scott at abcoa dot com
Description:
Documentation's URL: http://www.php.net/manual/en/ref.session.php
Problem: Some confusion and hard to read on the use of "mm" or shared
memory. I discovered that there are 3 options which are "files", "mm"
and "users" to be used with the sessions.save_handler but the
documentation didn't mentioned that. I had spend quite some time
looking for more information that would shed some lights about those.
Solution: Update the
--snip--
session.save_handler string
session.save_handler defines the name of the handler which is used
for storing and retrieving data associated with a session. Defaults to
files. See also session_set_save_handler().
--snip--
section to include the 3 options and explain the purpose of the 3
options. Example of it can be found at
http://www.zend.com/zend/tut/session.php#storage . Good example would
be
--snip--
Storage Modules
To read and save session data, PHP uses storage modules, thus
abstracting the back end of the library. There are currently three
storage modules available:
* Files. By default, PHP uses the files module to save the session
data to disk. It creates a text file named after the session ID in
/tmp. You probably won't ever need to access this file directly. In the
example of the session counter, the content of this file would look like
this, which is a serialized representation of the variable:
counter|i:4;
* mm. If you need higher performance, the mm module is a viable
alternative; it stores the data in shared memory and is therefore not
limited by the hardware I/O system.
* User. Used internally to realize user-level callback functions
that you define with session_set_save_handler().
The real power lies in the capacity to specify user callbacks as
storage modules. Because you can write your functions to handle
sessions while still being able to rely on the standardized PHP API,
you can store sessions wherever and however you want: in a database
like MySQL, XML files, on a remote FTP server (an FTP server is
unlikely, but you get the idea).
The function session_set_save_handler() takes six strings as arguments,
which must be your callback functions.
The syntax of the function is as follows:
void session_set_save_handler(string open, string close, string read,
string write, string destroy, string gc);
Tip
To leave out one argument, pass an empty string ("") to
session_set_save_handler().
--snip--
We would also need to explain that session_set_save_handler() that
contain up to 6 arguements are not the same things as setting the
session.save_handler that is either 1 of the 3 following options,
"files", "mm", and "users". Another confusion here...
Might be a good idea to mention that compiling with the shared memory
module may be needed for "mm" option to work as specified in the
"Installation" section of this php.net's session documentation.
--
Edit this bug report at http://bugs.php.net/?id=37484&edit=1
[PHP-DOC] #37484 [Opn]: Need a more clearer documenation on session's save_handler w/ shared memory.
ID: 37484
User updated by: scott at abcoa dot com
Reported By: scott at abcoa dot com
Status: Open
Bug Type:Documentation problem
PHP Version: Irrelevant
New Comment:
HOw come there are two related documentation on session. See one at
http://www.php.net/manual/en/ref.session.php
Previous Comments:
[2006-05-17 21:32:39] scott at abcoa dot com
Description:
Documentation's URL: http://www.php.net/manual/en/ref.session.php
Problem: Some confusion and hard to read on the use of "mm" or shared
memory. I discovered that there are 3 options which are "files", "mm"
and "users" to be used with the sessions.save_handler but the
documentation didn't mentioned that. I had spend quite some time
looking for more information that would shed some lights about those.
Solution: Update the
--snip--
session.save_handler string
session.save_handler defines the name of the handler which is used
for storing and retrieving data associated with a session. Defaults to
files. See also session_set_save_handler().
--snip--
section to include the 3 options and explain the purpose of the 3
options. Example of it can be found at
http://www.zend.com/zend/tut/session.php#storage . Good example would
be
--snip--
Storage Modules
To read and save session data, PHP uses storage modules, thus
abstracting the back end of the library. There are currently three
storage modules available:
* Files. By default, PHP uses the files module to save the session
data to disk. It creates a text file named after the session ID in
/tmp. You probably won't ever need to access this file directly. In the
example of the session counter, the content of this file would look like
this, which is a serialized representation of the variable:
counter|i:4;
* mm. If you need higher performance, the mm module is a viable
alternative; it stores the data in shared memory and is therefore not
limited by the hardware I/O system.
* User. Used internally to realize user-level callback functions
that you define with session_set_save_handler().
The real power lies in the capacity to specify user callbacks as
storage modules. Because you can write your functions to handle
sessions while still being able to rely on the standardized PHP API,
you can store sessions wherever and however you want: in a database
like MySQL, XML files, on a remote FTP server (an FTP server is
unlikely, but you get the idea).
The function session_set_save_handler() takes six strings as arguments,
which must be your callback functions.
The syntax of the function is as follows:
void session_set_save_handler(string open, string close, string read,
string write, string destroy, string gc);
Tip
To leave out one argument, pass an empty string ("") to
session_set_save_handler().
--snip--
We would also need to explain that session_set_save_handler() that
contain up to 6 arguements are not the same things as setting the
session.save_handler that is either 1 of the 3 following options,
"files", "mm", and "users". Another confusion here...
Might be a good idea to mention that compiling with the shared memory
module may be needed for "mm" option to work as specified in the
"Installation" section of this php.net's session documentation.
--
Edit this bug report at http://bugs.php.net/?id=37484&edit=1
[PHP-DOC] #37484 [NEW]: Need a more clearer documenation on session's save_handler w/ shared memory.
From: scott at abcoa dot com
Operating system:
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Need a more clearer documenation on session's save_handler w/
shared memory.
Description:
Documentation's URL: http://www.php.net/manual/en/ref.session.php
Problem: Some confusion and hard to read on the use of "mm" or shared
memory. I discovered that there are 3 options which are "files", "mm" and
"users" to be used with the sessions.save_handler but the documentation
didn't mentioned that. I had spend quite some time looking for more
information that would shed some lights about those.
Solution: Update the
--snip--
session.save_handler string
session.save_handler defines the name of the handler which is used for
storing and retrieving data associated with a session. Defaults to files.
See also session_set_save_handler().
--snip--
section to include the 3 options and explain the purpose of the 3 options.
Example of it can be found at
http://www.zend.com/zend/tut/session.php#storage . Good example would be
--snip--
Storage Modules
To read and save session data, PHP uses storage modules, thus abstracting
the back end of the library. There are currently three storage modules
available:
* Files. By default, PHP uses the files module to save the session
data to disk. It creates a text file named after the session ID in /tmp.
You probably won't ever need to access this file directly. In the example
of the session counter, the content of this file would look like this,
which is a serialized representation of the variable: counter|i:4;
* mm. If you need higher performance, the mm module is a viable
alternative; it stores the data in shared memory and is therefore not
limited by the hardware I/O system.
* User. Used internally to realize user-level callback functions that
you define with session_set_save_handler().
The real power lies in the capacity to specify user callbacks as storage
modules. Because you can write your functions to handle sessions while
still being able to rely on the standardized PHP API, you can store
sessions wherever and however you want: in a database like MySQL, XML
files, on a remote FTP server (an FTP server is unlikely, but you get the
idea).
The function session_set_save_handler() takes six strings as arguments,
which must be your callback functions.
The syntax of the function is as follows:
void session_set_save_handler(string open, string close, string read,
string write, string destroy, string gc);
Tip
To leave out one argument, pass an empty string ("") to
session_set_save_handler().
--snip--
We would also need to explain that session_set_save_handler() that contain
up to 6 arguements are not the same things as setting the
session.save_handler that is either 1 of the 3 following options, "files",
"mm", and "users". Another confusion here...
Might be a good idea to mention that compiling with the shared memory
module may be needed for "mm" option to work as specified in the
"Installation" section of this php.net's session documentation.
--
Edit bug report at http://bugs.php.net/?id=37484&edit=1
--
Try a CVS snapshot (PHP 4.4):
http://bugs.php.net/fix.php?id=37484&r=trysnapshot44
Try a CVS snapshot (PHP 5.2):
http://bugs.php.net/fix.php?id=37484&r=trysnapshot52
Try a CVS snapshot (PHP 6.0):
http://bugs.php.net/fix.php?id=37484&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=37484&r=fixedcvs
Fixed in release:
http://bugs.php.net/fix.php?id=37484&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=37484&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=37484&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=37484&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=37484&r=support
Expected behavior:http://bugs.php.net/fix.php?id=37484&r=notwrong
Not enough info:
http://bugs.php.net/fix.php?id=37484&r=notenoughinfo
Submitted twice:
http://bugs.php.net/fix.php?id=37484&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=37484&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=37484&r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=37484&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=37484&r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=37484&r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=37484&r=float
No Zend Extensions: http://bugs.php.net/fix.php?id=37484&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=37484&r=mysqlcfg
[PHP-DOC] cvs: phpdoc /en/reference/outcontrol/functions ob-get-length.xml
nlopess Wed May 17 19:45:49 2006 UTC Modified files: /phpdoc/en/reference/outcontrol/functions ob-get-length.xml Log: fix example title (user note) http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/outcontrol/functions/ob-get-length.xml?r1=1.4&r2=1.5&diff_format=u Index: phpdoc/en/reference/outcontrol/functions/ob-get-length.xml diff -u phpdoc/en/reference/outcontrol/functions/ob-get-length.xml:1.4 phpdoc/en/reference/outcontrol/functions/ob-get-length.xml:1.5 --- phpdoc/en/reference/outcontrol/functions/ob-get-length.xml:1.4 Tue Dec 27 21:12:53 2005 +++ phpdoc/en/reference/outcontrol/functions/ob-get-length.xml Wed May 17 19:45:49 2006 @@ -1,5 +1,5 @@ - + @@ -20,7 +20,7 @@ - A simple ob_get_contents example + A simple ob_get_length example
[PHP-DOC] #37473 [NEW]: MacOS X documentation update
From: [EMAIL PROTECTED] Operating system: Mac OS X PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: MacOS X documentation update Description: The Mac OS X install section of the manual is outdated. Some considerations: 1. Precompiled packages It appears darwinports is the most up-to-date resource for this, with fink being another common resource. entropy.ch offers a popular build with excellent information too but using a popular command such as 'port' seems more documentation worthy. We could link to all three with emphasis on darwinports. Also, these docs should never link to a specific file as they do currently (libphp4.so.gz), these docs should be generic in nature. 2. Compiling it The documentation should provide information for users wanting to compile PHP themselves as currently this information does not exist within the 'MacOS X Client' docs. There are some user comments that look helpful for this, and if needed we could also ask a few "mac experts" out there for helpful tips/info for making this process work, and mention common problems that could come about. 3. The "provided by Marc Liyanage" can be removed, we do not write author information in the manual. Whoever updates these docs will be rewriting them anyways... -- Edit bug report at http://bugs.php.net/?id=37473&edit=1 -- Try a CVS snapshot (PHP 4.4): http://bugs.php.net/fix.php?id=37473&r=trysnapshot44 Try a CVS snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=37473&r=trysnapshot52 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=37473&r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=37473&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=37473&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=37473&r=needtrace Need Reproduce Script:http://bugs.php.net/fix.php?id=37473&r=needscript Try newer version:http://bugs.php.net/fix.php?id=37473&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=37473&r=support Expected behavior:http://bugs.php.net/fix.php?id=37473&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=37473&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=37473&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=37473&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=37473&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=37473&r=dst IIS Stability:http://bugs.php.net/fix.php?id=37473&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=37473&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=37473&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=37473&r=nozend MySQL Configuration Error:http://bugs.php.net/fix.php?id=37473&r=mysqlcfg
