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
Right now, if the user tries to access an inexistent URL or if there's some internal server error, the generic Apache 2 white error pages show up. We could instead configure some custom, branded error pages, with more user-friendly information.
…lude/class.session.php:314
To prevent following error:
PHP Fatal error: Uncaught Error: Call to a member function getId() on bool in /.../include/class.session.php:314
Logged back trace:
PHP Fatal error: Uncaught Error: Call to a member function getId() on bool in /.../include/class.session.php:314
Stack trace:
#0 /.../include/class.session.php(336): osTicket\\Session\\AbstractSessionStorageBackend->getRecord()
#1 /.../include/class.session.php(281): osTicket\\Session\\AbstractSessionStorageBackend->update()
#2 [internal function]: osTicket\\Session\\AbstractSessionHandler->write()
#3 [internal function]: session_write_close()
Right now, if the user tries to access an inexistent URL or if there's some internal server error, the generic Apache 2 white error pages show up. We could instead configure some custom, branded error pages, with more user-friendly information.
See this tutorial for steps on how to do this: https://www.digitalocean.com/community/tutorials/how-to-configure-apache-to-use-custom-error-pages-on-ubuntu-14-04
The text was updated successfully, but these errors were encountered: