You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I just updated to the latest version, and noticed that whenever I redirect a page, my session gets destroyed. I've narrowed down the problem to the YiiDebugToolbarPanelRequest::run() method; more specifically, with $_SESSION. When I remove $_SESSION and set the "session" context value to null, everything works as expected. Of course, I had to make a few minor changes to a couple views by checking if $session is not empty and is an array, but disabling the Session Attributes request panel solves my problem.
I even added a check to see if session_id() is an empty string right before rendering the panel, but the problem still persisted. Any ideas what might be causing this issue? I do have auto start off for my session handler.
The text was updated successfully, but these errors were encountered:
I lost the entire day trying to find out why this is happening. The strange thing for me is that on Chrome everyting is ok, so the problem was only Firefox.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just updated to the latest version, and noticed that whenever I redirect a page, my session gets destroyed. I've narrowed down the problem to the YiiDebugToolbarPanelRequest::run() method; more specifically, with $_SESSION. When I remove $_SESSION and set the "session" context value to null, everything works as expected. Of course, I had to make a few minor changes to a couple views by checking if $session is not empty and is an array, but disabling the Session Attributes request panel solves my problem.
I even added a check to see if session_id() is an empty string right before rendering the panel, but the problem still persisted. Any ideas what might be causing this issue? I do have auto start off for my session handler.
The text was updated successfully, but these errors were encountered: