Upgrade pathway from v1.15.6 to 1.16.1

nicksweb

Just checking it's possible to update from 1.15.6 to 1.16.1 provided I've got PHP8 access? From reading I can not quite work it out.

Current Service Information is below and if it's possible I was going to upload the 1.16.x code base and switch on PHP8.

Server Information
osTicket Version v1.15.6 (1a64b84) — Up to date
Web Server Software Apache/2.4.41 (Ubuntu)
MySQL Version 8.0.28
PHP Version 7.4.28
PHP Extensions
gdlib Used for image manipulation and PDF printing
imap Used for email fetching
xml XML API
xml-dom Used for HTML email processing
json Improves performance creating and processing JSON
mbstring Highly recommended for non western european language content
phar Highly recommended for plugins and language packs
intl Highly recommended for non western european language content
fileinfo Used to detect file types for uploads
zip Used for ticket and task exporting
APCu Improves overall performance
Zend Opcache Improves overall performance
PHP Settings
cgi.fix_pathinfo "1" is recommended if AJAX is not working
date.timezone Australia/Brisbane
Database Information and Usage
Schema artline (127.0.0.1)
Schema Signature add628927ee030469f5d3272ebda1e16
Space Used 6.83 MiB
Space for Attachments 0.02 MiB
Timezone AEST (Interpreted as Australia/Melbourne)

nicksweb

Actually, I may have just found the answer, it looks like it's not currently possible according to the Upgrade and Migration guide? https://docs.osticket.com/en/latest/Getting%20Started/Upgrade%20and%20Migration.html

nicksweb

KevinTheJedi

@nicksweb

No, that's saying you cannot upgrade to newer versions if you are using osTicket pre-1.6. v1.6 is extremely old so you can ignore that statement.

Anyways, it's literally so simple. You download v1.16.1, unzip it, make full backups of your current site files and database, upgrade to PHP 8.0, copy over all the v1.16.1 files from upload/ to your running site, login to osTicket, and run the upgrader. If anything goes wrong (which it shouldn't) then restore everything from backup and retry.

Cheers.

nicksweb

KevinTheJedi Thanks for that - I re-attempted the upgrade as the first time I ran it it failed (My error) - Turns out my plugin's weren't up to date enough and wasn't being tracked in my PHP-FPM error logs. Which is where I had been checking for what was amiss. So, all I had loading up was a white page until I resolved the plugin's issue with FS and the 2FA plugin. The upgrade process worked like a charm though once the plugin issue was sorted.