[stevland]

Hi @staidans,

Thank you for granting me access to your installation.

For some reason the ticket # is getting wrapped in an additional tag in your system that is messing up it’s padding.

I couldn’t figure out why this is happening, but the good news it that it was easy enough to fix. I simply added the following to your Custom CSS:

.osta_ticket .truncate {
    white-space: initial !important;
}

Have added this CSS property to the next release so that no one else will experience this issue in the future.

 

[stevland]

@esbd,

That definitely is not happening on this end.

It is probably something in your custom CSS. If you turn it off I think this issue will go away.

 

However, you can add this to the bottom of your CSS to override whatever you have that is causing this issue:

#content,
#open-or-check,
#check-ticket,
#complianceouter,
#compliance,
#more-options,
#information,
#footer {
    background-image: none !important;
}

Let me know if this helps so I can mark this as resolved.

[stevland]

Hmmm I’m trying to at least understand your request.

Obviously Level of Support is some type of custom field you have set up, but I’m having trouble visualizing what exactly it is.

How do you currently switch between level 1 etc? Can you send a screen shot of how Level of Support appears on the page right now? 

[stevland]

By the way, I did look into this some more because it would be a useful thing to add.

But I figured out why the osTicket developers themselves do not show the phone number on the Ticket View page.

In a default osTicket installation, there is only one phone # field, and it is labelled phone.

But the administrator can change the label to anything that they want.

In my case, phone # isn’t enough. I want to have fields for a contact’s work, mobile and home phone #’s.

So in my case, I got rid of phone and I created three new fields: wphone, mphone and hphone.

In fact, most users would probably change the phone field to something else. In your case, you may have changed the phone field to the Italian telefono.

So there are two problems:

1) If we try to show the user’s Phone # on the Ticket View page, but the administrator has renamed the phone label, the function will be broken.

2) In my case, I have three phone fields. So even if it was possible, displaying only the default one wouldn’t really help that much anyway.

All of this is why, I assume, the osTicket developers decided to make us click on the User’s name and have all of the Contact Information —including any custom fields — displayed in one list.

Sorry, there is no elegant way around this. 

[stevland]

By the way, we fully support the Attachments on the Filesystem plugin now.

Its instructions are exactly the same under osTicket Awesome as the are under vanilla osTicket.

[stevland]

Hi @skyler360,

I haven’t heard back from you. I will mark this as resolved for now, but if you’re still having trouble please answer my questions above and I will help you sort it out.

[stevland]

Hi @jodellagc,

It has been almost two weeks and I have not received a response from you. Hopefully you managed to resolve this issue. If not, another osTicket Awesome update is now available. Perhaps you will want to try your luck with that. If you still have an issue with Scheduled Tasks, my best advice is to set everything up as if it is the first time.

I will mark this as resolved for now, but please do not hesitate to post an update.

[stevland]

Hi @skyler360,

It has been almost 2 weeks and I have not heard back from you. I assume that this issue was resolved. But if you are still having trouble, please let me know.

[stevland]

Hi @netesi,

I will be happy to help you with this issue. When you get a chance please send me the answers to the questions above.

[stevland]

I haven’t heard back from you. I’ve gone ahead and included this fix in the latest release, which is available now on the Downloads page. I am confident that it will resolve this issue.

I will mark this as resolved for now, but please don’t hesitate to post an update at any time.

[stevland]

It seems to me that you are both using the jQuery German workaround that I came up with here: 
https://osticketawesome.com/forums/topic/osticket-1-14-patch-4-german/

This must have something to do with your issues, but I can’t reproduce it on my end.

Please try resetting any Ticket Queue customizations that you have:

If doing that doesn’t resolve the issue, the only way I can help is if I can access your installation to see for myself.

Please submit this form (you can ignore the CPanel, SSH and FTP sections):
https://osticketawesome.com/troubleshooting/assistance-request-form/

[stevland]

The new release is now available on the Downloads page. Please let me know if installing it resolves this issue for you or not.

[stevland]

Hi guys,

I haven’t been able to reproduce this in my demo installation, my own personal business installation, or on my testing server.

If either of you would be willing to let me access your installation, that would be extremely helpful.

If so, please submit this form with as much detail as possible. Otherwise, sorry but I am out of ideas.

[stevland]

I haven’t heard back from you in a while, so I will mark this as resolved. But you can still post an update here if you wish.

[stevland]

BTW all of these Console errors should be cleared up in the next release (later this week, you will receive an email notification when it is available). But yes, it will require installing the upgrade. Thanks, @tanks.