I have an "index.php" page, near the top of which this line
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can close that page and - as long as I =
do not close the browser - I can come back and continue from where I =
was, thanks to the session administration. It works fine.
A bit down on the same page I have the following sequence - a link, =
disguised as a button:
The page "users_guide.php" is quite plain - no interaction with user or =
anything else. It does not use any session variables. It opens quite ok. =
To close it I use the cross in the upper right corner (Windows).
But ... When I come back to "index.php", I get=20
isset($_SESSION['run_id'])=3DFALSE
and thereby a new run id!
I have a number of "fake buttons" like this on that page and they all =
have the same effect on the run id. In one of them the addressed page =
actually uses the run id. That works ok, so I know it was not destroyed =
before the button was pressed.
By the way - if I use a simple link instead, the run id is persistent as =
it should be.
Any idea of how I can get around this (without going back to simple =
links - they don't look nice)?
I have an "index.php" page, near the =
top of which=20
this line
if =
(!isset($_SESSION['run_id']))=20
{$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can =
close that page=20
and - as long as I do not close the =
browser - I=20
can come back and continue from where I was,
size=3D2>thanks to the session administration. It works =
fine.
A bit down on the same page I have the =
following=20
sequence - a link, disguised as a=20
button:
The page "users_guide.php" is quite =
plain - no=20
interaction with user or anything =
else. It does=20
not use any session variables. It opens quite ok. To close it I use the =
cross in=20
the upper right corner
size=3D2>(Windows).
But ...
size=3D2>When I come=20
back to "index.php", I get
size=3D2>isset($_SESSION['run_id'])=3DFALSE
and thereby a new run id!
I have a number of "fake buttons" like =
this on that=20
page and they all have the same
size=3D2>effect on=20
the run id. In one of them the addressed page actually uses the =
face=3DArial size=3D2>run id. That works ok, so I know it was not =
destroyed before=20
the button was pressed. By the way - if I use a simple link instead, =
the run=20
id is persistent as it should =
be.
Any idea of how I can get around this =
(without=20
going back to simple links - they =
don't look=20
nice)?
size=3D2>/=20
Erik
size=3D2>
------=_NextPart_000_0008_01C80E65.98892670--
Re: Session variables persistency
am 18.10.2007 16:20:59 von yakuza
don't know wat u want exactly but you can set session to expire after
a certain time even if browser is closed
session_cache_expire(10); // set to expire after 10 mins
session_start();
$_SESSION['run_id']=3Dtime();
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
---- when do you want session destroyed, after what effect?
On Oct 14, 12:24Â pm, "Erik Kullberg" wrote:
> I have an "index.php" page, near the top of which this line
>
> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
>
> produces a persistent run id. I can close that page and - as long as I do=
not close the browser - I can come back and continue from where I was, tha=
nks to the session administration. It works fine.
>
> A bit down on the same page I have the following sequence - a link, disgu=
ised as a button:
>
>
border-style:solid; border-width:0px; border-color:black; padding:5px; marg=
in:0px;" TARGET=3D"_blank">
>
font-family:Times New Roman; font-size: 12px; font-weight: bold; width:90px=
; height:25px; padding-bottom: 0; " >
>
>
> The page "users_guide.php" is quite plain - no interaction with user or a=
nything else. It does not use any session variables. It opens quite ok. To =
close it I use the cross in the upper right corner (Windows).
>
> But ... When I come back to "index.php", I get
>
> isset($_SESSION['run_id'])=3DFALSE
>
> and thereby a new run id!
>
> I have a number of "fake buttons" like this on that page and they all hav=
e the same effect on the run id. In one of them the addressed page actually=
uses the run id. That works ok, so I know it was not destroyed before the =
button was pressed.
> By the way - if I use a simple link instead, the run id is persistent as =
it should be.
>
> Any idea of how I can get around this (without going back to simple links=
- they don't look nice)?
>
> / Erik
Re: Session variables persistency
am 18.10.2007 19:27:09 von Erik Kullberg
I do not want the session destroyed, but I get it destroyed after visiting
the described link. I cannot understand why.
/ Erik
"yakuza" skrev i meddelandet
news:1192717259.539807.40700@i38g2000prf.googlegroups.com...
don't know wat u want exactly but you can set session to expire after
a certain time even if browser is closed
session_cache_expire(10); // set to expire after 10 mins
session_start();
$_SESSION['run_id']=time();
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
---- when do you want session destroyed, after what effect?
On Oct 14, 12:24 pm, "Erik Kullberg" wrote:
> I have an "index.php" page, near the top of which this line
>
> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
>
> produces a persistent run id. I can close that page and - as long as I do
> not close the browser - I can come back and continue from where I was,
> thanks to the session administration. It works fine.
>
> A bit down on the same page I have the following sequence - a link,
> disguised as a button:
>
>
> style="border-style:solid; border-width:0px; border-color:black;
> padding:5px; margin:0px;" TARGET="_blank">
>
>
>
> The page "users_guide.php" is quite plain - no interaction with user or
> anything else. It does not use any session variables. It opens quite ok.
> To close it I use the cross in the upper right corner (Windows).
>
> But ... When I come back to "index.php", I get
>
> isset($_SESSION['run_id'])=FALSE
>
> and thereby a new run id!
>
> I have a number of "fake buttons" like this on that page and they all have
> the same effect on the run id. In one of them the addressed page actually
> uses the run id. That works ok, so I know it was not destroyed before the
> button was pressed.
> By the way - if I use a simple link instead, the run id is persistent as
> it should be.
>
> Any idea of how I can get around this (without going back to simple
> links - they don't look nice)?
>
> / Erik
Re: Session variables persistency
am 18.10.2007 23:18:32 von Michael Fesser
..oO(Erik Kullberg)
>I have made an example, see the three attached files.
Please don't post attachments to text-only groups (and no HTML like in
your first posting). Many newsservers will filter that out or even
reject the entire posting. Upload them to some webspace and post a URL.
>Put them in the same
>directory and run them, and you will see what I mean.
If you need help, you should make it as easy as possible for us to help
you. Don't expect us to copy files to our own servers (if we have one
available at all). A URL to a test case, maybe with a way to also
download the script's sources if necessary, works always best.
Micha
Re: Session variables persistency
am 19.10.2007 00:32:17 von Erik Kullberg
See http://kueng.se/session_test/page1.php
As you can see everything works fine as long as you can get back by use of a
link. If there is no link (so you have to get back the hard way) the session
ID will be destroyed.
Do you know of a cure for this?
/ Erik
"yakuza" skrev i meddelandet
news:1192717259.539807.40700@i38g2000prf.googlegroups.com...
don't know wat u want exactly but you can set session to expire after
a certain time even if browser is closed
session_cache_expire(10); // set to expire after 10 mins
session_start();
$_SESSION['run_id']=time();
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
---- when do you want session destroyed, after what effect?
On Oct 14, 12:24 pm, "Erik Kullberg" wrote:
> I have an "index.php" page, near the top of which this line
>
> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
>
> produces a persistent run id. I can close that page and - as long as I do
> not close the browser - I can come back and continue from where I was,
> thanks to the session administration. It works fine.
>
> A bit down on the same page I have the following sequence - a link,
> disguised as a button:
>
>
> style="border-style:solid; border-width:0px; border-color:black;
> padding:5px; margin:0px;" TARGET="_blank">
>
>
>
> The page "users_guide.php" is quite plain - no interaction with user or
> anything else. It does not use any session variables. It opens quite ok.
> To close it I use the cross in the upper right corner (Windows).
>
> But ... When I come back to "index.php", I get
>
> isset($_SESSION['run_id'])=FALSE
>
> and thereby a new run id!
>
> I have a number of "fake buttons" like this on that page and they all have
> the same effect on the run id. In one of them the addressed page actually
> uses the run id. That works ok, so I know it was not destroyed before the
> button was pressed.
> By the way - if I use a simple link instead, the run id is persistent as
> it should be.
>
> Any idea of how I can get around this (without going back to simple
> links - they don't look nice)?
>
> / Erik
Suddenly it works on this external server. It still does not work on my =
internal server.=20
Anyway - it seems it is not a php problem.
/ Erik
"Erik Kullberg" skrev i meddelandet =
news:80nQi.11276$ZA.7406@newsb.telia.net...
I have an "index.php" page, near the top of which this line
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can close that page and - as long as I =
do not close the browser - I can come back and continue from where I =
was, thanks to the session administration. It works fine.
A bit down on the same page I have the following sequence - a link, =
disguised as a button:
The page "users_guide.php" is quite plain - no interaction with user =
or anything else. It does not use any session variables. It opens quite =
ok. To close it I use the cross in the upper right corner (Windows).
But ... When I come back to "index.php", I get=20
isset($_SESSION['run_id'])=3DFALSE
and thereby a new run id!
I have a number of "fake buttons" like this on that page and they all =
have the same effect on the run id. In one of them the addressed page =
actually uses the run id. That works ok, so I know it was not destroyed =
before the button was pressed.
By the way - if I use a simple link instead, the run id is persistent =
as it should be.
Any idea of how I can get around this (without going back to simple =
links - they don't look nice)?
I have an "index.php" page, near the =
top of which=20
this line
if =
(!isset($_SESSION['run_id']))=20
{$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can =
close that=20
page and - as long as I do not =
close the=20
browser - I can come back and continue from where I was,
face=3DArial size=3D2>thanks to the session administration. It works=20
fine.
A bit down on the same page I have =
the following=20
sequence - a link, disguised as a=20
button:
The page "users_guide.php" is quite =
plain - no=20
interaction with user or anything =
else. It does=20
not use any session variables. It opens quite ok. To close it I use =
the cross=20
in the upper right corner
size=3D2>(Windows).
But ...
size=3D2>When I=20
come back to "index.php", I get
size=3D2>isset($_SESSION['run_id'])=3DFALSE
and thereby a new run =
id!
I have a number of "fake buttons" =
like this on=20
that page and they all have the same
size=3D2>effect on the run id. In one of them the addressed page =
actually uses=20
the run id. That works ok, so I =
know it was not=20
destroyed before the button was pressed. By the way - if I use a =
simple=20
link instead, the run id is persistent as
size=3D2>it=20
should be.
Any idea of how I can get around this =
(without=20
going back to simple links - they =
don't look=20
nice)?
size=3D2>/=20
Erik
size=3D2>
------=_NextPart_000_000C_01C811EA.D66398D0--
Re: Session variables persistency
am 20.10.2007 20:50:22 von yakuza
the session id stays the same for me. there is nothing in the code
that would destroy ses id. maybe you are rejecting your own cookies,
lol
On 18 Oct, 23:32, "Erik Kullberg" wrote:
> See http://kueng.se/session_test/page1.php
>
> As you can see everything works fine as long as you can get back by use o=
f a
> link. If there is no link (so you have to get back the hard way) thesessi=
on
> ID will be destroyed.
> Do you know of a cure for this?
> / Erik
>
> "yakuza" skrev i meddelandetnews:1192717259.539807.=
40700@i38g2000prf.googlegroups.com...
> don't know wat u want exactly but you can setsessionto expire after
> a certain time even if browser is closed
>
> session_cache_expire(10); // set to expire after 10 mins
> session_start();
> $_SESSION['run_id']=3Dtime();
> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
>
> ---- when do you wantsessiondestroyed, after what effect?
>
> Yakuza
> -----------------------
> ???????http://www.samamanda.com
>
> On Oct 14, 12:24 pm, "Erik Kullberg" wrote:
>
> > I have an "index.php" page, near the top of which this line
>
> > if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
>
> > produces a persistent run id. I can close that page and - as long as I =
do
> > not close the browser - I can come back and continue from where I was,
> > thanks to thesessionadministration. It works fine.
>
> > A bit down on the same page I have the following sequence - a link,
> > disguised as a button:
>
> >
> > style=3D"border-style:solid; border-width:0px; border-color:black;
> > padding:5px; margin:0px;" TARGET=3D"_blank">
> >
> > font-family:Times New Roman; font-size: 12px; font-weight: bold;
> > width:90px; height:25px; padding-bottom: 0; " >
> >
>
> > The page "users_guide.php" is quite plain - no interaction with user or
> > anything else. It does not use anysessionvariables. It opens quite ok.
> > To close it I use the cross in the upper right corner (Windows).
>
> > But ... When I come back to "index.php", I get
>
> > isset($_SESSION['run_id'])=3DFALSE
>
> > and thereby a new run id!
>
> > I have a number of "fake buttons" like this on that page and they all h=
ave
> > the same effect on the run id. In one of them the addressed page actual=
ly
> > uses the run id. That works ok, so I know it was not destroyed before t=
he
> > button was pressed.
> > By the way - if I use a simple link instead, the run id is persistent as
> > it should be.
>
> > Any idea of how I can get around this (without going back to simple
> > links - they don't look nice)?
>
> > / Erik
I have made some systematical tests, see =
http://kueng.se/session_test/page1.php
Maybe it is time to reinstall Apache and PHP, but I would like to know a =
little more, so I can avoid to get the same result again.
/ Erik
"Erik Kullberg" skrev i meddelandet =
news:80nQi.11276$ZA.7406@newsb.telia.net...
I have an "index.php" page, near the top of which this line
if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can close that page and - as long as I =
do not close the browser - I can come back and continue from where I =
was, thanks to the session administration. It works fine.
A bit down on the same page I have the following sequence - a link, =
disguised as a button:
The page "users_guide.php" is quite plain - no interaction with user =
or anything else. It does not use any session variables. It opens quite =
ok. To close it I use the cross in the upper right corner (Windows).
But ... When I come back to "index.php", I get=20
isset($_SESSION['run_id'])=3DFALSE
and thereby a new run id!
I have a number of "fake buttons" like this on that page and they all =
have the same effect on the run id. In one of them the addressed page =
actually uses the run id. That works ok, so I know it was not destroyed =
before the button was pressed.
By the way - if I use a simple link instead, the run id is persistent =
as it should be.
Any idea of how I can get around this (without going back to simple =
links - they don't look nice)?
I have made some systematical =
tests, see
class=3Dinline href=3D"http://kueng.se/session_test/page1.php" =
target=3D_blank>
face=3D"Times New Roman"=20
size=3D3>http://kueng.se/session_test/page1.php
Maybe it is time to reinstall Apache =
and PHP, but I=20
would like to know a little more, so I can avoid to get the same result=20
again.
I have an "index.php" page, near the =
top of which=20
this line
if =
(!isset($_SESSION['run_id']))=20
{$_SESSION['run_id']=3Dtime();}
produces a persistent run id. I can =
close that=20
page and - as long as I do not =
close the=20
browser - I can come back and continue from where I was,
face=3DArial size=3D2>thanks to the session administration. It works=20
fine.
A bit down on the same page I have =
the following=20
sequence - a link, disguised as a=20
button:
The page "users_guide.php" is quite =
plain - no=20
interaction with user or anything =
else. It does=20
not use any session variables. It opens quite ok. To close it I use =
the cross=20
in the upper right corner
size=3D2>(Windows).
But ...
size=3D2>When I=20
come back to "index.php", I get
size=3D2>isset($_SESSION['run_id'])=3DFALSE
and thereby a new run =
id!
I have a number of "fake buttons" =
like this on=20
that page and they all have the same
size=3D2>effect on the run id. In one of them the addressed page =
actually uses=20
the run id. That works ok, so I =
know it was not=20
destroyed before the button was pressed. By the way - if I use a =
simple=20
link instead, the run id is persistent as
size=3D2>it=20
should be.
Any idea of how I can get around this =
(without=20
going back to simple links - they =
don't look=20
nice)?
size=3D2>/=20
Erik
size=3D2>
------=_NextPart_000_000C_01C816DE.6B013090--
Re: Session variables persistency
am 25.10.2007 15:05:38 von Jerry Stuckle
Erik Kullberg wrote:
> I have an "index.php" page, near the top of which this line
>
> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
>
> produces a persistent run id. I can close that page and - as long as I
> do not close the browser - I can come back and continue from where I
> was, thanks to the session administration. It works fine.
>
> A bit down on the same page I have the following sequence - a link,
> disguised as a button:
>
>
> style="border-style:solid; border-width:0px; border-color:black;
> padding:5px; margin:0px;" TARGET="_blank">
>
>
>
> The page "users_guide.php" is quite plain - no interaction with user or
> anything else. It does not use any session variables. It opens quite ok.
> To close it I use the cross in the upper right corner (Windows).
>
> But ... When I come back to "index.php", I get
>
> isset($_SESSION['run_id'])=FALSE
>
> and thereby a new run id!
>
> I have a number of "fake buttons" like this on that page and they all
> have the same effect on the run id. In one of them the addressed page
> actually uses the run id. That works ok, so I know it was not destroyed
> before the button was pressed.
> By the way - if I use a simple link instead, the run id is persistent as
> it should be.
>
> Any idea of how I can get around this (without going back to simple
> links - they don't look nice)?
>
> / Erik
>
>
I doubt this is PHP or Apache. It sounds like your browser is clearing
cookies when you close the window.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Re: Session variables persistency
am 26.10.2007 00:08:40 von Erik Kullberg
Jerry, you are a genius!
I installed and ran Netscape v.8 and there everything is ok - no red results
in my test table!
I also reinstalled Explorer, but that had no effect.
Any idea of how to make Explorer behave?
/ Erik
"Jerry Stuckle" skrev i meddelandet
news:mNOdnbTTpogrCb3anZ2dnUVZ_tfinZ2d@comcast.com...
> Erik Kullberg wrote:
>> I have an "index.php" page, near the top of which this line
>> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
>> produces a persistent run id. I can close that page and - as long as I
>> do not close the browser - I can come back and continue from where I was,
>> thanks to the session administration. It works fine.
>> A bit down on the same page I have the following sequence - a link,
>> disguised as a button:
>>
>> style="border-style:solid; border-width:0px; border-color:black;
>> padding:5px; margin:0px;" TARGET="_blank">
>>
>>
>> The page "users_guide.php" is quite plain - no interaction with user or
>> anything else. It does not use any session variables. It opens quite ok.
>> To close it I use the cross in the upper right corner (Windows).
>> But ... When I come back to "index.php", I get
>> isset($_SESSION['run_id'])=FALSE
>> and thereby a new run id!
>> I have a number of "fake buttons" like this on that page and they all
>> have the same effect on the run id. In one of them the addressed page
>> actually uses the run id. That works ok, so I know it was not destroyed
>> before the button was pressed.
>> By the way - if I use a simple link instead, the run id is persistent as
>> it should be.
>> Any idea of how I can get around this (without going back to simple
>> links - they don't look nice)?
>>
>> / Erik
>>
>>
>
> I doubt this is PHP or Apache. It sounds like your browser is clearing
> cookies when you close the window.
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstucklex@attglobal.net
> ==================
>
Re: Session variables persistency
am 26.10.2007 05:29:42 von Jerry Stuckle
Erik Kullberg wrote:
> "Jerry Stuckle" skrev i meddelandet
> news:mNOdnbTTpogrCb3anZ2dnUVZ_tfinZ2d@comcast.com...
>> Erik Kullberg wrote:
>>> I have an "index.php" page, near the top of which this line
>>> if (!isset($_SESSION['run_id'])) {$_SESSION['run_id']=time();}
>>> produces a persistent run id. I can close that page and - as long as I
>>> do not close the browser - I can come back and continue from where I was,
>>> thanks to the session administration. It works fine.
>>> A bit down on the same page I have the following sequence - a link,
>>> disguised as a button:
>>>
>>> style="border-style:solid; border-width:0px; border-color:black;
>>> padding:5px; margin:0px;" TARGET="_blank">
>>>
>>>
>>> The page "users_guide.php" is quite plain - no interaction with user or
>>> anything else. It does not use any session variables. It opens quite ok.
>>> To close it I use the cross in the upper right corner (Windows).
>>> But ... When I come back to "index.php", I get
>>> isset($_SESSION['run_id'])=FALSE
>>> and thereby a new run id!
>>> I have a number of "fake buttons" like this on that page and they all
>>> have the same effect on the run id. In one of them the addressed page
>>> actually uses the run id. That works ok, so I know it was not destroyed
>>> before the button was pressed.
>>> By the way - if I use a simple link instead, the run id is persistent as
>>> it should be.
>>> Any idea of how I can get around this (without going back to simple
>>> links - they don't look nice)?
>>>
>>> / Erik
>>>
>>>
>> I doubt this is PHP or Apache. It sounds like your browser is clearing
>> cookies when you close the window.
>>
> Jerry, you are a genius!
> I installed and ran Netscape v.8 and there everything is ok - no red
> results in my test table!
> I also reinstalled Explorer, but that had no effect.
> Any idea of how to make Explorer behave?
>
> / Erik
>
>
(top posting fixed)
Toss it in the bit bucket? :-)
You might check an IE newsgroup. But I don't use it unless I am forced
to do so. So it might be a setting in it, but I wouldn't know what it
would be.
P.S. Please don't top post. Thanks.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================