Hi Martin,
I’m sorry for the very late reply.
And you probably aren’t going to like this response, but it is extremely unlikely that this issue was introduced by osTicket Awesome. It is an upstream issue with osTicket itself.
Please see this issue report for more information and some possible fixes.
I will close this for now, but if you still feel for some reason that it is an issue related to osTicket Awesome you can still reply again.
Thank you for understanding.