So with the end of support for POP/IMAP in Office 365 I've been tasked to update the OSTicket-site my company uses for support to 1.7 (just 1.6.3 now pending the final release) for official OAUTH support and I've kinda run into a reverse chicken-or-the-egg situation over the update from PHP7.4 to PHP8.0.
Currently the site uses OSTicket 1.15.8 on PHP7.4 with PHP8.0 (and 5.6) installed under Debian 10 "buster" with the latest Apache2 for it, but changing to/requiring PHP8.0 is preventing me from updating OSTicket to 1.16.3 or 1.17-RC1. I've tried two methods (naturally after backing up both the site and database) to perform this site update;
1 - Just copy the contents of the "Upload" directory in the extracted OSTicket download into the site's directory, over-writing all the old files, and then the ost-config.php settings file from the previously mentioned site backup
2 - Erase everything in the site directory, copy the contents in the "Upload" directory from the extracted OSTicket download into it and finally the ost-config.php from the site backup
Method 1 worked when I updated the site from 1.9.12 to 1.15.8, but it doesn't work now. I get nothing when I try to access it with a web browser to run the site update. Either when I've got PHP7.4 or PHP8.0 active. Method 2 gets me a little closer as I do get the into the site update menu when I've got PHP7.4 active, but it won't let me run the update as 1.6.3 requires PHP8.0. When I then try switch to PHP8.0 (simple "sudo a2dismod php7.4", "sudo a2enmod php8.0" and "systemctl restart apache2") it completely stops working and I can't get the updater, or anything else in OSTicket to work.
I suspected that it could be php8.0 just not working, but when I add a little addition we use with a landing page written in php with our company logos and a few notices about our activity hours etc. that works just fine. So did I miss something crucial and/or am I just being an idiot with something?
