Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
On Monday 02 August 2004 01:33, M. Sokolewicz wrote: I think we should convert all to the 2nd type, it's just clearer...! any comments?:) I agree. Friedhelm Betz wrote: No, because the function definitions make sure which arguments are passed by reference. There is no need to even know this sort of information. User should know that some parameter can be changed by function as it is passed by reference. Jakub Vrana
Re: [PHP-DOC] windows install
Friedhelm Betz wrote: a.): As you mentioned, copy to SYSTEMROOT b.): Use PHPRC, can be mor than one location, e.g.: c:\; d:\; c:\php etc. c.): copy ini file to the same folder apache.exe lives in (this also works for lbmysql.dll and libmysqli.dll) There's also registry entry HKLM\Software\PHP\IniFilePath. Jakub Vrana
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
I think we should convert all to the 2nd type, it's just clearer...! any comments?:) No, because the function definitions make sure which arguments are passed by reference. There is no need to even know this sort of information. Users need to know where they need to pass a variable (as opposed to passing only a value), and what function modifies the passed parameter (as opposed to returning the resulting value). Goba
[PHP-DOC] cvs: phpdoc /en/reference/funchand/functions get-defined-functions.xml /en/reference/info/functions get-defined-constants.xml /en/reference/var/functions get-defined-vars.xml
vrana Mon Aug 2 05:32:15 2004 EDT Modified files: /phpdoc/en/reference/info/functions get-defined-constants.xml /phpdoc/en/reference/funchand/functions get-defined-functions.xml /phpdoc/en/reference/var/functions get-defined-vars.xml Log: See also http://cvs.php.net/diff.php/phpdoc/en/reference/info/functions/get-defined-constants.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/info/functions/get-defined-constants.xml diff -u phpdoc/en/reference/info/functions/get-defined-constants.xml:1.6 phpdoc/en/reference/info/functions/get-defined-constants.xml:1.7 --- phpdoc/en/reference/info/functions/get-defined-constants.xml:1.6Thu Dec 18 06:47:08 2003 +++ phpdoc/en/reference/info/functions/get-defined-constants.xmlMon Aug 2 05:32:13 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/info.xml, last change in rev 1.71 -- refentry id=function.get-defined-constants refnamediv @@ -58,6 +58,7 @@ /para para See also + functiondefined/function, functionget_loaded_extensions/function, functionget_defined_functions/function, and functionget_defined_vars/function. http://cvs.php.net/diff.php/phpdoc/en/reference/funchand/functions/get-defined-functions.xml?r1=1.4r2=1.5ty=u Index: phpdoc/en/reference/funchand/functions/get-defined-functions.xml diff -u phpdoc/en/reference/funchand/functions/get-defined-functions.xml:1.4 phpdoc/en/reference/funchand/functions/get-defined-functions.xml:1.5 --- phpdoc/en/reference/funchand/functions/get-defined-functions.xml:1.4Thu Jan 15 07:42:26 2004 +++ phpdoc/en/reference/funchand/functions/get-defined-functions.xmlMon Aug 2 05:32:14 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.4 $ -- +!-- $Revision: 1.5 $ -- !-- splitted from ./en/functions/funchand.xml, last change in rev 1.6 -- refentry id=function.get-defined-functions refnamediv @@ -69,7 +69,9 @@ /informalexample /para para - See also functionget_defined_vars/function and + See also + functionfunction_exists/function, + functionget_defined_vars/function and functionget_defined_constants/function. /para /refsect1 http://cvs.php.net/diff.php/phpdoc/en/reference/var/functions/get-defined-vars.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/var/functions/get-defined-vars.xml diff -u phpdoc/en/reference/var/functions/get-defined-vars.xml:1.6 phpdoc/en/reference/var/functions/get-defined-vars.xml:1.7 --- phpdoc/en/reference/var/functions/get-defined-vars.xml:1.6 Thu Dec 18 12:46:55 2003 +++ phpdoc/en/reference/var/functions/get-defined-vars.xml Mon Aug 2 05:32:14 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/var.xml, last change in rev 1.34 -- refentry id=function.get-defined-vars refnamediv @@ -49,7 +49,9 @@ /informalexample /para para - See also functionget_defined_functions/function and + See also + functionisset/function, + functionget_defined_functions/function and functionget_defined_constants/function. /para /refsect1
Re: [PHP-DOC] PECL Doc questions
Philip Olson wrote: Downloads should be smaller somehow like only include bundled extensions. What about building two manual versions - one with PECL and one without? IMHO it's not necessary nowadays as there are only a few PECL extensions documented but will be more important when the majority of 314 extensions (instantly growing) are documented. It's similar as with PHP 5 Windows binaries - PECL is in separate download. Jakub Vrana
[PHP-DOC] Security of sessions
There are several bug reports regarding security of sessions on multi-user environments, there is mail from Peter Brodersen about this to internals@ (http://news.php.net/php.internals/11549), there is mail from me with brief summary to security@ and nothing happens. Don't you mind if I add this warning to PHP manual? === RCS file: /repository/phpdoc/en/reference/session/reference.xml,v retrieving revision 1.47 diff -u -r1.47 reference.xml --- reference.xml 20 Jul 2004 01:27:19 - 1.47 +++ reference.xml 2 Aug 2004 09:32:32 - @@ -90,7 +90,17 @@ attacker might listen to your network traffic. If it is not encrypted, session ids will flow in plain text over the network. The solution here is to implement SSL on your server and make it mandatory for users. + Third, session ID can be read from client's system if it is compromited by + e.g. virus or security hole in browser or OS. /para +warning + para + Sessions can be hijacked by other users on multi-user environments + regardless of setting link linkend=ini.safe-modesafe_mode/link, + link linkend=ini.open-basediropen_basedir/link or + link linkend=ini.session.save-pathsession.save_path/link. + /para +/warning /section section id=session.requirements reftitle.required; -- Jakub Vrana
[PHP-DOC] Re: PECL Doc questions
Philip Olson wrote: Version info: Is this issue solved, will this go into the manual docs? Ref: http://marc.theaimsgroup.com/?l=phpdocm=107574257608183 I will try to modify versioning script to mark PECL functions. It will mark them without version number in the first step. Then we can improve the script to mark them with PHP version number and/or PECL extension version number. Jakub Vrana
Re: [PHP-DOC] windows install
http://testes.aborla.net/phpdoc/install.windows.html http://testes.aborla.net/phpdoc/faq.installation.html#faq.installation.addtopath diff: http://testes.aborla.net/win.install.diff Just a few notes :) 1. either manually or by using the installer installer. ^^^ 2. IMHO We should note on a big section level (like windows installer) that there are complete installation packages, and those install much more at once for you, but none of those are endorsed by PHP.net, as we beleive that the manual installation is the best choice to get to know the system. This is already noted in the manual install part, but IMHO we need to have a big section for all-in-one installers, so people will recognize our advice and warning of the applicability of those tools only for testing purposes :) 3. Planning for the future, I have also added an internal link on the ActiveScript engine stuff, so we can document how can it be registered as a Windows Scripting Host provider, and used for scripting. That is a short and easy to write part and should be included in the Windows install section (see the readme in the actionscript php source). 4. PHP5 - PHP 5 5. For better maintenaice, we advice ^^^ ^^ 6. Windows 95 should not be mentioned in the FAQ entry as it is not supported anymore. 7. I would not advise people to edit the registry. Instead I would recommend setting of PHPRC to users. The FAQ entry needs to be duplicated / generalized to cover both the PATH and PHPRC setting. It is better to reiterate the same procedure for two vars, then describing two different procedures for the two vars! 8. It is still not clear to me, how php[45]ts.dll is found by a CGI and an SAPI module setup, and what part of the install instructions guarantee that it will be found at the default place, where someone unzips PHP. BTW I have not checked the Apache stuff thoroughly. Please review my patch and let me know if I can commit it. And if yes, can I do the change to the new install section (including removing the old chapters/instal./.xml)? First fix the problems. If you only commit the changes you made to the new install part, then go and do it now, but if you would like to commit all at once (including the removal of the old section), then please fix all complaints first :) Goba
Re: [PHP-DOC] windows install
b.): Use PHPRC, can be mor than one location, e.g.: c:\; d:\; c:\php etc. If PHPRC can be more than one location, it would be very nice to mention somewhere! Goba
Re: [PHP-DOC] windows install
I only had a brief look, but following comes to my mind: Manual Installation Steps: I would like to advice people to use php-(sapiname).ini or at least mention this somewhere. I would second that the SAPI specific ini file names need more promotion! I like to suggest that setup of a valid php.ini file is moved to the server specific instructions. Because one can run php just fine without any ini-file, you need this mainly for enabling extensions, or setting specific instructions. It is better to document it in the manual part IMHO, as php.ini settings are not server specific. Windows and PWS 4 or newer Instructions for php 5 are missing, filenames imply its for php 4 only (e.g.: pws-php4cgi.reg) Same for Windows NT/2000/XP and IIS 4 or newer (e.g: php4isapi.dll) These should be PHP 5 ready, sure! Goba
Re: [PHP-DOC] Re: PECL Doc questions
Version info: Is this issue solved, will this go into the manual docs? Ref: http://marc.theaimsgroup.com/?l=phpdocm=107574257608183 I will try to modify versioning script to mark PECL functions. It will mark them without version number in the first step. Then we can improve the script to mark them with PHP version number and/or PECL extension version number. Great! Goba
Re: [PHP-DOC] PECL Doc questions
Downloads should be smaller somehow like only include bundled extensions. What about building two manual versions - one with PECL and one without? IMHO it's not necessary nowadays as there are only a few PECL extensions documented but will be more important when the majority of 314 extensions (instantly growing) are documented. This is only theoretical now, but without changing the file structure, we can make any number of books around our files, so we can separate PECL and core extensions in the far future, it need be. Goba
Re: [PHP-DOC] Security of sessions
This is kind of FUD if you don't provide details, it just sparks fear and does not help anything. Goba There are several bug reports regarding security of sessions on multi-user environments, there is mail from Peter Brodersen about this to internals@ (http://news.php.net/php.internals/11549), there is mail from me with brief summary to security@ and nothing happens. Don't you mind if I add this warning to PHP manual? === RCS file: /repository/phpdoc/en/reference/session/reference.xml,v retrieving revision 1.47 diff -u -r1.47 reference.xml --- reference.xml 20 Jul 2004 01:27:19 - 1.47 +++ reference.xml 2 Aug 2004 09:32:32 - @@ -90,7 +90,17 @@ attacker might listen to your network traffic. If it is not encrypted, session ids will flow in plain text over the network. The solution here is to implement SSL on your server and make it mandatory for users. + Third, session ID can be read from client's system if it is compromited by + e.g. virus or security hole in browser or OS. /para +warning + para + Sessions can be hijacked by other users on multi-user environments + regardless of setting link linkend=ini.safe-modesafe_mode/link, + link linkend=ini.open-basediropen_basedir/link or + link linkend=ini.session.save-pathsession.save_path/link. + /para +/warning /section section id=session.requirements reftitle.required;
[PHP-DOC] cvs: phpdoc /en/language operators.xml
vrana Mon Aug 2 06:54:00 2004 EDT Modified files: /phpdoc/en/language operators.xml Log: Associativity, precedence, remove print\n# internals@ didn't object http://cvs.php.net/diff.php/phpdoc/en/language/operators.xml?r1=1.76r2=1.77ty=u Index: phpdoc/en/language/operators.xml diff -u phpdoc/en/language/operators.xml:1.76 phpdoc/en/language/operators.xml:1.77 --- phpdoc/en/language/operators.xml:1.76 Tue Jul 27 17:30:24 2004 +++ phpdoc/en/language/operators.xmlMon Aug 2 06:54:00 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.76 $ -- +!-- $Revision: 1.77 $ -- chapter id=language.operators titleOperators/title simpara @@ -61,8 +61,12 @@ entry[/entry /row row -entryright/entry -entry! ~ - ++ -- (int) (float) (string) (array) (object) @/entry +entrynon-associative/entry +entry++ --/entry + /row + row +entrynon-associative/entry +entry! ~ - (int) (float) (string) (array) (object) @/entry /row row entryleft/entry @@ -113,10 +117,6 @@ entry = += -= *= /= .= %= amp;= |= ^= lt;lt;= gt;gt;= /entry - /row - row -entryright/entry -entryprint/entry /row row entryleft/entry
Re: [PHP-DOC] PECL Doc questions
On Fri, 30 Jul 2004, Philip Olson wrote: Here are some questions/concerns about having all PECL docs inside of phpdoc: Builds: Will all or just bundled PECL docs be in phpdoc manual builds? All. Meaning, will a separate PECL manual ever exist? No As PECL grows the manual will grow and like we discussed having a separate developers manual this is a *similar* issue. PECL is going to be huge one day and contain many specialized extensions. So? What's wrong with that? I think all PECL exts should be documented in the PHP Manual. regards, Derick
[PHP-DOC] cvs: phpdoc /scripts xml-check.php
vrana Mon Aug 2 07:25:09 2004 EDT
Added files:
/phpdoc/scripts xml-check.php
Log:
Check syntax of single manual page
http://cvs.php.net/co.php/phpdoc/scripts/xml-check.php?r=1.1p=1
Index: phpdoc/scripts/xml-check.php
+++ phpdoc/scripts/xml-check.php
#!/usr/bin/php
?php
/*
+--+
| PHP Version 4|
+--+
| Copyright (c) 1997-2004 The PHP Group|
+--+
| This source file is subject to version 3.0 of the PHP license, |
| that is bundled with this package in the file LICENSE, and is|
| available through the world-wide-web at the following url: |
| http://www.php.net/license/3_0.txt. |
| If you did not receive a copy of the PHP license and are unable to |
| obtain it through the world-wide-web, please send a note to |
| [EMAIL PROTECTED] so we can mail you a copy immediately. |
+--+
| Authors:Jakub Vrána [EMAIL PROTECTED] |
+--+
*/
if (!isset($_SERVER[argv][1])) {
echo Purpose: Check XML syntax of single PHP manual file.\n;
echo Usage: xml-check.php filename.xml [xmllint-command]\n;
echo Note: Links are not checked.\n;
exit();
}
$file = file_get_contents($_SERVER[argv][1]);
$xmllint = (isset($_SERVER[argv][2]) ? $_SERVER[argv][2] : xmllint);
$root = str_replace('\\', '/', dirname(__FILE__));
$root = substr($root, 0, strrpos($root, '/'));
$realpath = str_replace('\\', '/', realpath($_SERVER[argv][1]));
$example_filename = $root/xml-check.xml;
$rootpos = strlen($root) + 1;
$language = substr($realpath, $rootpos, strpos($realpath, '/', $rootpos) - $rootpos);
$header = preg_replace('~.*(!DOCTYPE.*)book.*~s', '\\1',
file_get_contents($root/manual.xml.in));
$header = str_replace(array('@srcdir@', '@LANGDIR@', \n), array('.', $language, ''),
$header); // \n to preserve line numbers
$file = preg_replace('~(?xml[^]*)(.*)~s', \\1$headerbook .
(!preg_match(~chapter|reference~, $file) ? chapter
id='example'titleExample/title\\2\n/chapter : \\2) . \n/book\n, $file);
$fp = fopen($example_filename, wb);
fwrite($fp, $file);
fclose($fp);
passthru($xmllint --noent --noout --valid $example_filename 2
$example_filename.out); // xmllint outputs to stderr which is not catched by
shell_exec, 2 1 doesn't work on Windows
$errors = file_get_contents($example_filename.out);
$errors = preg_replace(~.*validity error : IDREF attribute linkend references an
unknown ID.*\n.*\n.*\n~, , $errors);
$errors = str_replace($example_filename, $_SERVER[argv][1], $errors);
echo $errors;
//~ unlink($example_filename);
unlink($example_filename.out);
?
Re: [PHP-DOC] Check syntax of single file
Gabor Hojtsy wrote: Nobody answered :-(. In the mean-time, I wrote a script with this purpose. Should I add it to CVS? Yes, please :) Committed. Jakub Vrana
Re: [PHP-DOC] [PATCH] rtl...
What is the status of RTL support in livedocs? Goba moshe doron rta: you correction is mistake. RTL and CHARSET are defines not vars at all. --/moshe Nuno Lopes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Moshe, as I've already told you, your patch had a little bug with GLOBALS. Attached is a correction for your patch. Nuno - Original Message - Wez Furlong [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Now, quit complaining and get coding ;-) --Wez. http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt this patch contains: 1. initial rtl support. 2. add some missing htmlspecialchars(). i change the htmlentities(); on pre into htmlspecialchars() coz htmlentities(); doesn't fit well for not english charsets, do i miss something? --/moshe
Re: [PHP-DOC] [PATCH] rtl...
i didn't followed the last livedocs patchs but the last time i test it, after the rtl stuff was commited, its just worked fine. Moshe. Gabor Hojtsy [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] What is the status of RTL support in livedocs? Goba moshe doron rta: you correction is mistake. RTL and CHARSET are defines not vars at all. --/moshe Nuno Lopes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Moshe, as I've already told you, your patch had a little bug with GLOBALS. Attached is a correction for your patch. Nuno - Original Message - Wez Furlong [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Now, quit complaining and get coding ;-) --Wez. http://moshe.i-com-it.com/patchs/livedocs-rtl3.patch.txt this patch contains: 1. initial rtl support. 2. add some missing htmlspecialchars(). i change the htmlentities(); on pre into htmlspecialchars() coz htmlentities(); doesn't fit well for not english charsets, do i miss something? --/moshe
Re: [PHP-DOC] [PATCH] rtl...
i didn't followed the last livedocs patchs but the last time i test it, after the rtl stuff was commited, its just worked fine. Great, so then I can just pull off my unread mails from that TODO list :) Goba
[PHP-DOC] #29018 [Com]: function arguments 'null' and staticval with n passing by reference
ID: 29018
Comment by: josh at vodafone dot de
Reported By: none at space dot com
Status: Feedback
Bug Type: Documentation problem
Operating System: any
PHP Version: 4.3.6
New Comment:
Workarounds? How elegant! :P
You got to be kidding, right? We were talking improvements!
The workarounds are known by know. Is there nothing more elegant like
foo(NULL);
Previous Comments:
[2004-07-28 21:58:48] [EMAIL PROTECTED]
Possible solution:
function foo ( $var){
if (is_null($var)){return 0};
return(1);
}
$somevar = null;
foo($somevar);
Possible workarounds:
allow_call_time_pass_reference can be set on per directory basis.
@ can be added before function call (with side-effect of not displaying
any errors of course)
There's no other solution AFAIK.
[2004-07-19 14:24:07] jsabre at jjsbr dot tv
I was wondering about this too... how can you deprecate this and not
tell the community what is going on? I found only very little info
about this issue out there. But meny people seem to truggle with it.
[2004-07-07 11:57:57] jform at helmsdeep dot org
above: sorry, typo:
function foo ($obj){
should obviously be
function myfunc ($obj){
i was copying...
[2004-07-07 11:55:42] jform at helmsdeep dot org
I agree totally! We used to be able to do the following:
myfunc( $someobj); #and
myfunc(''); #this, if nothing passed
function foo ($obj){
if(is_null($obj)){...};
...
}
At this point we have to pre-check everything and do some massive
recoding! What is an easy solution for this or waht were you thinking
when chaning this? How do I pass 'nothing' now?
[2004-07-05 19:07:17] none at space dot com
Description:
proper reference documentation missing on how to switch from 'call-time
call-by-reference' to 'call-by-reference'.
with more and more ISP's upgrading php from versions prior the
deprecated 'call-time call-by-reference' to newer versions, more and
more people get utterly frustrated searching solutions to fix their
codes or libs for the two situations below.
especially passing 'no object' or null to a class has become critical
and there is no clear statement in the documentation of (references
explained) on what logic the guys that deprecated the the 'call-time'
functionality had in mind to compensate for that lack of
functionality.
i think it's about time you post the concept and solution of this
change somewhere prominently.
Reproduce code:
---
function foo ( $var){
if (is_null($var)){return 0};
return(1);
}
#call now
foo($somevar); #will work
foo('');#will not work (how to do this properly?)
foo(1); #will not work (obviously)
Expected result:
1
0
0
--
Edit this bug report at http://bugs.php.net/?id=29018edit=1
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
Gabor Hojtsy wrote: I think we should convert all to the 2nd type, it's just clearer...! any comments?:) No, because the function definitions make sure which arguments are passed by reference. There is no need to even know this sort of information. Users need to know where they need to pass a variable (as opposed to passing only a value), and what function modifies the passed parameter (as opposed to returning the resulting value). Goba Right, I agree with Gabor on this, users should indeed see, in just one quick look, which variables might/will be altered by running that function. It also helps people intuitivly understand how certain functions work, iow how to get a useful return from it.
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
On Mon, 2 Aug 2004, Jakub Vrana wrote: On Monday 02 August 2004 01:33, M. Sokolewicz wrote: I think we should convert all to the 2nd type, it's just clearer...! any comments?:) I agree. Friedhelm Betz wrote: No, because the function definitions make sure which arguments are passed by reference. There is no need to even know this sort of information. User should know that some parameter can be changed by function as it is passed by reference. 100% agreed on that. Derick
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
On Mon, 2 Aug 2004, Derick Rethans wrote: User should know that some parameter can be changed by function as it is passed by reference. 100% agreed on that. That said, I'm not sure if adding amp; before the variable name is a good idea though I can't see any other way of doing this. Derick
RE: [PHP-DOC] http://www.php.net/manual/en/ref.pfpro.php
Hi Nuno,
You know, I went and searched the lists immediately *after* I posted, and
saw what was going on :( Sorry about not doing that sooner, but thanks for
taking care of this; I really appreciate it!
Cheers,
--
Justin M
Technical Support
VeriSign Payment Services
[EMAIL PROTECTED]
888-883-9770
Be careful in handling your account information! Please note that VeriSign
will never ask for your personal information via email or a pop-up window.
For technical and product information, please visit our updated Payment
Services Support site at: http://www.verisign.com/support/payflow/
-Original Message-
From: Nuno Lopes [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 31, 2004 3:58 AM
To: Meyer, Justin; PHPdoc
Subject: Re: [PHP-DOC] http://www.php.net/manual/en/ref.pfpro.php
Hello Justin,
The notes system is currently down.
I've added your note to the manual. It should be on-line in a
week or so.
Thanks,
Nuno
- Original Message -
From: Meyer, Justin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 30, 2004 5:33 PM
Subject: [PHP-DOC] http://www.php.net/manual/en/ref.pfpro.php
Hi Guys,
The information/documentation at the above URL is missing a
small but
critical bit of information that may cause a lot of folks
to be unable
to use this extension. I've been attempting to add a note
there, and
an internal error is reported each time.
If I cannot add the note at this time, would it be possible
for you to
either revise the docs, or add the note for me? Below is what I had
written:
Hi All,
One thing the updated config notes don't cover is that you almost
certainly
need to configure/build this extension as a shared extension --
Payflow
Pro
is statically linked to an older version of OpenSSL, and if
you try to
compile this extension statically into PHP, and then use it with
ModSSL or the OpenSSL extension, you'll run into segfaults
and other
interesting problems. So:
./configure --with-pfpro=shared,/usr/local
I repeat: If you do not build this extension as a shared extension,
you
will
almost certainly have problems!
Once PHP is built and installed, you'll then need to modify your
php.ini
in
two places:
One, set extension_dir to the directory in which you find
'pfpro.so',
so that PHP knows where to find the extension.
Two, add a line to php.ini that reads 'extension=pfpro.so'
(minus the
quotes!), so that PHP will always load the extension. Otherwise,
you'll
have
to call ?php dl('pfpro.so'); ? at the beginning of any script you
want
to
use with Payflow Pro.
Perhaps that's more information than necessary, but it
covers the bulk
of the difficulties that people run into using this
extension. If this
information could be incorporated into the PHP docs for this
extension, I would be most grateful :)
In any case, thanks for all your hard work on making PHP's docs the
most accessible of any I've seen. Keep kicking ass :)
--
Justin M
Technical Support
VeriSign Payment Services
[EMAIL PROTECTED]
888-883-9770
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
* Thus wrote Derick Rethans: On Mon, 2 Aug 2004, Derick Rethans wrote: User should know that some parameter can be changed by function as it is passed by reference. 100% agreed on that. That said, I'm not sure if adding amp; before the variable name is a good idea though I can't see any other way of doing this. The only problem i see it that it may confuse people into thinking that they need to use the in the call($to_function) Mabey putting it on the datatype: int dns_get_mx ( string hostname, array mxhosts [, array weight]) Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid!
Re: [PHP-DOC] windows install
On Monday 02 August 2004 12:14, Gabor Hojtsy wrote: I only had a brief look, but following comes to my mind: Manual Installation Steps: I would like to advice people to use php-(sapiname).ini or at least mention this somewhere. I would second that the SAPI specific ini file names need more promotion! I like to suggest that setup of a valid php.ini file is moved to the server specific instructions. Because one can run php just fine without any ini-file, you need this mainly for enabling extensions, or setting specific instructions. It is better to document it in the manual part IMHO, as php.ini settings are not server specific. At least for the CGI setup they are, some need cgi.force_redirect set to 0. But we have a faq entry on this http://www.php.net/manual/en/ini.sect.path-directory.php#ini.cgi.force-redirect and linking this from server specific instructions is perhaps enough? If we want to promote SAPI specific ini file names, setup of php-(sapiname).ini should be in the server specific instructions. Why? I believe a typical newbie should do (outlined in brief): 1.) download php4/5 2.) unzip at some location (we should use that locations from main/config.w32.h: c:\php4 and c:\php5) 3.) what webserver? setup of that server (Apache1/2, IIS/PWS, Omni, Sambar 4.) test the server with phpinfo 5.) which ini filename? php-cgi.ini/php-apache.ini ... 6.) right place for ini-file, PHPRC, PHPIniDir, PATH, Systemroot, install it, adjust cgi.force_redirec if needed. 7.) do 4.) again, check if right ini is used 8.) install extensions/ change ini settings. 9.) do 4.) Windows and PWS 4 or newer Instructions for php 5 are missing, filenames imply its for php 4 only (e.g.: pws-php4cgi.reg) Same for Windows NT/2000/XP and IIS 4 or newer (e.g: php4isapi.dll) These should be PHP 5 ready, sure! Yep;-) Friedhelm -- http://www.jungle-world.com/
Re: [PHP-DOC] windows install
On Sunday 01 August 2004 17:54, Gabor Hojtsy wrote: And now? Advice Apache 1 users to copy php.ini to C:\windows (or C:\winnt for win NT/2k)? Advice them to name the file php-apache.ini ;-) Could not recall if the option for naming the inis like the used sapi is documented, if not it should. main/config.w32.h: #define PHP_CONFIG_FILE_PATH (getenv(SystemRoot))?getenv(SystemRoot): Some Options for Apache 1: a.): As you mentioned, copy to SYSTEMROOT b.): Use PHPRC, can be mor than one location, e.g.: c:\; d:\; c:\php etc. c.): copy ini file to the same folder apache.exe lives in (this also works for lbmysql.dll and libmysqli.dll) b) is the only option: Use PHPRC! I thought about twice and I wonder why it is preferable to use PHPRC instead just copy php-(sapiname).ini to SYSTEMROOT? Using PHPRC is indeed nice but seems to be a superfluous hurdle for newbies. We do not talk about 'copy dlls' just one/two ini-files to SYSTEMROOT. Nothing wrong with that, IMHO. Friedhelm -- http://www.jungle-world.com/
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
Curt Zirzow wrote: * Thus wrote Derick Rethans: On Mon, 2 Aug 2004, Derick Rethans wrote: User should know that some parameter can be changed by function as it is passed by reference. 100% agreed on that. That said, I'm not sure if adding amp; before the variable name is a good idea though I can't see any other way of doing this. The only problem i see it that it may confuse people into thinking that they need to use the in the call($to_function) Mabey putting it on the datatype: int dns_get_mx ( string hostname, array mxhosts [, array weight]) Curt Which would just confuse people even more IMHO :S - Tul
[PHP-DOC] cvs: phpdoc /en/reference/url/functions base64-decode.xml base64-encode.xml
ceceMon Aug 2 16:06:30 2004 EDT Modified files: /phpdoc/en/reference/url/functions base64-encode.xml base64-decode.xml Log: ws fix http://cvs.php.net/diff.php/phpdoc/en/reference/url/functions/base64-encode.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/url/functions/base64-encode.xml diff -u phpdoc/en/reference/url/functions/base64-encode.xml:1.6 phpdoc/en/reference/url/functions/base64-encode.xml:1.7 --- phpdoc/en/reference/url/functions/base64-encode.xml:1.6 Tue Jul 6 08:00:30 2004 +++ phpdoc/en/reference/url/functions/base64-encode.xml Mon Aug 2 16:06:30 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/url.xml, last change in rev 1.2 -- refentry id=function.base64-encode refnamediv @@ -34,7 +34,7 @@ ]] /programlisting para - This example will produce : + This example will produce: /para screen ![CDATA[ http://cvs.php.net/diff.php/phpdoc/en/reference/url/functions/base64-decode.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/url/functions/base64-decode.xml diff -u phpdoc/en/reference/url/functions/base64-decode.xml:1.6 phpdoc/en/reference/url/functions/base64-decode.xml:1.7 --- phpdoc/en/reference/url/functions/base64-decode.xml:1.6 Sat Aug 16 10:59:57 2003 +++ phpdoc/en/reference/url/functions/base64-decode.xml Mon Aug 2 16:06:30 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/url.xml, last change in rev 1.2 -- refentry id=function.base64-decode refnamediv @@ -29,7 +29,7 @@ ]] /programlisting para - This example will produce : + This example will produce: /para screen ![CDATA[
Re: [PHP-DOC] windows install
3. Planning for the future, I have also added an internal link on the ActiveScript engine stuff, so we can document how can it be registered as a Windows Scripting Host provider, and used for scripting. That is a short and easy to write part and should be included in the Windows install section (see the readme in the actionscript php source). Note that this has moved to PECL as of PHP 5.0.1 and the ProgId changed (damned registered trademarks!). Also note that an ancient syslog() bug on windows has been resolved in the last couple of days that requires a couple of registry keys to be created at installation time (but only if you want nice clear syslog output in your event log). I'll send you more details in a day or so (or you can peek at php-src/win32/build/registersyslog.php) --Wez.
Re: [PHP-DOC] Re: cvs: phpdoc /en/reference/array/functions natsort.xml
On Monday 02 August 2004 17:35, Derick Rethans wrote: On Mon, 2 Aug 2004, Derick Rethans wrote: User should know that some parameter can be changed by function as it is passed by reference. 100% agreed on that. Ok, Ok, convinced ;-) thinking about after enough sleep ;-)) That said, I'm not sure if adding amp; before the variable name is a good idea though I can't see any other way of doing this. If we go this way, we need to make clear how this protos are meant to read and used. In fact this should be clear but for newbis maybe a FAQ entry, or addition to appendices/about.xml the section about protos is suitable? Sadly, AFAIRC, most protos in the php-src are not written this way, which makes it hard(er) to generate protos from the source; admitting this might not be an argument for hiding this sort of info;) Friedhelm -- http://www.jungle-world.com/
Re: [PHP-DOC] windows install
On Monday 02 August 2004 12:11, Gabor Hojtsy wrote: http://testes.aborla.net/phpdoc/install.windows.html http://testes.aborla.net/phpdoc/faq.installation.html#faq.installation.ad dtopath diff: http://testes.aborla.net/win.install.diff Just a few notes :) [..] 8. It is still not clear to me, how php[45]ts.dll is found by a CGI and an SAPI module setup, and what part of the install instructions guarantee that it will be found at the default place, where someone unzips PHP. Guaranty for SAPI module setup to find php[45]ts.dll is the fact that it sits in the same folder as the SAPI dlls. This is true for PHP 5 as the zip is packaged this way and for PHP 4 by copy/move sapi dlls from sapi folder to the main folder php-4.x.y is unzipped. Friedhelm -- http://www.jungle-world.com/
[PHP-DOC] cvs: phpdoc /en/faq installation.xml /en/install/windows apache1.xml apache2.xml index.xml manual.xml
nlopess Mon Aug 2 17:33:03 2004 EDT Modified files: /phpdoc/en/install/windows apache1.xml apache2.xml index.xml manual.xml /phpdoc/en/faq installation.xml Log: re-write of the windows install section. still need some reviewing #going to sleep now... http://cvs.php.net/diff.php/phpdoc/en/install/windows/apache1.xml?r1=1.5r2=1.6ty=u Index: phpdoc/en/install/windows/apache1.xml diff -u phpdoc/en/install/windows/apache1.xml:1.5 phpdoc/en/install/windows/apache1.xml:1.6 --- phpdoc/en/install/windows/apache1.xml:1.5 Sat Jun 5 16:47:47 2004 +++ phpdoc/en/install/windows/apache1.xml Mon Aug 2 17:33:03 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.5 $ -- +!-- $Revision: 1.6 $ -- sect1 id=install.windows.apache1 titleApache 1.3.x on Microsft Windows/title para @@ -8,6 +8,12 @@ have link linkend=install.windows.apache2instructions and notes for Apache 2 on a separate page/link. /para +note + para + You should read the link linkend=install.windows.manualmanual + installation steps/link first! + /para +/note simpara There are two ways to set up PHP to work with Apache 1.3.x @@ -61,6 +67,9 @@ # For PHP 5 Action application/x-httpd-php /php/php-cgi.exe + +# specify the directory where php.ini is +SetEnv PHPRC C:/php ]] /programlisting /example @@ -94,53 +103,39 @@ sect2 id=install.windows.apache1.module titleInstalling as an Apache module/title - para - If you would like to use PHP as a module in Apache, be sure to copy - filenamephp4ts.dll/filename to the filenamewindows/system/filename - (for Windows 9x/Me), filenamewinnt/system32/filename (for Windows - NT/2000) or filenamewindows/system32/filename (for Windows XP) - directory, overwriting any older file. Then you should add the following - lines to your Apache httpd.conf; file: - itemizedlist - listitem -simpara - Open httpd.conf; with your favorite editor and locate the - literalLoadModule/literal directive and add the following line - emphasisat the end/emphasis of the list for PHP 4: - literalLoadModule php4_module c:/php/sapi/php4apache.dll/literal - or the following for PHP 5: - literalLoadModule php5_module c:/php/php5apache.dll/literal -/simpara - /listitem - listitem -simpara - You may find after using the Windows installer for Apache that you need - to define the literalAddModule/literal directive for - filenamemod_php4.c/filename. This is especially important if the - literalClearModuleList/literal directive is defined, which you will - find by scrolling down a few lines. You will see a list of - literalAddModule/literal entries, add the following line - emphasisat the end/emphasis of the list: - literalAddModule mod_php4.c/literal For PHP 5, instead use - literalAddModule mod_php5.c/literal -/simpara - /listitem - listitem -simpara - Search for a phrase similar to - literal# AddType allows you to tweak mime.types/literal. You will - see some literalAddType/literal entries, add the following line - emphasisat the end/emphasis of the list: - literalAddType application/x-httpd-php .php/literal. - You can choose any extension you want to parse through PHP here. .php - is simply the one we suggest. You can even include .html, and .php3 - can be added for backwards compatibility. -/simpara - /listitem - /itemizedlist + You should add the following lines to your Apache httpd.conf; file: /para - + para + example + titlePHP as an Apache 1.3.x module/title +programlisting role=apache-conf +![CDATA[ +AddType application/x-httpd-php .php + +# For PHP 4 +LoadModule php4_module c:/php/sapi/php4apache.dll + +# For PHP 5 +LoadModule php5_module c:/php/php5apache.dll + +# specify the directory where php.ini is +SetEnv PHPRC C:/php +]] + /programlisting + /example + /para + simpara + You may find after using the Windows installer for Apache that you need + to define the literalAddModule/literal directive for + filenamemod_php4.c/filename. This is especially important if the + literalClearModuleList/literal directive is defined, which you will + find by scrolling down a few lines. You will see a list of + literalAddModule/literal entries, add the following line + emphasisat the end/emphasis of the list: literalAddModule + mod_php4.c/literal. For PHP 5, instead use literalAddModule + mod_php5.c/literal + /simpara simpara If you would like to use the source code highlighting feature, you need
Re: [PHP-DOC] windows install
Nice done;-)
Thanks!
I only had a brief look, but following comes to my mind:
Manual Installation Steps:
I would like to advice people to use php-(sapiname).ini or at least
mention
this somewhere.
I like to suggest that setup of a valid php.ini file is moved to the
server
specific instructions. Because one can run php just fine without any
ini-file, you need this mainly for enabling extensions, or setting
specific
instructions.
Oh yes, I need to document the php-{sapi}.ini
Windows and PWS 4 or newer
Instructions for php 5 are missing, filenames imply its for php 4 only
(e.g.:
pws-php4cgi.reg)
Same for Windows NT/2000/XP and IIS 4 or newer (e.g: php4isapi.dll)
At the latest reading the instructions for IIS/PWS it is not clear to me,
where the ini-file should go, therefore my above suggestion to provide
this
sort of info perhaps in the server specific instructions ( at keast for
the
sapi modules)
Don't take this offending, jst a few thoughts after a very quick look;-)
Of course, no offending :) I haven't touch the IIS/PWS section. I can
install IIS tomorrow to test...
And if yes, can I do the change to the new install section
IMHO commit your nice work to the new install section, once it is there it
can
be easily reviewed and tweaked up, if needed.
OK, I'll commit it in a minute (with several fixes noticed by Goba).
It's already late now, but I'll review the docs tomorrow.
(including
removing the old chapters/instal./.xml)?
There's no hurry to remove the old files;-)
The hurry is just because 'make test' will fail if you don't delete those
files (because of ID colisions)
Nuno
