have noticed that the session timed out message is not display any longer.
after re-logging back in, the message appeared.
cleared cookies and used different browsers, when my timeout is reached, the app logins out, but no message is displayed indicating that the timeout occurred
Note that when your session times out, you are redirected back to the login page with login.php?expired=1 and the message shows in the login page. If your project uses another page after session timeout, the message cannot be shown.
According to the source code, in the login page, the expiry message “Your session has expired” is displayed as error message. If you have enabled the advanced setting “Use Bootstrap Toast message”, the error message will be displayed as Toast (at the top right corner of the page), Toast error message will not auto-hide. If you have not enabled the advanced setting, the error message is displayed as Bootstrap alert in the page (under the “Login” page heading) and it will not auto-hide either.
So you may check that after session timeout to which page you are redirected. If not the login page (e.g. due to some page redirecting server event), you won’t see the error message. If it is the login page, you may check if there is any custom code which may prevent the server/client side error message from showing.
its setup as toast.
the message is being displayed… below the footer in the bottom left hand corner for some reason… both in edge and chrome
i did a login.php hack and removed:
// Session
if (session_status() !== PHP_SESSION_ACTIVE)
\Delight\Cookie\Session::start(Config(“COOKIE_SAMESITE”)); // Init session data
and the session timeout message appeared back in the top right hand corner.
is there something still lingering around from the past code?, all the other messages appear fine ?
also noticed that he login screen text input fields are the full length when the message does not appear, after removing the session cookie code, the login fields and prompts were centered on the page and not the full width…
I have the same code but I do not see such behavior. In fact, the code is server side and should not affect client side Toast. The Toast will not move to the bottom left unless some HTML is corrupted so the browser show it an unexpected position. I guess you did not do composer update (according to history the cookie composer package was added in v2020.0.14) and did not upload the “vendor” folder again, so the PHP outputs error (you can view the HTML source of the page in your browser to check) and the error breaks HTML so the browser render the page unexpectedly.
oh man… found the problem…
the user can chose the template profile from the 14 colors available (my customization), which is stored in their profile record. when they login I change the template to their selected choice. But on Page_Loading event, I didn’t check if it was == null, hence the login page css wasn’t loaded (user isn’t logged in yet…) and overwriting the default .css causing toast problem
added if clause, which checks if the thme is null and doesn’t activate the users theme yet…
if(@$_SESSION[‘gTheme’] != null)
Config(“PROJECT_STYLESHEET_FILENAME”, @$_SESSION[‘gTheme’]); // User’s Selected Project stylesheet