[stevland]

Yikes! I’m at a loss. Thanks for letting me know.

[stevland]

Hi @jdelisle,

I logged into your installation and fixed the “long answer” fields. I also took the liberty of fixing a few other minor layout irregularities that I observed in your forms.

For now I put my tweaks in your Custom CSS.

These tweaks will be integrated into the next release, so the next time you upgrade you can remove the custom code from Theme Options > Custom CSS.

Regarding the fact that the user-submitted content is not editable on the Ticket View page is definitely a glitch with osTicket Awesome. Unfortunately, I do not have time to deal with this right now, but I have added it to my list.

[stevland]

Você já tentou limpar o cache do navegador?

—

Have you tried clearing your browser cache?

[stevland]

@lafr That is exactly what I intend on doing once things begin to settle down in the next month.

@james Thank you for your kind offer of support. I just posted the 1.15 update on the Downloads page if any of you guys are eager to give it a try.

In the meantime I am going to start working on the next two releases (v1.14.5 & v1.15.1), which should be super easy now that I got this major release out of the way. I won’t be announcing anything until those are also posted.

[stevland]

It is totally possible, and it isn’t hugely complicated. But it is beyond the scope of what I can offer to do for free.

You can easily figure out how web fonts are embedded on your main website and copy the same functionality over to osTicket Awesome. It might look something like this:

@font-face{font-family: 'Your Font'; src: url('../../your-main-website/assets/font/yourfont-webfont.eot');

If you already have the fonts stored on your server you could simply call them using that path. Then it would just be a matter of overriding the fonts you want to change using CSS. Here is a quick example of what it would look like.

body.client-side,
body.client-side #landing_page h1,
body.client-side #landing_page h2,
body.client-side #landing_page h3 {
    font-family: 'Your Font', sans-serif !important;
}

If all of your mods are CSS-based (like the ones above) you can drop them all in Admin Panel > Theme > Custom CSS. That way the mods will persist after an update.

But keep in mind that if you end up having to modify any files you will want to keep a note of what you did, because you’ll need to manually re-apply the same tweak(s) after any update.

If all of this is beyond your skillset you can always hire someone to implement this for you using a service such as freelancer.com.

Good luck!

[stevland]

That looks really useful.

But it is beyond what I can support, but I’ll give you a couple thoughts.

When you installed osTicket Awesome, did your Pfad_zu_osTicket change? 

The path to the User Directory in osTicket Awesome is still /scp/users.php

If you followed the osTicket Awesome installation instructions you should have a backup of your original osTicket. So you could try using that path (e.g. https://yourdomain.com/support-old/scp/users.php) to see if that works.

That’s all I can think of. Good luck.

[stevland]

@supportcomplavis-de,

Thank you for bringing this to my attention.

It appears that an upstream change of code in osTicket resulted in my fix being overwritten somewhere along the way.

It will be fixed again in the next releases. But if you want to manually fix it right away you’ll look for the following code in /include/staff/ticket-view.inc.php around line 1007:

<a class="inline-edit" data-placement="bottom" data-toggle="tooltip" title="<?php echo $title; ?>"
href="<?php echo $href; ?>">

which you’ll change to:

<a class="ticket-action inline-edit" data-placement="bottom" data-toggle="tooltip" title="<?php echo $title; ?>"
href="<?php echo $href; ?>">

[stevland]

Eché un vistazo y así es como funciona osTicket por defecto. Ningún archivo adjunto está incluido en el correo electrónico. Probablemente haya una forma de agregarlo a la plantilla de correo electrónico. Pero sería una pregunta para hacer en el foro de osTicket.

—

I had a look and this is how osTicket works by default. Any attachment is not included in the email. There is probably a way to add it to the email template. But it would be a question to ask in the osTicket forum.

[stevland]

Thanks for your support @webtekpc!

[stevland]

That’s the spirit! 😀

[stevland]

I see that the priority colors are not showing up as intended. 

Is this a new installation? You may need to clear your browser cache.

But if you are actually asking how to modify the colors to something of your own choosing, I would have to look into it. I can’t quite recall but I don’t think it is a simple answer.

[stevland]

Hi @webtekpc,

Thank you for your concern and sorry for my absence.

Also, thank you for sharing your solution.

[stevland]

Nope, sorry those are my only suggestions.

But again, this is actually an osTicket question. By asking it here you on have the potential of receiving a small fraction of the suggestions that you might receive if you asked in the osTicket Mods and Customizations forum.

[stevland]

@qcmadmin

Everything you’ve said is accurate and completely true.

I apologize for having disappointed you.

I’m catching up and hopefully I will have some new releases very soon!

[stevland]

Leider unterstützen wir das Google 2FA-Plugin derzeit nicht.

Die Version für Version 1.15 (die in Kürze verfügbar sein wird) enthält eine integrierte 2FA-Lösung. Vielleicht reicht das für Ihre Anforderungen.

Wenn Sie das Google 2FA-Plugin noch benötigen, lassen Sie mich wissen, woher Sie es haben, und ich werde sehen, ob ich es mit osTicket Awesome zum Laufen bringen kann. Aber keine Garantie!

—

Sorry, we do not support the Google 2FA plugin at this time.

The release for v1.15 (which will be available soon) will have a built-in 2FA solution. Perhaps that will be enough for your requirements.

If you still need the Google 2FA plugin, let me know were you got it from and I will see if I can make it work with osTicket Awesome. But no guarantee!