php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #14841 this is a test bug report.
Submitted: 2002-01-04 00:42 UTC Modified: 2002-02-09 19:45 UTC
Votes:20
Avg. Score:3.4 ± 1.7
Reproduced:11 of 16 (68.8%)
Same Version:7 (63.6%)
Same OS:4 (36.4%)
From: jimw@php.net Assigned:
Status: Not a bug Package: Website problem
PHP Version: 4.1.1 OS:
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jimw@php.net
New email:
PHP Version: OS:

 

 [2002-01-04 00:42 UTC] jimw@php.net
hopefully the last new one for now.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-01-04 04:14 UTC] imajes@php.net
and this is a nice long comment that stretches lots....................................................................................................................................................................................................................................................................................................................................................................


 [2002-01-04 04:26 UTC] imajes@php.net
ok, that wasn't a long comment, it was a long word (which will in fact stretch an email. lets see how it copes when pasting some typical bug data....
./configure --with-apxs=/etc/httpd/bin/apxs --enable-track-vars --enable-ftp --with-gd=../gd-1.8.4 --prefix=/etc/php --sysconfdir=/etc/php --with-imap=../imapServer

What you are describing is normal behaviour.

The way exec() works is that it executes the first argument, and then returns all the output to the second argument as an array. Finally, any status the command returns is sent to the third argument, if specified. 

You may find these pages informative:

http://www.php.net/manual/en/function.exec.php
http://www.php.net/manual/en/ref.array.php

Previous Comments:

 [2002-01-04 04:26 UTC] imajes@php.net
ok, i'll stop hijacking this bug for now.
 [2002-01-04 15:48 UTC] jimw@php.net
more testing.
 [2002-01-04 16:28 UTC] derick@php.net
Bleh
 [2002-01-04 16:29 UTC] sterling at vl-srm dot net
I love weeeeeeeeed!
 [2002-01-04 16:32 UTC] derick@php.net
Blegh from Lynx
 [2002-01-04 16:33 UTC] derick at vl-srm dot net
mmmm, the submit button at the bottom would help a lot for me, a lynx user.

Derick
 [2002-01-04 16:35 UTC] sterling@php.net
I'M NOT FROM VL-SRM.NET!!!!!!!!! :)
 [2002-01-04 18:43 UTC] mfischer@php.net
Ene mene muh und draussen there you are.
 [2002-01-04 19:10 UTC] jan@php.net
greetings from the usergroup meeting cologne!
 [2002-01-04 23:19 UTC] ceo at l-i-e dot com
Testing on two platforms, in parallel.  Sorry.
 [2002-01-04 23:19 UTC] ceo at l-i-e dot com
Simply adding another comment for testing purposes.

Sorry.

<?php
  /* How does it do on code?
  */
?>

<?php
  # I can't type a TAB, but what if I paste it?
	$date = date('M d Y');
	$query = "select album_title, inventory.quantity, 
band_name, email_address, fname, lname ";
?>
 [2002-01-05 00:46 UTC] jimw@php.net
blah blah blah.
 [2002-01-05 00:47 UTC] jimw@php.net
hmm.
 [2002-01-05 06:25 UTC] hellekin@php.net
hop hop... Weed is weird. For my wedding I'll have a magic cauldron with weed in it. Lots of it. Magic, that is.
 [2002-01-05 06:28 UTC] hellekin@php.net
Does it support <b>some</b> <i>HTML</i> ?

Or even (<script

language="JavaScript"><!-- // alert('JavaScript !'); //--></script>JavaScript) ?

what about the <pre>
&lt;pre&gt; tag ?





























































</pre> ?
 [2002-01-05 06:39 UTC] hellekin@php.net
May I suggest to use the two following functions.
The first one is to get rid of JavaScript and unwanted stuff before storing to the database ; the second one for automagic formatting while displaying the stored message. It's useful to have two functions for cases when one can edit the message.

function msgClean($txt) {
 
    /* SCRIPT PATTERN MATCHING */
    $txt = preg_replace("/<script([\n\r]*.*)>([\n\r]*|[^>]*.*)<\/script>/i",'',$txt);
 
    /* STRIP UNWANTED HTML TAGS */
    $txt = strip_tags($txt,"<b></b><i></i><u></u>");
 
    return $txt;
}
function msgFormat($txt) {
 
    /* PLEASE KEEP THAT IN ORDER -- how */

    /* LINK MATCHING PATTERN */
    $txt = preg_replace("/([[:alpha:]]+):\/\/([\w\d-#\?=\/&]+[^\s_]+)(?<![,.:;])/i",'<a href="\1://\2">\1://\2</a>',$txt)

    /* EMAIL MATCHING PATTERN */
    $txt = preg_replace("/(?!mailto:)([[:alnum:]-.]+)@([[:alnum:]-.]+\.[[:alnum:]]{1,3})(?<![,.:;])/i",'<a href="mailto:\

    /* PARAGRAPH MATCHING PATTERN */
    $txt = preg_replace("/(\r\n\r\n|\n\n)/i",'<p>',$txt);
 
    /* SINGLE LINE MATCHING PATTERN */
    $txt = preg_replace("/(\r\n|\n)/i",'<br />',$txt);
 
    return  $txt;
}

 [2002-01-06 13:39 UTC] cynic@php.net
looks pretty good, but the metadata at the top (bug #, status, etc) is 
somewhat mangled in w3m. Looks better in links, and (ironically) best in lynx.

oh, and the submit button between the mailaddress input and the textarea on 
this page is IMO placed badly -- it'll result in lots of empty comments.
 [2002-01-06 13:41 UTC] jimw@php.net
it would only result in lots of empty comments if we didn't check to make sure a comment was submitted. :)
 [2002-01-06 14:45 UTC] jimw@php.net
this should look a little more tolerable in netscape 4. making sure it still works.
 [2002-01-08 13:32 UTC] philip at notloggedin dot net
This bug is crazy, I like!







a lot.
 [2002-01-15 07:13 UTC] sander@php.net
Shoudn't we make this bug a bogus so it doesn't show up in the stats???
 [2002-02-01 14:17 UTC] jimw@php.net
just testing.
 [2002-02-01 14:20 UTC] jimw@php.net
oops, the from address wasn't quite right. take 2.
 [2002-02-01 14:49 UTC] jimw@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

 [2002-02-01 14:50 UTC] jimw@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

 [2002-02-01 15:02 UTC] jimw@php.net
The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php
 [2002-02-01 15:04 UTC] jimw@php.net
The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php
 [2002-02-09 19:43 UTC] jimw@php.net
this should go through.
 [2002-02-09 19:45 UTC] jimw@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".


should go through.
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Tue Dec 06 00:03:59 2022 UTC