Bug #14339 Updated: functions available in the xml source do not show up in the online manual

From: Date: Tue, 04 Dec 2001 18:41:49 +0000
Subject: Bug #14339 Updated: functions available in the xml source do not show up in the online manual
References: 1  Groups: php.dev php.doc 
Request: Send a blank email to php-dev+get-72483@lists.php.net to get a copy of this message
ID: 14339 Updated by: hholzgra Reported By: sschmidt@strategyfirst.com Old Summary: no parse_str function on-site ??? Status: Assigned Bug Type: Documentation problem Operating System: irrelevant PHP Version: 4.1.0 Assigned To: hholzgra New Comment: ... :( forget about the iis_* functions (not documented) and the pcntl_* stuff (documented but not included in manual.xml) but at least yp_errno and yp_err_string are definetly missing Previous Comments: ------------------------------------------------------------------------ [2001-12-04 13:36:42] eschmid@php.net Sorry making traffic, it was only my stupid Windows ME. There many people working for php.net. But the source of the PHP manual should be the same. I have now looked over the history of en/functions/strings.xml and found only parse_str() but no parse_url(). Hartmut, could it possible, that you have branched out the parse_url() function :) If parse_str() isn´t visible in the online manual, we are using wrong tools. I know this is not a place to start discussions about books. Which book are you using? Please mail per PM to eschmid@php.net ------------------------------------------------------------------------ [2001-12-04 13:35:25] hholzgra@php.net Egon: repeating off-topic facts doesn't help at all both jade and openjade on my local system do not generate the parse_str() page, to and there are even more functions affected: - iis_add_server - iis_get_dir_security - iis_get_script_map - iis_get_server_by_comment - iis_get_server_by_path - iis_get_server_rights - iis_remove_server - iis_set_app_settings - iis_set_dir_security - iis_set_script_map - iis_set_server_rights - iis_start_server - iis_start_service - iis_stop_server - iis_stop_service - parse_str - pcntl_fork - pcntl_signal - pcntl_waitpid - pcntl_wexitstatus - pcntl_wifexited - pcntl_wifsignaled - pcntl_wifstopped - pcntl_wstopsig - pcntl_wtermsig - yp_err_string - yp_errno ------------------------------------------------------------------------ [2001-12-04 13:24:18] goba@php.net I am one webmaster@php.net. I can say, that the problem is not at php.net, Jade our XML->HTML generator program cannot generate that function.parse-str.php named HTML file used in the online manual to show the documentation. This may be an undocumented thing in the Jade program. This is why this function is listed at zend.com and in the XML file, but not in the online manual at php.net. Strange thing though that there is a http://www.zend.com/manual/function.parse-str.php but no http://www.php.net/manual/en/function.parse-str.php I don't know how often the zend.com manual is updated, but I think not that often as the php.net one (daily)... ------------------------------------------------------------------------ [2001-12-04 13:13:47] eschmid@php.net Look at the two functions at http://zend.com/phpfunc/p.php. Both functions have valid links to the online manual. ------------------------------------------------------------------------ [2001-12-04 13:10:59] sschmidt@strategyfirst.com It never even occurred to me to try www.zend.com. I've been spoiled by the semming user-friendliness at www.php.net (not to mention the easy to remember URL...) but I finally found the function in my print (paper) PHP book. Who works on the www.php.net? Anybody here who can just fix it? Isn't it an obvious and easy thing to fix, if all the text is already on the Zend website? ------------------------------------------------------------------------ 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/?id=14339 Edit this bug report at http://bugs.php.net/?id=14339&edit=1

« previous php.dev (#72483) next »