[stevland]

The way the ticket list table now displays in mobile view involved some advanced hackery. Long story short the only way to display the table headers (i.e. “Ticket Number”, “Last Updated”, etc.) is through CSS. So I have to re-code all of the headings for every language pack into CSS as you see above.

I do have a way of automating the task using Google Translate, but you made me realize that that is giving poor translations. So now I am manually copying and pasting the user translated text that is already included in the osTicket language packs. 

So far I have 3 complete and 42 left to go. 🙁

[stevland]

It was the TinyMCE plugin. I disabled it and cleared the browser cache. Now everything works as expected.

The TinyMCE plugin is no longer developed or supported; you shouldn’t use it.

[stevland]

Thank you. That style has been moved to .client-desktop.css where it belongs. 🙂

[stevland]

BTW this is fixed in osTicket-1.12-Awesome-103, which is now available to download.

[stevland]

Hmmm. Please don’t misinterpret me, I am very motivated to help you resolve this. But I haven’t encountered this on my end. And I have been though the demos with a fine-toothed comb with all manner of browsers and devices. Also, no one else has reported this.

Therefore, I have to ask myself: what is different about your environment? 

You say you’ve used “IE, Chrome & Firefox”.

I assume you mean Edge — not IE — yes? (osTicket Awesome does not support IE!).

Given that you have access to IE or Edge I also assume that you are on Windows, correct?

I assume that you don’t have similar issues while loading other web pages, yes?

The more information you can provide about your environment the more likely it is that I can think of something to try.

Right now the only possibility that comes to mind is that you could have a third-party plugin or extension (such as an ad blocker) that is being glitchy and interfering with the loading of the page. Please try disabling any browser extensions.

You probably won’t like my response, but (unless another person jumps in here and reports the same issue) I really do think it is something on your end. Because I can’t see what you are experiencing it is almost impossible to troubleshoot. But I would be happy to connect to your computer through a TeamViewer session to figure it out. Let me know if you want to do this.

[stevland]

Oh ya, I didn’t notice that.

It is actually because of an oddity with osTicket’s code.

I submitted an issue report here.

I added it to my list to review before the next release. Thanks for the head’s up.

[stevland]

I’ve been struggling with how to represent the idea that there is a reply waiting. I wanted to make it something that everyone can easily understand. But the ‘1’ is hard-coded and does not actually indicate anything… if there are 2 replies it doesn’t say ‘2’. 

So yes I agree that this is a completely unsatisfactory solution. In fact, I’ve already decided to change it again. Here is how I designed it to work in the Client portal:

[stevland]

I will mark this as resolved for now, but feel free to respond if you haven’t sorted this out yet.

[stevland]

Hmmm. Perhaps you should try clearing your browser cache.

I haven’t received an email notification from your osTicket regarding a user account. You used info@osticketawesome.com, yes?

[stevland]

FYI osTicket-1.12-Awesome-103 is now available.

[stevland]

FYI osTicket-1.12-Awesome-103 is now available.

[stevland]

Added to list, thank you.

[stevland]

Cool. Thanks for your patience.

You have given me too many options. I can only use one translation after all. Should I go with these?

Fällig am
Geschlossen am
Erstellt am

[stevland]

I’ll have a patch ready tonight or tomorrow with all languages. But if you want a quick fix for German you can add the following to /osta/user-styles.css:

html[lang="de"] .list td.osta_ticket:before { content: "Ticketnummer";}
html[lang="de"] .list td.osta_lastupdated:before { content: "Letzte Aktualisierung";}
html[lang="de"] .list td.osta_subject:before { content: "Gegenstand";}
html[lang="de"] .list td.osta_username:before { content: "Von";}
html[lang="de"] .list td.osta_assignee:before { content: "Zugewiesen an";}
html[lang="de"] .list td.osta_duedate:before { content: "Geburtstermin";}
html[lang="de"] .list td.osta_closedate:before { content: "Abschlussdatum";}
html[lang="de"] .list td.osta_datecreated:before { content: "Datum erstellt";}
html[lang="de"] .list td.osta_department:before { content: "Abteilung";}
html[lang="de"] .list td.osta_lastmessage:before { content: "Letzte Nachricht";}
html[lang="de"] .list td.osta_lastresponse:before { content: "Letzte Antwort";}
html[lang="de"] .list td.osta_status:before { content: "Status";}
html[lang="de"] .list td.osta_team:before { content: "Mannschaft";}

[stevland]

I’m sorry, I think I misunderstood what we were talking about. 

There was an issue previously where custom fields would not show up. This has been fixed in the new release.

But you were pointing out that that ticket counting is not behaving as expected when filters are customized.

I believe this is an issue with osTicket itself. The best response is to report it in the osTicket forum or report it on GitHub.