Blocks/cart -won't keep the info

[llegrand]

on version 1.2.1  (the site that has issues is this block)  I have now found how to remove the information that was previously stuck (wouldn't delete).   Now the cart holds the selected products as long as the session is open.   But when the site is closed-  does not matter if they are logged into their account or not,  the items in the cart do not remain.   

Where is the information for this stored in the DB?
Do I need to replace the file(s)  that control this action?  If so,  which ones?

This is the block info:

 Block Text ID cart Controller blocks/cart Block Templates :blocks/cart_top.tplblocks/cart.tpl

thanks
Lee

[abolabo]

can you check is session id value changed after site closed? Also check session ttl (setting). Plus php can purge sessions automatically with it's own GC (garbage collector). You should to investigate this setting with phpinfo(); (or php.ini)

[llegrand]

On the site it says
mysql.connect_timeout = 20;
session.use_cookies = On;
session.use_trans_sid = Off;
session.gc_maxlifetime = 12000000;

Checking with an account older on the site:
When first open session:
PHPSESSID_AC_CP7682295d5782f5253ec387049f81a3b3

PHPSESSID_AC_SF
73076ff1f5b7e5d1234b8130325fc6fb

Added three items  - left site,  and returned -  nothing in the view cart,  ID remain the same.

PHPSESSID_AC_CP7682295d5782f5253ec387049f81a3b3

PHPSESSID_AC_SF73076ff1f5b7e5d1234b8130325fc6fb

I am unclear as to which session ttl setting you are inquiring -  there are lots of places that can be set.

This site is set up on the same server with the same configurations that several other abantecart installations are running and they do not have this issue.

Perhaps I should just replace the files that control this functions?
I can make a fresh install  and port the DB,  I just want to be sure that the issue is not resident in the DB someplace.

Thanks

[abolabo]

Abantecart stores session_id on client side as cookie. Other session stuff is in session data on server side. If some process kills it - you should to determine it.

I see only 3 variants of causes:
- cookie issue (forbidden) (session_id the same in your case)
- php garbage collector (GC) (http:://php.net/manual/en/session.configuration.php#ini.session.gc-divisor)
- session expire time in your settings
- some other process clears php temporary directory(shell scripts, cgi, etc).

I have no more ideas yet. I don't see cause is in session class. It clear data only in case when session expires

[abolabo]

i think this value wrong
session.gc_maxlifetime = 12000000;