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.
Recently, we have observed that our awesome themes are occasionally reverting to their default settings, causing all customizations to be lost. This issue disrupts the user experience and undermines the reliability of our themes. Please help us with this issue.
We experience this too. We have a custom theme set and it gets switched off and reverts back to the default. We thought at first it was down to a user making a change but this is not the case.
We haven't been able to pin down what triggers the custom theme to be disabled.
Jeremy
Hi Jacqueline and Jeremy,
Thank you both for reporting this. I was able to reproduce this obscure issue and identify the cause.
The theme settings page was processing form data unconditionally on every request, including empty or incomplete ones. When that happened, all checkbox-based settings (custom theme toggle, scroll-to-top, consent message, custom CSS, etc.) were being blanked out and saved over your actual configuration. This could be triggered by things like a server's post_max_size being exceeded, a truncated request from a slow connection, or even a browser glitch, which explains why it seemed random and was so hard to pin down.
Apologies for the frustration this has caused. A fix will be included in the next release.
Is this issue taken care off ?
Is it any option for save configuration and roll-back ? (image)
This extremely rare issue was resolved in osTicket-1.18.3-Awesome-104.