2. PHPRunner General questions
  3. Problems with Cookies and Multiple Sessions - IE versus Firefox
This topic is locked

Problems with Cookies and Multiple Sessions - IE versus Firefox

 		3/12/2009 12:04:02 AM
PHPRunner General questions
M
 MikeB941 author

PHPRUNNER BUILD 766

Firefox 3.0.7

IE 6.0.2900.2180...
Having peculiar problems under Firefox 3.0.7 running two different PHPRUNNER generated applications in two separate Firefox browser windows (one system is our picture inventory system, the other is our client information system - both are generated separately and have the SAME BASE URL but are uploaded into different directories i.e www.ourwebsite.com/app1'>www.ourwebsite.com/app1 and www.ourwebsite.com/app2'>www.ourwebsite.com/app2).
Under IE 6 all works as expected - under Firefox 3.0.7 it is NOT POSSIBLE to have two windows open running different PHPRUNNER generated applications as it appears they must share some kind of common cookie information and step on each other.
Firefox only shows 3 cookies (despite they're being two completely separate applications running: 1 username, 1 password and 1 PHPSESSID all three with the same base url i.e. www.ourwebsite.com).
IE must somehow distinguish the cookie identifiers (including the directory name) whereas Firefox 3.0.7 doesn't appear to be doing that and the two different applications appear to be overwriting each others cookie data (the symptom is erratic behavior (i.e no data, strangely presented pages, etc.) in one of the applications).
ANY HELP with ANY KNOWN issues with Cookies in Firefox 3.0.7 using multiple DIFFERENT generated PHPRUNNER applications at the same time in two different browser windows would be greatly appreciated.
Take Care... Mike.
M
 		MikeB941 author 3/12/2009

Also meant to add that the area this problem particularly seems to affect is the "last selection criteria". For example, if I sign into our CLIENT information system and go to the list page, all the clients are there and look normal.
If I then open another Firefox browser window and login to our PICTURE inventory (which has default search criteria on the list page) all looks normal there.
BUT, when I return to the CLIENT system and do a SHOW ALL on the list page NO RECORDS are displayed (in fact, there's NO WAY to get any client records displayed on the list page in the CLIENT system while the PICTURE system is active in another browser window.
As soon as I LOGOFF of the PICTURE system, I can go back into the CLIENT system and hit SHOW ALL and all the records return (again it looks like this search criteria info is being stored in a cookie and that cookie is being STEPPED ON between the two systems).
Thanks again for any help.
Take Care... Mike.
A
 		acpan 3/12/2009

I had similar issues and tried different cache settings on sever etc but wont work,

in the end, I used 2 seperate domain names instead of ip address, it fixed for me.
http://a.coy.com and http://b.coy.com
instead of
http://192.1.1.1/a and http://192.1.1.1/b
Hope it helps.
M
 		MikeB941 author 3/12/2009

Thanks very much for confirming this situation acpan and appreciate your suggestion for a work around!
SERGET - JANE - HELP - this is a BIG PROBLEM for our Firefox users (3.0.7 specifically).
Can the cookie handling code be modified to be BROWSER WINDOW/APPLICATION SPECIFIC in the Firefox environment to avoid these problems between two different PHPRUNNER generated applications running at the same time?
Many, many thanks for all of your help.
Take Care... Mike.
J
 		Jane 3/13/2009

Mike,
try to open generated include/dbcommon.php file and uncomment following line:

// @session_set_cookie_params(0,$dirname);


This workaround won't work if there are "bad" symbols in the directory name.
M
 		MikeB941 author 3/13/2009

Hi Jane!
WORKS BRILLIANTLY!!! Thank you so much!!!
I've always wondered how best to handle modifying the generated output like this?
I'll open a new topic for this - but THANKS AGAIN for all your help on this!
Take Care... Mike.
C
 		chaintm 6/10/2009

having this same issue with the newest build of phprunner, so I did this and its seems to have fixed it.