well,
if you are on windoze, you could try IE(6), it assingns a ne session(id) in every new window, as it opens a new process everytime (you can see it in the taskmanager)
whereas FF and Opera use the same process for all simultaneously opened windows.
or -if you dislike IE (like I do)- just use different browsers.
Another attempt is described in php.ini,
; session.save_path = "N;/path"
; where N is an integer. Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories....
but i never tried it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
one solution would be copy $_SESSION array to $GLOBALS['SESSION'] and close session after init (end of common.lib.php) - but this prevents writing data back to session at a later point ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=326580
Originator: NO
yes - the session file can only be accessed exclusively
Logged In: YES
user_id=1383652
Originator: NO
well,
if you are on windoze, you could try IE(6), it assingns a ne session(id) in every new window, as it opens a new process everytime (you can see it in the taskmanager)
whereas FF and Opera use the same process for all simultaneously opened windows.
or -if you dislike IE (like I do)- just use different browsers.
Another attempt is described in php.ini,
; session.save_path = "N;/path"
; where N is an integer. Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories....
but i never tried it.
Logged In: YES
user_id=326580
Originator: NO
session.save_path = "N;/path" has no effect on this
it just tells PHP how to store the sessions
Logged In: YES
user_id=326580
Originator: NO
one solution would be copy $_SESSION array to $GLOBALS['SESSION'] and close session after init (end of common.lib.php) - but this prevents writing data back to session at a later point ...
Logged In: YES
user_id=1383652
Originator: NO
as of pma292 you can install you own (f.e. mysql based) session handler as well.
Logged In: YES
user_id=326580
Originator: NO
this is not a bug but a limitation (in PHP) - switch to another session handler than file
Logged In: YES
user_id=624319
Originator: YES
phpMyAdmin should call session_write_close() before sending the query to the database.
When the query has finished, than call session_start() again.
This is the only possible thing that have to be done.
Kind regards,
Michael Rack
http://www.michaelrack.de/
Close PHP session sounds misleading.