Release Candidate 1 for osTicket 1.14 released

The developer KevinTheJedi just announced the release of a new version of osTicket.  Version v1.14-RC.1.  This version is a Release Candidate for the forthcoming v1.14.

This new version has some long awaited features:

  • Ticket Merge – this feature allows you to combine two or more Tickets so that their threads will all be in one single (Parent) Ticket.
  • Ticket Link – this feature allows you to group tickets together (with out actually manipulating any Tickets).
  • Schedule and Business Hour SLAs – this feature expands the pretty basic SLAs that have been in osTicket for years.  It allows you to specify hours of operation, holidays, etc.
  • Expanded Print View – This improves the Print feature to be able to include ticket events in the threading.

As a reminder: RC means Release Candidate.
A release candidate means that while we think its pretty stable and usable, it is being released to be tested.
Release Candidates should not be used in Production Environments.

You can download this new RC release at https://osticket.com/download

Source: https://forum.osticket.com/d/95397-osticket-v1-14-rc1-released

osTicket 1.12.1 Released!

A new stable version of osTicket has just been released version 1.12.1. It also introduces some really useful new features including editing task threads, adding and removing Collaborators with out a page refresh.  Update: the new version does not have any database format changes, so the upgrader will not run [since it is not needed].

Here is an overview of all the new features and bug fixes included:

Enhancements

  • issue: Queue Sort Title No Validation Error (029b0f2)
  • Issue: Tickets Visibility (60aa7b8)
  • task: Implement edit of task thread (394ddee)
  • Reformat Incorrect Reply-To Headers (e9dda94)
  • DatetimeField: Add jquery-ui-timepicker-addon (dbff3b2)
  • Add/Remove Collaborators Without Refresh (5a5044a)

Improvements

  • issue: API Unexpected Data Warnings (4f68eb9)
  • Double semicolon removed (bacd836)
  • Empty extra in list_items (1309a6c)
  • Issue: Ticket Alerts vs Dept Recipients (581f1f9)
  • issue: iFrame Single Quotes (4b59b4f)
  • issue: PDF Squares Instead Of Text (69c5095)
  • issue: Class Format Disposition Misspelling (1d3f1a3)

Performance and Security

  • Remove File Type Override (539d343)
  • Validate integrity of uploads (eba6fb9)
  • issue: Rogue Closing div Breaks HTML Thread Tree (3bb4c0a)
  • xss: Install Form (c3ba5b7)
  • security: CSV Formula Injection (9981848)
  • security: HTML File Browser Execution (Windows: Firefox/IE) (33ed106)

As always the new stable can be downloaded from osticket.com/download.

But wait there is more! They also released a maintenance release for the 1.10 series v1.10.7.

The release notes for this are here:

https://github.com/osTicket/osTicket/releases/tag/v1.10.7

osTicket support

So you’re running osTicket version 1.11.x or 1.11-rc1 and you don’t want to upgrade it to current (1.12). Well if that is you then I have news and it is probably news that you are not going to like.  Due to the security issues in the 1.11 branch support for it has been discontinued effective yesterday 4/24/2019.

So what does this mean?  It means that support for that branch no longer exists.  However, there is some good news, as this means the support for 1.10.x has been extended until the next major release.  That means you can expect more maintenance releases for the 1.10 branch until support for it drops off (with the next major release).

Here is the breakdown:
1.12: support active
1.11: support ended on April 24, 2019
1.10: support active
 1.9: support ended on Feb 06, 2019
 1.8: support ended on Nov 1, 2016

osTicket 1.12.0 Released!

A new stable version of osTicket has just been released version 1.12.0. It also introduces some really useful new features including ACL (Access Control List) and iFrame support.  Update: the new version does not have any database format changes, so the upgrader will not run [since it is not needed].

Here is an overview of all the new features and bug fixes included:

