Re: parse_str and session vars
| From: | Rasmus Lerdorf | Date: | Mon, 04 Mar 2002 08:38:21 +0000 |
| Subject: | Re: parse_str and session vars | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-80678@lists.php.net to get a copy of this message | ||
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 something funky like that. It is too late at night to figure this
particular code out.
-Rasmus
On Mon, 4 Mar 2002, Thomas Wentzel wrote:
> 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.
> >
> > -Rasmus
> >
> > On Mon, 4 Mar 2002, Markus Fischer wrote:
> >
> > > 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 double checked that, after parse_str(), $foo is set
> > > to foobar ?
> > >
> > > --
> > > Please always Cc to me when replying to me on the lists.
> > > GnuPG Key:
> > > http://guru.josefine.at/~mfischer/C2272BD0.asc
> > >
>