#21886 [Com]: parameters sometimes not submitted

From: Date: Mon, 17 Feb 2003 06:13:47 +0000
Subject: #21886 [Com]: parameters sometimes not submitted
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-33296@lists.php.net to get a copy of this message
ID: 21886 Comment by: wayne@ptaff.ca Reported By: technik@infoworxx.de Status: Feedback Bug Type: Session related Operating System: Linux 7.2 PHP Version: 4.3.0 New Comment: sniper@php.net, I guess the '$session' variable confuses your understanding of the problem. The snippet from the first report does NOT use any session-related functions and after forking this bug to bug#22211 I realize it's the same bug after all: parameters sometimes not submitted (as the title says). Replace all occurences of '$session' with '$foo' and you'll get the same misbehavior. The simple and straightforward example you're looking for is in the bugreport itself: just wrap the redirectTo method in a "class whatever" and declare $session as an instance of that class. The result would be the same whether or not session-related are broken, fixed or not-existant. Please re-read the code and stop this ob-session ;) that bug really is a showstopper for all OO in PHP 4.3.0 Previous Comments: ------------------------------------------------------------------------ [2003-02-17 00:13:44] wayne@ptaff.ca sniper@php.net, I guess the '$session' variable confuses your understanding of the problem. The snippet from the first report does NOT use any session-related functions and after forking this bug to bug#22211 I realize it's the same bug after all: parameters sometimes not submitted (as the title says). Replace all occurences of '$session' with '$foo' and you'll get the same misbehavior. The simple and straightforward example you're looking for is in the bugreport itself: just wrap the redirectTo method in a "class whatever" and declare $session as an instance of that class. The result would be the same whether or not session-related are broken, fixed or not-existant. Please re-read the code and stop this ob-session ;) that bug really is a showstopper for all OO in PHP 4.3.0 ------------------------------------------------------------------------ [2003-02-15 10:13:42] sniper@php.net Then you must also know that some behaviour of them was fixed in 4.3.0 and most likely you're just relying on the broken behaviour...can't really tell without a short and complete example script. ------------------------------------------------------------------------ [2003-02-14 04:21:08] technik@infoworxx.de I am sorry, actually I do not have time, I hope I can give you an example in the next two days - sorry for that (but your first reply took more than two days :-). But - it is NOT an misunderstanding how sessions work. I am using sessions since the beginning of PHP 4 and the same code is running under 4.2.3 perfect. Regards, Sebastian ------------------------------------------------------------------------ [2003-02-13 12:40:12] sniper@php.net wayne@ptaff.ca: Please open your own report about this, seems like the original reporter of this bug is not responding and your problem seems a bit different. (IMO, neither of these are bugs, just misunderstanding how sessions work) ------------------------------------------------------------------------ [2003-02-13 11:04:18] wayne@ptaff.ca Ooops! I please forgive my mistake, in my last post, switch the call from: $bar->myecho("apple, orange"); to: $bar->myecho("apple", "orange"); ------------------------------------------------------------------------ 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/21886 -- Edit this bug report at http://bugs.php.net/?id=21886&edit=1

« previous php.bugs (#33296) next »