The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
You can change the configuration of session.cookie_lifetime so that the browser doesn't just throw your session's cookie away when it's closed (you just give it a number of seconds, and it sets the expiration date)...
ReplyDelete// assuming you can't change your php.ini file
ini_set('session.cookie_lifetime', 3600); // one hour
...But how long do you want the session to remain viable? Because another configuration setting you'd need to worry about is session.gc_maxlifetime, which sets (again, in seconds) how long session data is allowed to exist (unchanged, I believe?) before it is considered garbage.
The default for session.gc_maxlifetime is 1,440 seconds, or about 24 minutes.
Consider the security risks mentioned. to extend the session lifetime,
ReplyDeleteyou can set the lifetime of the session cookie before starting the session as follows.
$lifetime=60*60*24*14; //2 weeks in seconds. you can change the time as you wish
session_set_cookie_params($lifetime, '/');
session_start();