Have you checked these first?
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
Note: Never paste the contents of your ost-config.php file here; it holds your database credentials.
Two quick checks before posting: try clearing your browser cache, and press SHIFT+O on any Staff Panel page to enter Safe Mode (a stock osTicket with no enhancements). If the problem still shows in Safe Mode, it's in osTicket itself, not osTicket Awesome. But let us know about the issue either way.
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
This forum is public. Never post order numbers, full license keys, email addresses, or payment details.
This is the place for general questions about how billing and licensing work — renewals, activation, staging slots, plan differences, and what happens when a license lapses.
For anything tied to your specific account, refund, or payment, contact us directly instead.
PHP 7.4.25 // MySQL 5.7.32 // Apache web server
Hi Guys,
Tried this upgrade twice now and never had an issue - the upgrade appears to go ok, but after the upgrade everything works ok apart from when you click the "open" queue button you get this error. Any ideas welcome...
Update - I have tried this a few more times including playing with the version of PHP. Something doesnt seem right, I either get an error clicking on the open ticket queue button (everything else is ok) OR most of the time (4 times out of 6) the bar containing "open / my tickets / closed / search / new ticket" wont show properly. It will flash up for second then vanish, i note it also happens to the cookies message on the bottom of the page at the same time.
It doesn occur in the vanilla version it much be the OSTicket Awesome build?
Can anyone suggest anything?
Many thanks!
Anyone out there?
Please can someone help?
Hello world?
Hi @alexbuckland,
I'm sorry I didn't reply in a timely manner.
I assume you've worked this out by now, but if not feel free to write back and let me know.