Re: [PHP-DOC] cvs: phpdoc /php copyright.php getting-started.phpinstall.hpux.php install.linux.php install.macosx.php install.openbsd.phpinstall.solaris.php install.unix.php install.windows.php installa

2002-10-03 Thread Derick Rethans

Hello,

what are you doing here? Putting HTML files into the repository really 
makes no sense. Please revert this.

Derick


On Fri, 4 Oct 2002, Wei-ching Kao wrote:

> coldocean Fri Oct  4 03:17:05 2002 EDT
> 
>   Added files: 
> /phpdoc/php   copyright.php getting-started.php install.hpux.php 
>   install.linux.php install.macosx.php 
>   install.openbsd.php install.solaris.php 
>   install.unix.php install.windows.php installation.php 
>   intro-whatcando.php introduction.php preface.php 
>   tutorial.firstpage.php tutorial.forms.php 
>   tutorial.oldcode.php tutorial.php tutorial.useful.php 
>   tutorial.whatsnext.php 
>   Log:
>   
>   
>   

--

---
 Derick Rethans   http://derickrethans.nl/ 
 JDI Media Solutions
--[ if you hold a unix shell to your ear, do you hear the c? ]-


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] #17069 [Opn->Csd]: Session & register_globals

2002-10-03 Thread iliaa

 ID:   17069
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
-Status:   Open
+Status:   Closed
 Bug Type: Documentation problem
 Operating System: Windows 2000
 PHP Version:  4.1.2
 New Comment:

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:


[2002-08-23 08:04:52] [EMAIL PROTECTED]

I'm wondering if this is actually still true. Can anyone confirm this?



[2002-05-30 06:46:21] [EMAIL PROTECTED]

It's a mis-assumption that session_register()ing a global variable
put's it into $_SESSION in the same request. 

Sessions never behaved this way.

The documentation should be clearer on this, reclassifying.



[2002-05-07 05:57:46] [EMAIL PROTECTED]

This code don't work properly:


Reload


If register_globals is On, reload will increment counter. 

If register_globals is Off, session will "read_only" like. 
It create session file with zero length. Any write not occurs. 
session_encode() returns a empty string;






-- 
Edit this bug report at http://bugs.php.net/?id=17069&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] #17122 [Ver->Csd]: Values set in _SESSION doesn't stick

2002-10-03 Thread jmcastagnetto

 ID:   17122
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
-Status:   Verified
+Status:   Closed
 Bug Type: Documentation problem
 Operating System: Linux RH 7.2
 PHP Version:  4.2.0
 New Comment:

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

Added comment on the limitations for variable names in the
documentation.


Previous Comments:


[2002-09-30 09:23:41] [EMAIL PROTECTED]

I've been having a similar problem for over a week. Tried everything I
could think of.  Script looked like this:

variable={$HTTP_SESSION_VARS['AVAR']}";
?>

Seemed everyone else could get it to work except for a friend and I.
I'm using IE 6.0.28, he's using Netscape 4.04.
I was able to correct the problem by doing the following while running
IE6.0.28:

a) Select Tools/Internet Options
b) Select Privacy Tab
c) Click on Advanced button
d) Check Override Automatic Cookie Handling
e) Check Always allow session cookies

After doing this - everything worked fine - even the test scripts above
(except for the variable 4).

I then went back and unchecked the Override Automatic Cookie Handling -
assuming that this would return me back to a state where AVAR would not
increment.  Much to my chagrin, it continued to work.  This leads me to
believe that there's a registry setting somewhere that controls this
behavior.  Now, to find out what it is and how to check for it on a
user's machine from within PHP.



[2002-07-08 09:35:24] [EMAIL PROTECTED]

This test case I posted is with register_global turned off.  Well, the
documentation should stated that the number can not be used as the
first character.  I wonder how can anyone tell the difference on
$_SESSION from an array?  It look a lot like an array in some way.



[2002-07-05 15:50:47] [EMAIL PROTECTED]

As session variables are subject to be registered as global variables
(if register_globals is on), and identifier names (including variable
names) cannot begin with a numeric character, it's not too hard to see
that session variables should not begin with a number. Basically
session variables
should follow naming ruiles for identifiers IMHO.



[2002-07-05 15:46:23] [EMAIL PROTECTED]

Whoop!  One more thing!  $_SESSION[CUSTOMER_ID] does work on page 1
also!  Didn't include that as Example #3 on page 1.



[2002-07-05 15:43:30] [EMAIL PROTECTED]

I struggled with the $_SESSION problem for almost a week.  When I read
this report, that is when reality hit me.  In the comment written by
"[EMAIL PROTECTED]" saying that I'm not suppose to use the numberic value.
 I'm using PHP 4.2.1 and AIX 4.3.3.  Here's the example that work which
should not have work at all.  See the "//This one work!! (Numberic
Value)".

Why do I have to spend almost a week struggling over it?  I read many
documentation about $_SESSION vs. session_register() with the
register_global turned off, but they say nothing about the numeric
value that aren't allowed to be used?

Thanks,
 FletchSOD

--clip--
//---Page 1-
define(CUSTOMER_ID,0);
define(CUSTOMER_NAME,1);
define(STREET,4);
define(CITY,5);
define(STATE,6);
define(ZIP_CODE,7);

$salt = strtoupper(md5(uniqid(rand(;
session_id($salt);
session_start();

//$result is from odbc_exec
odbc_fetch_into($result,$_SESSION,1);

//Example #1
print_r($_SESSION);   //This one work!! (Numeric Value)

//Example #2
echo $_SESSION[0];  //This one work also! (Numberic Value)

header("Location: https://www.whatever.com/page2.php";);
//---Page 2-
session_start();

print_r($_SESSION);  //This one does not work!
--clip--



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/17122

-- 
Edit this bug report at http://bugs.php.net/?id=17122&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] cvs: phpdoc /en/reference/session reference.xml

2002-10-03 Thread Jesus M. Castagnetto

jmcastagnetto   Thu Oct  3 23:05:09 2002 EDT

  Modified files:  
/phpdoc/en/reference/sessionreference.xml 
  Log:
  Adding text to explaing bug #17122 on session variable names
  
  
Index: phpdoc/en/reference/session/reference.xml
diff -u phpdoc/en/reference/session/reference.xml:1.15 
phpdoc/en/reference/session/reference.xml:1.16
--- phpdoc/en/reference/session/reference.xml:1.15  Thu Oct  3 04:02:03 2002
+++ phpdoc/en/reference/session/reference.xml   Thu Oct  3 23:05:09 2002
@@ -1,5 +1,5 @@
 
-
+
  
   Session handling functions
   Sessions
@@ -119,6 +119,14 @@
   has been changed to use $_SESSION everywhere. You can
   substitute $HTTP_SESSION_VARS for
   $_SESSION, if you prefer the former.
+ 
+ 
+  The keys in the $_SESSION associative
+  array are subject to the
+  same limitations as regular variable names in PHP, i.e. they cannot
+  start with a number and must start with a letter or underscore.
+  For more details see the section on
+  variables in this manual.
  
 
 



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] #19699 [Opn]: 'array_walk()' violates recommended 'allow_call_time_pass_reference=Off'

2002-10-03 Thread sniper

 ID:   19699
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Open
 Bug Type: Documentation problem
 Operating System: Windows
-PHP Version:  4.2.3
+PHP Version:  4.2.3,4.3.0-dev
 New Comment:

updated version information.



Previous Comments:


[2002-10-03 16:27:08] [EMAIL PROTECTED]

OK.

Manual is incorrect here, in PHP4 functions either specify if an arg is
passed by ref or by value. In array_walk only the first argument is
ever passed by reference. I can see that passing userdata by reference
would be nice but unfortuantly it is too much of a big change that
could break too many scripts to make as this point as people may be
relying on the fact it is passed by reference.

For example

function my_function($value, $key, $userdata)
{
 $userdata = strrev($userdata.$key.$value);
}

$array1 = array("one", "two", "three")l
$mydata = "array1";
array_walk($array1, 'my_function', $mydata);

This POOR example would not work with thrid parameter passed by ref so
for now am changing this to a documentation problem as the
documentation is currently slightly misleading in it advocates using
calltime pass by reference when infact the first param only is ever
passed by reference.

- James



[2002-10-03 15:50:01] [EMAIL PROTECTED]

I tried using the latest snapshot for Windows:

   System Windows 9x localhost 4.10  
   Build Date Oct 3 2002 20:15:03  

but I still encounter the same problems.



[2002-10-01 18:51:35] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip



[2002-10-01 17:38:45] [EMAIL PROTECTED]

The PHP manual contains the following note about 'array_walk()':

   Note: 
   If func needs to be working with the actual values of the array,
specify 
that the first parameter of func should be passed by reference. Then
any 
changes made to those elements will be made in the array itself. 

So if you want to let 'array_walk()' pass the third parameter by
reference, 
you're inclined to specify that the third parameter of func should be
passed by 
reference.  In the example underneath, the notation '&$userData' is
used to 
specify so:

   function PrepareBowl($value, $key, &$userData) {
 print 'Mixed so far... ' . ($userData .= "$value ") . "\n";
   }
 
   $ingredients = array('peach', 'cherry', 'alchohol');
   $bowl = '';
   array_walk($ingredients, 'PrepareBowl', $bowl);
   print "Bowl: $bowl";

This doesn't work however; '$assembly' will not be passed by reference
and the 
output will be an empty 'bowl':

   Mixed so far... peach 
   Mixed so far... peach cherry 
   Mixed so far... peach cherry alchohol 
   Bowl: 

Only when you use the '&' notation within 'array_walk()' to specify
that the 
third parameter should be passed by reference:

   array_walk($ingredients, 'PrepareBowl', &$bowl);

the output will be as expected:

   Mixed so far... peach 
   Mixed so far... peach cherry 
   Mixed so far... peach cherry alchohol 
   Bowl: peach cherry alchohol 

but, using the recommended php.ini setting
'allow_call_time_pass_reference=Off',
you'll receive the warning:

   Warning: Call-time pass-by-reference has been deprecated - argument
passed by value; If you would like to pass it by reference, modify the

declaration of array_walk(). If you would like to enable call-time 
pass-by-reference, you can set allow_call_time_pass_reference to true
in 
your INI file. However, future versions may not support this any
longer.

This looks the same like bug 4116
(http://bugs.php.net/bug.php?id=4116), posted Apr 12, 2000.  Although
this bug is closed with a reply that it works like the 
replier think it should work, this doesn't seem logic to me because the
first 
parameter *is* passed by reference without specifying; try:

   array_walk(array('peach', 'cherry', 'alchohol'), 'PrepareBowl',
&$bowl);

and you'll receive:

   Fatal error: Only variables can be passed by reference ...

Furthermore, I can't see much use of passing a third variable to
'array_walk()'
by value, modify it by passing it to func by reference ... without
receiving 
back the modified variable.

Would it be a suggestion to let 'array_walk()' receive the third
parameter by 
reference if specified so in the receiving func?  This would be in line
with
the behaviour of the first parameter to func.


Freddy Vulto




-- 
Edit this bug report at http://bugs.php.net

[PHP-DOC] #19742 [Opn]: [chm] bug on ref.domxml.html

2002-10-03 Thread sniper

 ID:   19742
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Open
-Bug Type: DOM XML related
+Bug Type: Documentation problem
 Operating System: windows
 PHP Version:  4.2.1
 New Comment:

reclassified


Previous Comments:


[2002-10-03 15:37:02] [EMAIL PROTECTED]

Well, I am reading bugs of how to get the different objects and
components of an xml document, and I have got a simply and fine
solution that is like follow,
");
$dom_tree = domxml_xmltree( $my_xml_file[0] );
echo "DOMTREE loaded";
print("");
print_r( $dom_tree );
print("");
echo "\n";
?>
The best of it, you do not need the whole path to read the file and you
get the whole description of your DOM.

This is my "books.xml" file,
La
pesteAlbert
Camus30
where the tree is listed in one only line.

And here is what I get with the above php code,

DOMTREE loaded

DomDocument Object
(
[name] => #document
[url] => 
[version] => 1.0
[encoding] => UTF-8
[standalone] => -1
[type] => 9
[compression] => -1
[charset] => 1
[0] => 1
[1] => 8040992
[children] => Array
(
[0] => DomElement Object
(
[type] => 1
[tagname] => books
[0] => 2
[1] => 8040880
[children] => Array
(
[0] => DomElement Object
(
[type] => 1
[tagname] => book
[0] => 3
[1] => 8040784
[children] => Array
(
[0] => DomElement Object
(
[type] => 1
[tagname] => Title
[0] => 4
[1] => 8040688
[children] =>
Array
(
[0] =>
DomText Object
(
   
[type] => 3
   
[name] => #text
   
[content] => La peste
[0]
=> 5
[1]
=> 8040608
)

)

)

[1] => DomElement Object
(
[type] => 1
[tagname] =>
Author
[0] => 6
[1] => 8040512
[children] =>
Array
(
[0] =>
DomText Object
(
   
[type] => 3
   
[name] => #text
   
[content] => Albert Camus
[0]
=> 7
[1]
=> 8048576
)

)

)

[2] => DomElement Object
(
[type] => 1
[tagname] => Price
[0] => 8
[1] => 8048512
[children] =>
Array
(
   

[PHP-DOC] #19743 [NEW]: Addition to the Documentation

2002-10-03 Thread wyvern

From: [EMAIL PROTECTED]
Operating system: --
PHP version:  4.2.3
PHP Bug Type: Documentation problem
Bug description:  Addition to the Documentation

I program service scripts in PHP designed to be portable to other systems
running PHP.  And while the same code works on my own site, a few people
have reported some really gnarly errors when trying to run the code on
their own sites.  Since I can't access their sites to see what the problem
is, and I can only try and figure it out from the error messages they send
me...
 
A list of error messages PHP returns, along with general descriptions as
to what might have caused them would be invaluable for me.  I could also
direct people there if their queries were simple enough.
 
Brian
-- 
Edit bug report at http://bugs.php.net/?id=19743&edit=1
-- 
Try a CVS snapshot: http://bugs.php.net/fix.php?id=19743&r=trysnapshot
Fixed in CVS:   http://bugs.php.net/fix.php?id=19743&r=fixedcvs
Fixed in release:   http://bugs.php.net/fix.php?id=19743&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=19743&r=needtrace
Try newer version:  http://bugs.php.net/fix.php?id=19743&r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=19743&r=support
Expected behavior:  http://bugs.php.net/fix.php?id=19743&r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=19743&r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=19743&r=submittedtwice
register_globals:   http://bugs.php.net/fix.php?id=19743&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=19743&r=php3
Daylight Savings:   http://bugs.php.net/fix.php?id=19743&r=dst


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] #19699 [Opn]: 'array_walk()' violates recommended 'allow_call_time_pass_reference=Off'

2002-10-03 Thread jmoore

 ID:   19699
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Open
-Bug Type: Arrays related
+Bug Type: Documentation problem
 Operating System: Windows
 PHP Version:  4.2.3
 New Comment:

OK.

Manual is incorrect here, in PHP4 functions either specify if an arg is
passed by ref or by value. In array_walk only the first argument is
ever passed by reference. I can see that passing userdata by reference
would be nice but unfortuantly it is too much of a big change that
could break too many scripts to make as this point as people may be
relying on the fact it is passed by reference.

For example

function my_function($value, $key, $userdata)
{
 $userdata = strrev($userdata.$key.$value);
}

$array1 = array("one", "two", "three")l
$mydata = "array1";
array_walk($array1, 'my_function', $mydata);

This POOR example would not work with thrid parameter passed by ref so
for now am changing this to a documentation problem as the
documentation is currently slightly misleading in it advocates using
calltime pass by reference when infact the first param only is ever
passed by reference.

- James


Previous Comments:


[2002-10-03 15:50:01] [EMAIL PROTECTED]

I tried using the latest snapshot for Windows:

   System Windows 9x localhost 4.10  
   Build Date Oct 3 2002 20:15:03  

but I still encounter the same problems.



[2002-10-01 18:51:35] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip



[2002-10-01 17:38:45] [EMAIL PROTECTED]

The PHP manual contains the following note about 'array_walk()':

   Note: 
   If func needs to be working with the actual values of the array,
specify 
that the first parameter of func should be passed by reference. Then
any 
changes made to those elements will be made in the array itself. 

So if you want to let 'array_walk()' pass the third parameter by
reference, 
you're inclined to specify that the third parameter of func should be
passed by 
reference.  In the example underneath, the notation '&$userData' is
used to 
specify so:

   function PrepareBowl($value, $key, &$userData) {
 print 'Mixed so far... ' . ($userData .= "$value ") . "\n";
   }
 
   $ingredients = array('peach', 'cherry', 'alchohol');
   $bowl = '';
   array_walk($ingredients, 'PrepareBowl', $bowl);
   print "Bowl: $bowl";

This doesn't work however; '$assembly' will not be passed by reference
and the 
output will be an empty 'bowl':

   Mixed so far... peach 
   Mixed so far... peach cherry 
   Mixed so far... peach cherry alchohol 
   Bowl: 

Only when you use the '&' notation within 'array_walk()' to specify
that the 
third parameter should be passed by reference:

   array_walk($ingredients, 'PrepareBowl', &$bowl);

the output will be as expected:

   Mixed so far... peach 
   Mixed so far... peach cherry 
   Mixed so far... peach cherry alchohol 
   Bowl: peach cherry alchohol 

but, using the recommended php.ini setting
'allow_call_time_pass_reference=Off',
you'll receive the warning:

   Warning: Call-time pass-by-reference has been deprecated - argument
passed by value; If you would like to pass it by reference, modify the

declaration of array_walk(). If you would like to enable call-time 
pass-by-reference, you can set allow_call_time_pass_reference to true
in 
your INI file. However, future versions may not support this any
longer.

This looks the same like bug 4116
(http://bugs.php.net/bug.php?id=4116), posted Apr 12, 2000.  Although
this bug is closed with a reply that it works like the 
replier think it should work, this doesn't seem logic to me because the
first 
parameter *is* passed by reference without specifying; try:

   array_walk(array('peach', 'cherry', 'alchohol'), 'PrepareBowl',
&$bowl);

and you'll receive:

   Fatal error: Only variables can be passed by reference ...

Furthermore, I can't see much use of passing a third variable to
'array_walk()'
by value, modify it by passing it to func by reference ... without
receiving 
back the modified variable.

Would it be a suggestion to let 'array_walk()' receive the third
parameter by 
reference if specified so in the receiving func?  This would be in line
with
the behaviour of the first parameter to func.


Freddy Vulto




-- 
Edit this bug report at http://bugs.php.net/?id=19699&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] ini-seetings

2002-10-03 Thread Friedhelm Betz


[...]

>> >> Where should error and logging config options go to, to errorfunc?
>> 
>> > Features / error handling ?
>> 
>> Ok, this would imply to link them from refernce/errorfunc.

> Doh, reverting my last suggection, put them to reference/errorfunc.

Done :-)

> As discussed before, if we go on with the multilevel reference TOC
> (see phpdoc/rfc/manual.xml.in), things like features/persistent
> connections will go to the database level in the TOC. Error handling
> description can already be moved to reference/errorfunc IMHO. It's
> definitely like an intro in other parts, like the XML or session parts.
> We don't have a features/session part, because this text is in the session
> functions intro, and so should the features go to their relevant part.
> As far as I can remember, we already discussed this ;)

I can't remember...;-)

I have the time to move/integrate features/error-handling to
reference/errorfunc. I took a look at RFC/manual.xml.in:
 
  &Features;
  &features.error-handling;

...
  
Here it is still under features.
Is it ok to integrate the features/error-handling in
referenc/errorfunc?

 Friedhelm   



 Friedhelm   


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] cvs: phpdoc /en/appendices tokens.xml

2002-10-03 Thread Sander Roobol

sander  Thu Oct  3 15:00:34 2002 EDT

  Modified files:  
/phpdoc/en/appendices   tokens.xml 
  Log:
  Typos
  
  
Index: phpdoc/en/appendices/tokens.xml
diff -u phpdoc/en/appendices/tokens.xml:1.6 phpdoc/en/appendices/tokens.xml:1.7
--- phpdoc/en/appendices/tokens.xml:1.6 Wed Aug 14 19:10:56 2002
+++ phpdoc/en/appendices/tokens.xml Thu Oct  3 15:00:33 2002
@@ -1,5 +1,5 @@
 
-
+
 
 
  List of Parser Tokens
@@ -9,7 +9,7 @@
   "Parse error: unexpected T_SR, expecting ',' or ';' in script.php on line 
10."
  
  
-  You're supposed to know that T_SR means. For everybody who doesn't 
+  You're supposed to know what T_SR means. For everybody who doesn't 
   know that, here is a table with those identifiers, PHP-syntax and 
   references to the appropriate places in the manual.
  
@@ -68,7 +68,7 @@
 
 
  T_BREAK
- break;
+ break
  break
 
 



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] Error List...

2002-10-03 Thread Philip Olson

This appears to be a feature request to expand 
the documention found here:

  http://www.php.net/manual/en/tokens.php

Ideas?

Regards,
Philip Olson


On Thu, 3 Oct 2002, Gabor Hojtsy wrote:

> Please add this as a documentation bug at http://bugs.php.net/
> 
> Goba
>   - Original Message - 
>   From: Brian Huisman 
>   To: [EMAIL PROTECTED] 
>   Sent: Thursday, October 03, 2002 11:02 AM
>   Subject: [PHP-DOC] Error List...
> 
> 
>   I don't know if you have one already, but a list of all the error messages PHP 
>generates would be useful.
>
>   I program service scripts in PHP designed to be portable to other systems running 
>PHP.  And while the same code works on my own site, a few people have reported some 
>really gnarly errors when trying to run the code on their own sites.  Since I can't 
>access their sites to see what the problem is, and I can only try and figure it out 
>from the error messages they send me...
>
>   A list of error messages PHP returns, along with general descriptions as to what 
>might have caused them would be invaluable for me.  I could also direct people there 
>if their queries were simple enough.
>
>   Do you already have such a page?
>
>   Brian
> 


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DOC] Error List...

2002-10-03 Thread Gabor Hojtsy



Please add this as a documentation bug at http://bugs.php.net/
 
Goba

  - Original Message - 
  From: 
  Brian 
  Huisman 
  To: [EMAIL PROTECTED] 
  Sent: Thursday, October 03, 2002 11:02 
  AM
  Subject: [PHP-DOC] Error List...
  
  I don't know if you have one already, but a list 
  of all the error messages PHP generates would be useful.
   
  I program service scripts in PHP designed to be 
  portable to other systems running PHP.  And while the same code works on 
  my own site, a few people have reported some really gnarly errors when trying 
  to run the code on their own sites.  Since I can't access their sites to 
  see what the problem is, and I can only try and figure it out from the error 
  messages they send me...
   
  A list of error messages PHP returns, along with 
  general descriptions as to what might have caused them would be invaluable for 
  me.  I could also direct people there if their queries were simple 
  enough.
   
  Do you already have such a page?
   
  Brian


[PHP-DOC] Error List...

2002-10-03 Thread Brian Huisman



I don't know if you have one already, but a list of 
all the error messages PHP generates would be useful.
 
I program service scripts in PHP designed to be 
portable to other systems running PHP.  And while the same code works on my 
own site, a few people have reported some really gnarly errors when trying to 
run the code on their own sites.  Since I can't access their sites to see 
what the problem is, and I can only try and figure it out from the error 
messages they send me...
 
A list of error messages PHP returns, along with 
general descriptions as to what might have caused them would be invaluable for 
me.  I could also direct people there if their queries were simple 
enough.
 
Do you already have such a page?
 
Brian


[PHP-DOC] #19423 [Opn->Csd]: Problem with extension_dir in PHP.ini

2002-10-03 Thread k . schroeder

 ID:   19423
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
-Status:   Open
+Status:   Closed
 Bug Type: Documentation problem
 Operating System: Windows 9x/NT/ME/2000/XP
 PHP Version:  4.2.3


Previous Comments:


[2002-09-27 12:34:01] [EMAIL PROTECTED]

Should be mentioned in the manuel...

Derick



[2002-09-27 10:03:23] [EMAIL PROTECTED]

I had the same problem, after some hours of struggeling, I finanaly got
it 

This doesn't work : extension_dir=c:\php

This works :  extension_dir=c:\php\

It doesn't matter what dircotry the extension_dir is pointing to, you
must put the last '\' there to make it work.

Good luck all :)



[2002-09-25 13:20:53] [EMAIL PROTECTED]

Is the assumption that if no directory is specified, that it will
automaticlly look in the c:\WINNT\System32 directory for the extension
dlls, correct?



[2002-09-24 17:36:30] [EMAIL PROTECTED]

I'm using the ISAPI version on Win2k IIS.

My install drive for php is I:\php\

My php.ini is in the H:\winnt\ directory (the phpinfo() function
reports that is were it found it).

Php.ini coding :

; Directory in which the loadable extensions (modules) reside.
extension_dir = I:/php/extensions/


As long as I don't specify a extension to load, php works fine. But,
once I un remark an extension (ei. php_mssql.dll), it gives the "unable
to load dynamic library 'I:/php/extensions/php_mssql.dll' The support
module not found" message.

I've tried both ways, I:\\ and I:/



[2002-09-24 17:10:49] [EMAIL PROTECTED]

No php.ini does not have to be on the c: drive. 

However please make sure you are using the c:\\ or c:/ syntax. Also
make sure that your php.ini file is in the correct location (look at
the output of phpinfo()). With the cli and cgi versions you can often
get away with putting the php.ini file in the same dir as the
executable and it will find it there.

- James



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/19423

-- 
Edit this bug report at http://bugs.php.net/?id=19423&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] cvs: phpdoc /en/chapters install.windows.xml

2002-10-03 Thread Kai Schröder

k.schroeder Thu Oct  3 06:04:10 2002 EDT

  Modified files:  
/phpdoc/en/chapters install.windows.xml 
  Log:
  #19423: Problem with extension_dir in PHP.ini 
  
  
Index: phpdoc/en/chapters/install.windows.xml
diff -u phpdoc/en/chapters/install.windows.xml:1.18 
phpdoc/en/chapters/install.windows.xml:1.19
--- phpdoc/en/chapters/install.windows.xml:1.18 Mon Aug 12 22:45:13 2002
+++ phpdoc/en/chapters/install.windows.xml  Thu Oct  3 06:04:10 2002
@@ -1,5 +1,5 @@
 
-
+
   
Installation on Windows systems

@@ -252,8 +252,9 @@
   
You will need to change the 'extension_dir' setting to
point to your php-install-dir, or where you have placed
-   your php_*.dll files. ex:
-   c:\php\extensions
+   your php_*.dll files. Please do not
+   forget the last backslash. ex:
+   c:\php\extensions\
   
  
  



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] cvs: phpdoc /en/reference/session reference.xml

2002-10-03 Thread Sascha Schumann

sas Thu Oct  3 04:02:04 2002 EDT

  Modified files:  
/phpdoc/en/reference/sessionreference.xml 
  Log:
  typos
  
  this needs a rewrite, some parts are incomprehensible due to lack
  of structure.
  
  
Index: phpdoc/en/reference/session/reference.xml
diff -u phpdoc/en/reference/session/reference.xml:1.14 
phpdoc/en/reference/session/reference.xml:1.15
--- phpdoc/en/reference/session/reference.xml:1.14  Thu Oct  3 03:54:36 2002
+++ phpdoc/en/reference/session/reference.xml   Thu Oct  3 04:02:03 2002
@@ -1,5 +1,5 @@
 
-
+
  
   Session handling functions
   Sessions
@@ -134,10 +134,11 @@
  Use of $_SESSION (or
  $HTTP_SESSION_VARS with PHP 4.0.6 or less) is
  recommended for improved security and code readablity. With
- $_SESSION, there is no need to use
- session_register()/session_unregister()/session_is_registered()
- functions. Session variables are accessible like any other
- variables.
+ $_SESSION, there is no need to use the
+ session_register(),
+ session_unregister(),
+ session_is_registered() functions. Session variables
+ are accessible like any other variables.
  
   
Registering a variable with $_SESSION.
@@ -179,7 +180,7 @@
 
@@ -189,12 +190,12 @@
 
  If register_globals
- is enabled, then all global variables can be registered as session
- variables and the session variables will be restored to corresponding
- global variables. Since PHP must know which global variables are
- registered as session variables, users need to register variables with
- session_register() function. You can avoid this by simply setting entries
- in $_SESSION.
+ is enabled, then each global variable can be registered as session
+ variable. Upon a restart of a session, these variables will be restored
+ to corresponding global variables. Since PHP must know which global
+ variables are registered as session variables, users need to register
+ variables with session_register() function. You can avoid this by simply
+ setting entries in $_SESSION.
  
   
If you are using



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DOC] cvs: phpdoc /en/reference/session reference.xml

2002-10-03 Thread Sascha Schumann

sas Thu Oct  3 03:54:37 2002 EDT

  Modified files:  
/phpdoc/en/reference/sessionreference.xml 
  Log:
  Bring documentation a bit closer to reality
  
  

Index: phpdoc/en/reference/session/reference.xml
diff -u phpdoc/en/reference/session/reference.xml:1.13 
phpdoc/en/reference/session/reference.xml:1.14
--- phpdoc/en/reference/session/reference.xml:1.13  Sat Sep 14 17:26:46 2002
+++ phpdoc/en/reference/session/reference.xml   Thu Oct  3 03:54:36 2002
@@ -1,5 +1,5 @@
 
-
+
  
   Session handling functions
   Sessions
@@ -112,52 +112,32 @@
   As of PHP 4.1.0, $_SESSION is available as
   global variable just like $_POST,
   $_GET, $_REQUEST and so on.
-  Not like $HTTP_SESSION_VARS,
-  $_SESSION is always global. Therefore,
-  global should not be used for
-  $_SESSION.
+  Unlike $HTTP_SESSION_VARS,
+  $_SESSION is always global. Therefore, you do not
+  need to use global for
+  $_SESSION. Please note that this documentation
+  has been changed to use $_SESSION everywhere. You can
+  substitute $HTTP_SESSION_VARS for
+  $_SESSION, if you prefer the former.
  
 
 
 
  If track_vars is
- enabled and register_globals
  is disabled, only members of the global associative array
- $HTTP_SESSION_VARS can be registered as session
+ $_SESSION can be registered as session
  variables. The restored session variables will only be available
- in the array $HTTP_SESSION_VARS.
- 
-  
-   Registering a variable with track_vars
-   enabled
-  
-  
-
-  
- 
+ in the array $_SESSION.
 
 
  Use of $_SESSION (or
  $HTTP_SESSION_VARS with PHP 4.0.6 or less) is
- recommended for security and code readablity. With
- $_SESSION or
- $HTTP_SESSION_VARS, there is no need to use
+ recommended for improved security and code readablity. With
+ $_SESSION, there is no need to use
  session_register()/session_unregister()/session_is_registered()
- functions. Users can access session variable like a normal
- variable.
+ functions. Session variables are accessible like any other
+ variables.
  
   
Registering a variable with $_SESSION.
@@ -178,7 +158,7 @@
  
  
   
-   Unregistering a variable with $_SESSION.
+   Unregistering a variable with $_SESSION and register_globals disabled.
   
   
 
   
  
+ 
+  
+   Unregistering a variable with register_globals enabled, after
+   registering it using $_SESSION.
+  
+  
+
+  
+ 
 
 
  If register_globals
  is enabled, then all global variables can be registered as session
- variables and the session variables will be restored to
- corresponding global variables. Since PHP must know which global
- variables are registered as session variables, users must register
- variables with session_register() function while
- $HTTP_SESSION_VARS/$_SESSION
- does not need to use session_register().
+ variables and the session variables will be restored to corresponding
+ global variables. Since PHP must know which global variables are
+ registered as session variables, users need to register variables with
+ session_register() function. You can avoid this by simply setting entries
+ in $_SESSION.
  
   
If you are using
-   $HTTP_SESSION_VARS/$_SESSION
+   $_SESSION
and disable register_globals,
do not use session_register,
session_is_registered and
-   session_unregister.
+   session_unregister, if your scripts shall work
+   in PHP 4.2 and earlier. You can use these functions in 4.3 and later.
   
   
If you enable register_globals
-is recommended for both security and performance reason.
+is recommended for both security and performance reasons.
   
  
  
@@ -243,20 +238,21 @@
  
 
 
- If both track_vars and
- register_globals
- are enabled, then the globals variables and the
- $HTTP_SESSION_VARS/$_SESSION
- entries will reference the same value for already registered
- variables.
+ is enabled, then the global variables and the
+ $_SESSION entries will automatically reference the
+ same value for session variables which were registered in prior session
+ instances.
 
 
- If user use session_register() to register session variable,
- $HTTP_SESSION_VARS/$_SESSION
- will not have these variable in array until it is loaded from
- session storage. (i.e. until next request)
+ Additionally, if you register a new session variable by using
+ session_register(), the entry in the global scope
+ and the $_SESSION entry will not reference the same
+ value until the next session start (this applies to PHP 4.2 and before
+ only).  I.e. a modification to the