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.
Hi, I have the same problem described here :
https://osticketawesome.com/forums/topic/text-size-in-menus-and-languages-issues/
However, what is NOT properly translated is some basic menu items (Open, My Tickets, Closed etc. Look at everything in this screenshot for example). I'm thinking this is a bug? As far as I understand, only your extra theme menus have custom texts?
Thanks!
As you will see in this screenshot, this is currently an issue with osTicket itself:
And it isn't limited to one language pack. Here I'm using the Japanese language pack:
I took the time to report this in the osTicket Forum.
Ah, I see, that's a bummer! I'll have to translate some stuff in the php files. Thanks for the clarification!
I hope they fix it for 1.14, I'm hoping to upgrade to 1.14 as soon as your theme is updated for it after it's release.
I see it still isn't fixed in 1.12.3, unfortunately.
I expect it will be fixed by 1.14, if not sooner!