[stevland]

This isn’t an osTicket Awesome question, but thank you for sharing your solution.

[stevland]

Hi guys, 

I’m sorry that I’ve been unavailable for a while.

And I agree, this is a terrible mistake.

I’m really pleased that you managed to work out your own solution.

For anyone else that is reading this, upgrade to the latest hotfix (osTicket-1.17.3-Awesome-102) or (recommended) simply open /include/client/header.inc.php and replace its contents with this code.

[stevland]

Hi guys. You are asking for new upstream osTicket features that are beyond my paygrade! ( ._.)

You should ask here: https://forum.osticket.com/t/feature-request

Sorry I can’t help.

[stevland]

Hi @jmyderwykpolice-belleville-on-ca,

Sorry for the inconvenience. It is fixed now. Thank you for letting me know! 

[stevland]

@stephenehos-ca,

Thank you for the note. However, the logo is removed in Dark Mode by design.

I made this decision for two reasons.

Hopefully most osTicket admins take the time to format their company’s logo to make it look good in osTicket Awesome as per these logo tips.

But there’s a good chance the company logo won’t look good in Dark Mode.

So it would require the ability for the osTicket admin to upload a 2nd logo to be used when individual agents choose to enable Dark Mode.

This seems like unnecessary complexity.

The other reason I decided against displaying the logo is that it is unneeded in the first place.

The only people who should ever see the Agent Panel are, of course, agents. They already know what company they are working for. So I’ve always felt that the company logo in the backend is actually a waste of real estate.

In my mind, Dark Mode is a feature for power users.  I hope that most people will agree with me that the best option is to maximize the amount of useful information that is displayed on the screen.

[stevland]

Thank you for the report, Stephen@EhOS.

This will be fixed in the next release… very soon!

[stevland]

Thank you for sharing your fix, @reinierstuptech-com.

[stevland]

Hello everyone.

In case you haven’t noticed, osTicket Awesome now includes a Dark Mode… by popular demand!

Update and enjoy.

[stevland]

Hello everyone.

In case you haven’t noticed, osTicket Awesome now includes a Dark Mode… by popular demand!

Update and enjoy.

[stevland]

Hi lizenz,

This sounds exactly like an upstream issue with osTicket itself that was discussed on this forum here and here.

But that issue was resolved with 1.17.1. If you’re running 1.17.2 you should definitely not be encountering it.

Try editing include/class.usersession.php and replacing line 140 with the code on this page:

https://github.com/osTicket/osTicket/pull/6379/files

Let me know if that fixes your issue or not.

[stevland]

Hi lizenz,

I’m sorry for the super late reply.

I’ll need to take a look.

Please complete sections 1 and 2 of this form.

And in section 7 kindly add some instructions to help me reproduce the issue.

@reinierstuptech-com you can do the same, if you wish. Hopefully we can sort this out quickly.

[stevland]

Hello,

The first thing I would check is your cron job. Make sure the path to api/cron.php is still correct.

If that doesn’t resolve your issue there is lots of info related to troubleshooting osTicket / email fetching issues in the osTicket forum:

https://www.google.com/search?q=osticket+email+fetching+not+working

Keep in mind it is very unlikely this is an issue introduced by osTicket Awesome. In other words, if you’d upgraded to the latest version of vanilla osTicket — whatever the issue is — most likely you’d be experiencing it.

I point that out because there is no reason to limit your search for a solution to this forum.

[stevland]

@todd.kisida@xbyte.com,

A personal search!?

What a bizarre issue, and amazing that you figured it out. Thanks for sharing.

[stevland]

The reason I asked if you’re using OAuth2 is that what you have both described sounds like this issue:

https://forum.osticket.com/d/102248-microsoft-oauth-returning-to-homepage-without-user-logged-in/22

I can’t really help you with this (other than pointing you in the right direction) as I don’t use OAuth2 myself, and as this issue doesn’t have anything to do with osTicket Awesome it is way beyond the level of support I can offer.

I will mark this as ‘Resolved’, but you can still comment if you feel that I’ve made a mistake.

I hope you get this sorted out soon. Good luck.

[stevland]

Hi @mjdventures,

Thank you for your question.

Vanilla osTicket makes the entire row bold when there is a “new reply”, which includes both a) an existing ticket with a new comment from the client and b) an entirely new ticket that you haven’t responded to yet.

We decided a long time ago that this was too visually distracting. In other words, there was too much emphasis given to new replies and it ended up making the entire Ticket List look visually unattractive and hard to read.

Therefore, we made the design decision to use the green New Reply icon to make that distinction.

If you find this isn’t adequate enough for your needs you can add the following code to Admin Panel > Theme > Custom CSS

table.list tbody td a {
font-weight: inherit;
}

That CSS will additionally make the Subject text bold.