cookie_lifetime
> > only applies to cookies. So I don't
> > know why my sessions are not expiring. Does anybody have any Idea? Should
> > I just be manually checking
> > for the duration of the session(?) and then delete it if it has expired?
> &
I create a new object and then assign it to a session var
$customer = new Customer($_GET['facilityID'], $_GET['customerID']);
$_SESSION['acceptPayment']['customer'] = $customer;
but later when I access that session var [in the the same file but in a different function and different instance], php
Hi I was wondering if anybody has any Ideas about or has experienced
this
I create a new object and then assign it to a session var
$customer = new Customer($_GET['facilityID'], $_GET['customerID']);
$_SESSION['acceptPayment']['customer'] = $customer;
but later when I access that session var [
:
$customer = unserialize($_SESSION['acceptPayment']['serializedCustomer']);
and now you can access the object. There is a hidden jewl about this method, I now no
longer
have to include or require the class file because it is already defined in the
serialized string.
Matt
Matt
Wow thats strange?? I am using PHP 4.3.2 as well and I don't see that happening where
it serializes the object when assigning it to the $_SESSION. I am using the dbg
debugger and nusphere PHP editor and I can step through the code and as I do
it shows that the session var is not serialized. Howe
Hi Mike
Yes your right about when the session data is updated. The problem then
lies in when I try to read the object from the session var. I include at
the top of the file the class definition.
Not to get sidetracked but when you say you wrote another layer, are you
talking
about utilizing the
6 matches
Mail list logo