Enhancements

  • issue: Upgrader Wrong Guide Link (#4739)
  • iframe: Allow Multiple iFrame Domains (#4781)
  • variable: Complete Thread ASC or DESC (#4737)
  • issue: Strip Emoticons (#4523)
  • feature: ACL (Access Control List) (#4841)

Improvements

  • issue: Maxfilesize Comma Crash (#4340)
  • issue: System Ban List (#4706)
  • queues: Fix compatibility issues with newer jQuery (#4698)
  • filedrop: Fix file drag and drop (#4719)
  • issue: PHP 7.2 Plugin Delete (#4722)
  • issue: Local Avatar Annotation (#4721)
  • Selected Navigation Item (#4724)
  • Issue: Attachments on Information Fields (#4730)
  • issue: No Save Button On Quicknotes (#4706)
  • Issue: Duplicate Tickets in Closed Queue (#4736)
  • issue: APC CLI (#4731)
  • users: Fix seaching of users (#4741)
  • issue: Custom Column Org Link (#4755)
  • issue: Internal Note Ignored (#4745)
  • issue: PHP 7.2 Ticket Status (#4758)
  • issue: Canned Response Variables (#4759)
  • issue: FAQ Search Results (#4771)
  • issue: FAQ Return Errors (#4772)
  • Queue Columns (#4785)
  • issue: Duplicate Form Titles (#4788)
  • Issue: Exporting Tickets (#4790)
  • issue: Organizations Users Sort (#4806)
  • issue: Multilingual FAQ Category w/ Parent (#4812)
  • issue: Task Print PDF (#4814)
  • Issue: MPDF Export PHP < 7.0 (#4815)
  • Quick Filter Fixes: (#4728)
  • Assignment Restriction Issue (#4744)
  • Issue: Saving Checkbox Values (#4798)
  • Issue: Choosing Fields to Export (#4797)
  • oops: Thread Variable Fatal Error (#4820)
  • oops: Emojis Strip Korean (#4823)
  • issue: iFrame On Install (#4824)
  • Issue: Ticket Export Headers (#4796)
  • issue: Organization Ticket Export No Filename (#4825)
  • MPDF Issues (#4827)
  • issue: sendAccessLink On NULL (#4828)
  • issue: sendAccessLink On NULL v1.11 (#4829)
  • Update README.md (eccc57ae5f4180)
  • issue: iFrame Single Quotes (#4844)
  • issue: Choice Validation Accept Punctuation (#4847)
  • issue: ACL Move To Inc Files (#4848)
  • Issues since v1.11 release (#4850)
  • PJAX: Increase default timeout (#4855)
  • Mime Decode – Encoded char (#4851)
  • MPDF Tasks (#4856)
  • issue: .eml/.msg Attachments (#4857)
  • issue: Task EstDueDate (#4862)
  • Bug fixes and enhancements for v1.11 (#4863)
  • Mailer: Allow for ability to pass -f option as from_address (#4864)
  • Ticket Link: Always return a link (#4865)
  • Minor Fixes (e628373)

Performance and Security

  • xss: XSS To LFI Vulnerability (#4869)
  • jquery: Update Again (#4858)

As always the new stable can be downloaded from osticket.com/download.

But wait there is more! They also released a maintenance release for the 1.10 series v1.10.6. The release notes for this are here:

https://github.com/osTicket/osTicket/releases/tag/v1.10.6

 

Backups aren’t just for breakfast anymore

It seems that the new site database failed to back up correctly for the past 4 months. So in order to get the site back up and running again I had to re-import an older version of the database. This means that all the work that I have done on the site is gone forever. Needless to say that it will take me a while to re-write all the posts that are missing, and get the site back to where it was.

Please take a minute and make sure that your backups are running correctly. Thank you.

Welcome to day 0.

UPDATE: Original backup restored was from 2018/10/03. I’ve just restored the site to a newer backup of 2018/10/31.

Upgrading osTicket 1.10.x to current 1.11.0

So you’re running osTicket version 1.10.x and you want to upgrade it to current which as of this writing is 1.11.0, and you need a little help. Well, you’ve come to the right place.  One very important thing to note: contrary to what the osTicket FAQ at https://osticket.com/faq says, you need a newer version of PHP than 5.3.  I would recommend any version from 5.6 to 7.2.  So if you have 5.3 go upgrade first.  This version introduces support for 5.6 to 7.2.  As of this writing I am running 7.2.15 in production on multiple sites.

If you have ever upgraded osTicket in the past your experience this time will not be much different than it was previously.

Before you start it is important to mention that if you have installed any mods or performed any custom coding (including changing graphics, translations, etc.) that upgrading will not be as simple as it sounds in this article and you will lose all the modifications that you have made. You could very well break your site or at the very least lose some of the functionality that you currently enjoy.

1. Put the site into offline mode.

To do this log into your site and navigate to Admin panel -> Settings -> Helpdesk Status and toggle the radial to “Offline (Disabled)”, scroll down and click “Save Changes”.

note: I personally leave the site open, but navigated back to the Client panel.

2. Make a backup of your database.

There are various ways to do this and I am not going to cover all of them. My preferred way is to use command line. You can do this by simply issuing a command similar to:

mysqldump -u userName -p databaseName > fileName.sql

note: change userName to your DB username, databaseName to the name of your DB, and fileName to what ever you want to call the backup file.

One other easy way to do backups (on windows) is to use MySQL Admin (deprecated) or MySQL WorkBench.

3. Make a backup of your site.

Once again there are various ways to achieve this. I trust that you know how you want to do it, just make sure that you do it.

NOTE: You should never rely on your ISPs automatic backups,
always make your own backups before upgrading!!!

While you are here, you may want to also make a separate copy of your /include/ost-config.php file. This file contains the database connection information.

4. Download the latest version of OSTicket. osticket.com/download.

Note: If you are running any plugins (especially any of the auth plugins), you should also download the new versions of those.

5. Extract it to your OSTicket directory. Yes, you can and should have it over write existing files.

Note: If you also downloaded upgrade to your plugins make sure that you put there in /include/plugins at this point.

6. re load your web page. When the page loads you should be looking at the image below. Since this is an upgrade you should be looking at the upgrader. This is important to note since the Upgrader looks different from the Installer.

fig 1 – upgrader
click image to enlarge

 

 

At this point you should be able to click the “Start Upgrade Now” button. The next screen should look like this:

fig 2 – upgrader, page 2
click image to enlarge

 

 

Unless you have a reason not to, go ahead and click the “Do It Now!” button. This should result in a small rectangle popping up in the middle of your screen like this:

fig 3 – upgrader upgrading

 

 

Once it has completed you should be looking at the following page:

fig 4 – upgrader, upgrade completed
click image to enlarge

 

 

Now, if you click on the Settings tab you should be looking at the following:

fig 5 – admin panel, version
click image to enlarge

 

 

While you are here, if you had previously put the site into Offline mode, you should put it back in Online mode (don’t forget to click Save Changes at the bottom of the page).

Congratulations! You’ve upgraded from 1.10.x to 1.11.0, however you are not quite finished yet.

7. Time for post install clean up.

Go into your OSTicket directory and delete [or rename] the setup folder. It is not needed for a live or production site and should never be left on a publicly accessible server. I recommend that you delete it, but some people like renaming it to keep the files around should they need it again. For the record you should not need it again, and if you did you can always just re-download the distribution archive. This will also get rid of the annoying nag screen at the top of the site.

Next go to your /include folder and make the ost-config.php read only. How to do this varies by OS.

That’s it for the “hard” stuff. I recommend that you take another backup of your site (both database and files) since you just made major changes to the site.

Enjoy!

ntozier / tmib

 

p.s. the instructions for installing and configuring the LDAP/AD plugin really haven’t changed.

osTicket 1.11.0 Released!

After a long wait the new stable version of osTicket has just been released version 1.11.0. For the security conscious this is great news since it finally adds support for PHP 7.1 and 7.2. It also introduces some really useful new features including the long awaited Custom Queues that we saw the preview of back in the 1.11-rc1 (Release Candidate) and the long awaited whole thread template variable.

Here is an overview of all the new features introduced in rc1 and the new stable:

1.11.0-rc1 – Major New Features

  • Create Ticket or Task from Thread Entry
  • Custom Columns/Custom Queues
  • Inline Edit
  • Ticket Referral
  • Support CC (Collaborators)
  • Export Agent CSV
  • Department Access CSV
  • Archive Help Topics/Departments
  • Nested Knowledgebase Categories

1.11.0 – Major New Features

  • Release Ticket Assignment (d354e09)
  • Require Help Topic To Close Ticket (#4400)
  • Disable Collaborators On Reply (#4420)
  • Complete Thread Variable (#4613)
  • Public Mark As Answered/Unanswered (#4612)

The number of bug fixes and enhancements these two releases have is fairly staggering and too long to list here. Please take a look at the github release notes for those. They can be found here:

1.11.0-rc1 at:

https://github.com/osTicket/osTicket/releases/tag/v1.11.0-rc1

1.11.0 at

https://github.com/osTicket/osTicket/releases/tag/v1.11

But wait there is more! They also released a maintenance release for the 1.10 series v1.10.5. The release notes for this are here:

https://github.com/osTicket/osTicket/releases/tag/v1.10.5

tmib.net undergoing changes

Good afternoon all,

I’ve just completed migrating my site from Drupal to WordPress. and it seems that resulted in a loss of all images, and some of the posts and fonts didnt transfer well either.  While I plan to go back through and remove bad formatting I doubt that I will take the time to re-cover the images, but chances are most of them were really old and no longer needed.  New posts going forward will of course have new images. 🙂

Installing osTicket 1.10.4: Troubleshooting MySQL8 and PHP older than 7.1.16

MySQL 8 was released recently (to this writing) and of course that means people are going to start using it.  Since I have seen a couple posts on the forums with people using MySQL 8 I decided to fire up a new VM and install the following:

  • OS: Windows 2012 R2
  • Webserver: IIS 8
  • MySQL 8.0.12
  • PHP 5.6.31

note: PHP 5.6 is still the recommended version of PHP for osTicket until 1.11 is released.  You should not have this problem if you are running PHP 7.1.16+ or PHP 7.2.4+ but since osTicket does not support those versions yet.

After checking to make sure that: IIS was serving pages and PHP was working in IIS it was time to download and install osTicket.  The new website downloader is neat and allows you to download a languages and plugins together which can be a time saver. As a reminder always install osTicket with out any language packs and then add your desired language packs.

Running the installer resulted in the following error:

Database Connection information `Unabled to connect to MySQL Server: Server sent charset unknown to the client.`  Please report to the devs

To fix this you will need to locate and edit your MySQL configuration file (my.cnf or my.ini). Since this is a new MySQL 8 installation under windows it is at: C:\ProgramData\MySQL\MySQL Server 8.0\my.ini.  Once you located the file locate # character-set-server=.  Directly after it add the line:character-set-server=utf8

Next you will need to restart MySQL.  You might be able to do this with MySQL WorkBench or services.msc.  My server had some patches that installed so I just restarted the server for the patches to finish.

Running the installer again of course resulted in another error message:

Database connection information `Unable to connect to MySQL Server: The server requested authentication method unknown to the client`

Starting with MySQL 8.0.4, the default authentication plugin for MySQL server was changed from mysql_native_password to caching_sha2_password. There are two things that you need to do in MySQL to fix this. First: if you are running an older version of PHP (pre 7.1.16) you will need to set default_authentication_plugin=mysql_native_password in my.cnf. Restart the server.

Next you will need to edit the user account. I could not do this in the most recent version of MySQL WorkBench using the ui. You can do this one of two ways:
1. delete and recreate the user. Make sure authentication is set to ‘Standard’. Make sure you give the same permissions back that the user had.
2. run the following SQL Query (edit this for your user)
alter user 'username'@'localhost' identified with mysql_native_password by 'password';

After doing this the installer ran fine.