[stevland]

I have an updated version of osTicket Awesome for 1.11 to release in the next day or two.

Hopefully I will have a release ready for 1.12 within a week or two.

[stevland]

Sorry, I absolutely do not intend to support Internet Explorer at all.

If I did try to support IE, I would have to start by removing a bunch of features. And then 60% of my development time would be spent trying to make things work in IE. IE was obsolete before it was retired. Now even Microsoft says it isn’t a valid option for web browsing.

Incidentally, this topic has been covered before (and I offer a bit of a workaround in this discussion).

Safari is a different story. I am overdue to have a sit-down with Safari and try to coax it into playing nicely with osTicket Awesome. Chrome, Firefox, Opera and Edge are all very good at rendering web pages according to web standards. From a web design perspective, Safari is the new IE. 🙁

[stevland]

You can try this:

#sub_nav li + li > a {
    margin-left: 0 !important;
}
#sub_nav li.top-queue + li > a {
    margin-left: 20px !important;
}
.customQ-dropdown ul li > span.newItemQ {
    padding: 0 !important;
    margin: 0 8px 0 0 !important;
}

But this fix will be included in osTicket-Awesome-1.11-v1.1, which will drop in the next day or two.

[stevland]

Hmmm. What version of osTicket / osTicket Awesome are you using?

FYI I just uploaded and downloaded a bunch of files and opened them successfully using osTicket Awesome v1.11-1.0. I tested using.docx, .doc, .xlsx, .png and .jpg files.

If you would like me to look into this for you I will need you to create a temporary agent account (Admin Panel > Agents > Add New Agent) using info@osticketawesome.com. Be sure to give the account full administrative privileges.

[stevland]

@Energy 

FYI I did figure out what you are referring to. 

I disabled the bold font a long time ago because I feel it makes the ticket list look too cluttered.

I do see what you mean about being useful, however, so I’m trying to think of a compromise to implement in a future release.

It is on the list! Stay tuned.

[stevland]

@digitalis-france,

Have you tried hard-coding the full URL? I suspect that will fix your issue.

Using a relative link i.e. ../pics/login.png is fine on the server, but when you go to print I suspect that the PDF software will only look for local paths unless you specify the absolute https://domain.com/ etc. path.

I hope this helps!

 

[stevland]

I should also add that the ability to change priority from the main ticket screen was a mod that I developed.

Unfortunately it hasn’t been working properly for some time, and actually osTicket v1.11 broke it completely.

Unfortunately I have removed it for now but I plan on adding it back very soon.

[stevland]

BTW, you’ll be able to switch to English_CAD in the next releases starting next week.

And I’m including native support for both the UK and the Canadian flags.

[stevland]

Hi @aeromarine,

Just a head’s up, in case you haven’t noticed… this was fixed in the last release. I’ll have more releases next week so you may want to upgrade to the latest (1.11-v1.2) when it becomes available.

[stevland]

@visimitra,

I just saw your solution now, many months later.

Thank you for posting this! I added the vi instruction to the Troubleshooting page.

[stevland]

I’m sorry, I can’t support third-party plugins with osTicket Awesome. 

Having said that, I did take a quick look for you and I can say that there is nothing about this plugin that would make it difficult to install. Whether you are installing it with osTicket or osTicket Awesome — the instructions should pretty much be the same.

I have no idea how well it will work with osTicket Awesome though. YMMV. Good luck!

[stevland]

No problem.

Thanks for posting your solution. Hopefully it will help someone else.

I haven’t set up the OAuth plugin in years. Seeing your installation gave me a chance to tweak the CSS margins for the button, which will be included in future releases. 🙂

[stevland]

Hi @visimitra,

On my end the “Sign in with Google” button is showing up on correctly on both the Client and Staff login pages. I tested with

• Chrome, Edge, Firefox and Opera on Windows 10
• Chrome, Safari on MacOS
• Samsung Internet and Firefox on Android.

I also turned off my WiFi so that technically I used two disparate network connections to view your login pages.

Unless you fixed something on your end I have to speculate that there is something (firewall?) blocking the image on your network.

What is unique is that the image is loading off of Google’s server. Any other images that exist in osTicket / osTicket Awesome are loading locally. Perhaps you have some security setting that is preventing a remote file/image from being used.

<img class=”sign-in-image” src=”https://developers.google.com/+/images/branding/sign-in-buttons/Red-signin_Long_base_44dp.png” alt=”Sign in with Google+”>

I hope this gives you a clue and helps you figure it out.

I was happy to take a look, but I’m afraid that this not an osTicket Awesome issue and it falls outside of the type of things that I can support.

[stevland]

Yes, thanks for the heads up.

I am hoping to have corresponding releases next week.

[stevland]

Hi @visimitra,

If you send me the URL for your osTicket Awesome installation I will be happy to take a look.

If you wish to keep it private you can send it to info@osticketawesome.com.