[stevland]

You caught me on a good day! Glad I could help.

[stevland]

Please see the fourth item from the bottom on the FAQs page.

[stevland]

The table width is actually 100% of the space denoted by the tag #content.

Therefore, it is dictated by this (/osta/css/staff-desktop.css, line 55):

#content {
    max-width: 1200px;
}

But #content is a global template element that affects all pages, so if you want to tinker with the ticket list table you’ll want to do something like this to /osta/user-styles.css:

.index-page #content,
.tickets-page #content {
    max-width: 100%;
}

What you’ll find, however, is that this is not the magic fix that you are hoping for. The table itself will be wider, but the columns will retain their previous width. And if I remember correctly, setting the column widths using the new osTicket method of doing so is ignored by osTicket Awesome. But I could be wrong about this.

It has been a few months since I’ve tweaked the table layout, but let me assure you that possibly a hundred hours has gone into tweaking it over the past few years. I’m sure widening the table looks like a super easy thing to do, but even going from 940px to 1200px was a challenge.

Also keep in mind that if you make the table and columns wider, you’ll also want to test everything on smaller screens before declaring victory.

Please don’t mistake my willingness to point you in the right direction as a promise that you’ll find success, or a guarantee that I’ll support you in this endeavor.

Having said that, if you manage to pull off something that you are happy with and want to have it considered for inclusion in a future release, feel free to post your findings here.

[stevland]

The width of osTicket’s ticket list table is 940px.

In osTicket Awesome it is increased to a maximum width 1200px.

Not the improvement that you were hoping for, perhaps, but it is 27% wider.

Note that you have enabled 4 extra columns in that screenshot. I have to wonder if you would be happier with fewer custom columns.

A full-width ticket list (or at least a wider ticket list) in desktop layout is something that has been requested and is being considered for future development. Feel free to add your vote here.

I’m going to mark this as Resolved as there really isn’t anything to be “fixed”. But feel free to reply.

[stevland]

Clear your browser cache and let me know if that fixes the issue.

[stevland]

Hi boxer2t,

You’re right, I have the back to top button hidden in the mobile layout.

If you want to enable it, add the following code to /osta/user-styles.css:

@media screen and (max-width: 760px) {
    #scroll-to-top {
      display: inline;
    }
}

What do you guys think… should the back to top button be shown in the mobile layout, or is it superfluous?

[stevland]

Hi @strong,

I’m glad that you have it sorted… thank you for letting me know!

[stevland]

Lo sentimos, no hay opciones integradas para ajustar las fuentes en esa página.

La única forma de hacer cambios es usar CSS para anular los estilos. Pero esto requeriría algunos conocimientos sobre cómo escribir código CSS.

Se supone que la fuente utilizada para los números Abrir / Cerrado es Product Sans. Debe tener un aspecto como este:

Pero por alguna razón, la fuente Product Sans no se está utilizando en su instalación y los números parecen demasiado grandes.

Entonces, por ejemplo, si desea reducir el tamaño de esos números, puede agregar el siguiente código CSS a /osta/user-styles.css:

span.number {
    font-family: sans-serif;
    font-size: 20px;
    position: initial;
}

Con respecto a que Asunto se capitaliza, osTicket Awesome no está haciendo esto. Sus usuarios o agentes deben estar usando TODAS LAS MAYÚSCULAS cuando escriben el Asunto.

Estoy usando Google Translate para tratar de expresar algunos pensamientos complicados, espero que mis palabras sean claras y que esto te ayude.

No dude en responder si tiene más preguntas.

[stevland]

To be honest, this doesn’t sound like an issue specific to osTicket Awesome. But I am willing to try to help you narrow down the cause of the problem.

First, try clearing your browser cache and try again.

If that doesn’t help, try the Email Access Link function through the osTicket core interface (hopefully you kept a working copy of your original osTicket installation). Let me know if this works or not.

HTTP Error 500 is a very generic message that is displayed on the web page. The actual error message is recorded in the error logs, usually the Apache error logs. Have a look for the relevant message that is being recorded at the time that the Email Access Link form is submitted. Feel free to post the error here.

[stevland]

Thanks for the update, @boxer2t. I’m glad that you got it sorted.

[stevland]

Hola @sistemascsc,

Estoy feliz de echar un vistazo. ¿Cuál es la URL de su instalación?

Si prefiere mantenerlo en privado, puede enviar el enlace por correo electrónico a info@osticketawesome.com.

[stevland]

Hi @strong,

This is what the files should look like after being successfully extracted:

Have you managed to work it out yet?

[stevland]

Wow, this is a very unusual situation. The latest version has been downloaded dozens of times and this is the first issue that has been reported.

So you are saying that when you extract osTicket-1.12.2-Awesome-101.zip to your computer, the /osta folder is missing?!

Do you get any error messages when you extract it?

I would offer to take a look or even upload the files for you, but as you are on a private network this will not be possible.

If you send an email to info@osticketawesome.com I will reply with a Dropbox link to the archive. Maybe you’ll have better luck downloading it from another server.

[stevland]

Sorry, I didn’t foresee this possibility. In my experience, when a zip archive has corruption, nothing will extract. I can’t recall that I’ve ever ended up with a partial extraction.

In any event, I assume you are now uploading all of the newly extracted files to your server, yes?

Please let me know if this resolves the issue.

[stevland]

I see what you are saying now!

The whole osTicket navigation system was revamped in v1.11. I can’t recall why I didn’t include search in osTicket Awesome’s mobile navigation. Two possibilities come to mind:

1. I already had a Search field and an Advanced Search button in place, so I may have decided that these were adequate. If this is the case, I either didn’t realize that I was leaving out the Personal Search items in the mobile navigation, or I figured this feature wouldn’t be terribly missed (please note that it has never been my intention for the mobile layout to have 100% of the functionality that the desktop version has).
2. The new osTicket code that generates the navigation items is actually quite sophisticated. On my end it required quite a bit of hackery to transpose it into osTicket Awesome’s mobile navigation. I brought in a full-time PHP programmer to help work out the bugs. It is possible that we just could not get the Search functionality to cooperate.

tl;dr I can’t recall exactly why Search is missing from the mobile navigation. I will look into this and see what I can come up with and I will eventually let you know. Sorry, I can’t promise that it will happen soon (or even at all).

There is an easy workaround for this though. When you click on a Personal Search in desktop layout you’ll notice the URL:

/scp/tickets.php?queue=20

Therefore, your staff can easily create bookmarks in their mobile web browser for their Personal Searches.

I hope this helps.