Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi I am Useing db Sessions. as soon as the user login i save few params in the session via session::set, without Session::save() and it works i can retrive the data from the session at any point from any controller.
Now. from a diffrent controller after the user has loogedin . when i try to add more values to the session via Session::put/set it dosn't add it only when i use session::save();
Any Idea why i need to use Session::save(); and why i don't need at the first time?
once i use Session::save() can i still add data to the session ?
Thx
@primo They work for me without having to call save().
Not sure if you are doing this...but if you are dd()ing your output, then it won't save it to the database because Laravel saves the data at the end of the request lifecycle. dd() interrupts that so the sessions never get saved unless you manually call save().
It Happens also when i try to write it to the log. It also work for me when on login page without the save() method but not when i try to add data to the session along the way it doesn't work unless i use save()
Please or to participate in this conversation.