As I mentioned earlier - it is not because I don't know how to
circumvent it
but next to actually fixing the bugs/issues I just felt that reporting
them
would be a good thing :)
/Thomas
Rasmus Lerdorf wrote:
>
> Should work just fine. But since you don't seem to care how you do it, I
> don't u
Should work just fine. But since you don't seem to care how you do it, I
don't understand why you don't just do the obvious. Loop through the GET
vars and set each one. ie.
foreach($HTTP_GET_VARS as $name=>$val) $$name=$val;
-Rasmus
On Mon, 4 Mar 2002, Thomas Wentzel wrote:
> PHP 4.1.2 std.
PHP 4.1.2 std. no CVS
Rasmus Lerdorf wrote:
>
> Which version of PHP? I tested your file123 thing here and it worked just
> fine.
>
> On Mon, 4 Mar 2002, Thomas Wentzel wrote:
>
> > I'm very sorry, but it seems - that the solution with
> > import_request_variables
> > is even worse. I've trie
Which version of PHP? I tested your file123 thing here and it worked just
fine.
On Mon, 4 Mar 2002, Thomas Wentzel wrote:
> I'm very sorry, but it seems - that the solution with
> import_request_variables
> is even worse. I've tried import_request_variables with ("g","f") and
> ("g","foo")
> bu
I'm very sorry, but it seems - that the solution with
import_request_variables
is even worse. I've tried import_request_variables with ("g","f") and
("g","foo")
but now foo isn't even set in file2.php (the url arg to file3 is now
"bar")
Thomas Wentzel wrote:
>
> OK! Thanks, Rasmus!
>
> That wil
OK! Thanks, Rasmus!
That will allow me to keep working on my current model
/Thomas
Rasmus Lerdorf wrote:
>
> Use import_request_variables('g') instead of parse_str($QUERY_STRING) for
> now. It does the same thing in your case in a more efficient manner. I
> think the session code is holding a
Use import_request_variables('g') instead of parse_str($QUERY_STRING) for
now. It does the same thing in your case in a more efficient manner. I
think the session code is holding a reference to the original data and
php_treat_data() is not doing the right thing when overwriting existing
vars. Or s
hehe
Thanks - I needed that :)
Rasmus Lerdorf wrote:
>
> It is. I am looking at it now. There may actually be a problem. $foo is
> set to foobar, but the session stays at "bar" if $foo is set via
> parse_str(). Something funky in the session code. parse_str() is working
> just fine.
>
> -R
It is. I am looking at it now. There may actually be a problem. $foo is
set to foobar, but the session stays at "bar" if $foo is set via
parse_str(). Something funky in the session code. parse_str() is working
just fine.
-Rasmus
On Mon, 4 Mar 2002, Markus Fischer wrote:
> On Mon, Mar 04, 2
On Mon, Mar 04, 2002 at 09:21:26AM +0100, Thomas Wentzel wrote :
> And Markus - thanks, but I tried to subsitute parse_str($QUERY_STRING)
> with parse_str("foo=foobar") which also didn't set my session var, foo
> So that is not the problem either!
Ah! I now see what you mean!
Have you
Actually, yes it does...
$foo="foobar"; instead of parse_str($QUERY_STRING);
in file2.php - then file3.php echoes "foo: foobar".
Obviously - otherwise there wasn't any point in having sessions.
And Markus - thanks, but I tried to subsitute parse_str($QUERY_STRING)
with parse_str("foo=foobar") w
Sure, Rasmus!
But...
I'm using parse_str because file2 in my example is supposed to be
a generic handler for all other scripts on my "site". Offcourse I could
use "1.5 million" $HTTP_GET_VARS for each registered session variable
(as
I wouldn't know what to expect)
The reason I did write to this li
On Mon, Mar 04, 2002 at 08:49:09AM +0100, Thomas Wentzel wrote :
> file2.php:
> session_start();
> $old=$foo;
> parse_str($QUERY_STRING);
>
> Header("Location: file3.php?old=$old&foo=$foo");
> ?>
>
> file3.php:
> session_start();
> echo "foo: $foo";
>
You are posting to the wrong list. And why are you using parse_str()?
PHP automatically imports these variables for you. Use
$foo=$HTTP_GET_VARS['foo'] in that second script of yours.
Next time send your user-level question like this to php-general.
-Rasmus
On Mon, 4 Mar 2002, Thomas Wentzel
Hi,
I have encountered an issue with parse_str, that I believe needs to
be addressed - allthough I might be mistaken, and in that case feel
free to ridicule me - and tell me to go to the general list :)
Well... I want to be able to do something like this:
file1.php:
file2.php:
15 matches
Mail list logo
