msession_unlock
The note about an included file not being able to access the sessions is not true. You just have to do a session_start(); in the included file.
This is what drove me here today, because I was noticing the same thing. But I tried the above on a whim and it works fine. You wouldn't think you'd need to start a session twice, but I guess the scripts are looked on as separate in that regard.
Mike
Session Handling
- Introduzione
- Installazione/Configurazione
- Costanti predefinite
- Esempi
- Sessions and security
- Session Funzioni
- session_cache_expire — Ritorna il valore corrente di scadenza della cache
- session_cache_limiter — Assume o imposta il limitatore di cache corrente
- session_commit — Alias di session_write_close
- session_decode — Decodifica i dati di sessione da una stringa
- session_destroy — Distrugge tutti i dati registrati in una sessione
- session_encode — Codifica i dati della sessione corrente in una stringa
- session_get_cookie_params — Restituisce i parametri del cookie di sessione
- session_id — Assume o imposta l'id di sessione corrente
- session_is_registered — Scopre se una variabile è registrata nella sessione
- session_module_name — Assume o imposta il corrente modulo di sessione
- session_name — Recupera e/o imposta il nome della sessione corrente
- session_regenerate_id — Update the current session id with a newly generated one
- session_register — Registra una o più variabili con la sessione corrente
- session_save_path — Assume o stabilisce il percorso di salvataggio sessione corrente
- session_set_cookie_params — Imposta i parametri del cookie di sessione
- session_set_save_handler — Imposta le funzioni di archiviazione sessioni a livello utente
- session_start — Inizializza i dati di sessione
- session_unregister — Deregistra una variabile dalla sessione corrente
- session_unset — Libera tutte le variabili di sessione
- session_write_close — Scrive i dati di sessione e termina la sessione
add a note
User Contributed NotesSessions
mike at basementideas dot com
08-Jul-2008 02:05
08-Jul-2008 02:05
pushedx
02-Jul-2008 12:01
02-Jul-2008 12:01
Here is something to watch out for when working with sessions.
Let's say you have two pages, Page A and Template Z. If Page A sets session data and includes Template Z, the session data is not properly registered for the execution of Template Z due to how session data is written *after* a script has executed [1].
As a result, your second page will not have the right session data, so you are a bit in a pickle. I'm sure there are other work arounds, perhaps with cookies or flat files, but you cannot use session data in that fashion.
The reason I have this setup is because I will have a number of Page A-Z's that will contain page specific content and one Template Z page that renders each page's specific content in the site layout. This way, the site content changing is independent of the style the site uses and the site style can change without modifying the actual content. It's a dynamically configurable site template design.
[1] See the "session_write_close" documentation page.