Generally speaking many of the previous FAQ answers [for former versions of osTicket] some times still apply to the current version. The line numbers will be wrong, but the information is usually still good. If you do not see an answer to your question please check out the older versions of this FAQ and/or post on the osTicket forums.
Software related items. Such as software review, comments, etc.
If you downloaded the original 1.9 release please download it. There were several quick fixes that were bundled afterwards.
As of today you can now download 1.9 codenamed "Whispers" from the osticket.com/downloads page.
Here is a list of the enhancements, bug fixes, and Security updates:
So you wrote a mod or a plugin and want to add some configuration options directly to into the osTicket Admin panel. This is a short tutorial on how to add a setting to osTicket 184.108.40.206, and then have your mod (or plugin) check that setting.
First off realize that modding osTicket can result in the breaking of your site, and you should really perform a backup of both the site and your database prior to making changes.
One of the [I feel] less documented features of osTicket is the ticket API. This API has been built into osTicket for quite some time and allows you to write your own html forms and push the data to osTicket to open tickets. This means that you could write a contact block for your web page and have it submit to osTicket directly, or if you have another piece of software that can run a script you can write your own custom script to open tickets from that software. Example a network monitoring system (like NOCOL/SNIPS) could open a tick
There has been a lot of talk recently about some of the new features and the direction that osTicket is heading in. In the past I've mentioned that osTicket will have individual user accounts for clients. Today I get to share a little more about this coming feature! Jared (aka greezybacon) posted the following commit notes over on github a short time ago:
I have been running a Debian server here at work for a several years now mostly as a web server, but also as a way for me to have quick access to some of the old cli tools like whois, dig, etc. While running updates I ran across this error:
Fetched 199 B in 1s (122 B/s) Reading package lists... Done W: GPG error: http://debian.opennms.org stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 57801F6F5B9EFD43