Upgrading from 1.6 ST

deborahfitchett

I've inherited osTicket v1.6 ST from a very technically minded predecessor and it's run so well I've

never had to touch it before. Now, though, we've moved it to a new

server with PHP v5.6 and while everything else about it appears to run perfectly there,

our scheduled task to fetch mail using api/cron.php is failing. Running this script

in command line I see a slew of warnings and strict standards notices, along with a deprecated notice:> php.exe \api\cron.phpPHP Strict Standards: Non-static method Misc:() should not be called statically in \main.inc.php on line 101PHP Strict Standards: Non-static method Sys:() should not be called statically in \main.inc.php on line 146PHP Strict Standards: Non-static method Cron:() should not be called statically in \api\cron.php on line 20PHP Strict Standards: Non-static method Cron:() should not be called statically in \include\class.cron.php on line 39PHP Deprecated: Assigning the return value of new by reference is deprecated in \include\pear\Mail\mimeDecode.php on line 335PHP Strict Standards: Non-static method MailFetcher:() should not be called statically in \include\class.cron.php on line 24PHP Strict Standards: Non-static method Misc:() should not be called statically in \include\class.mailfetch.php on line 346PHP Warning: mcrypt_decrypt(): Key of size 15 not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported in \include\class.misc.php on line 51PHP Strict Standards: Non-static method Misc:() should not be called statically in \include\class.mailfetch.php on line 346PHP Warning: mcrypt_decrypt(): Key of size 15 not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported in \include\class.misc.php on line 51PHP Strict Standards: Non-static method Misc:() should not be called statically in \include\class.mailfetch.php on line 346PHP Warning: mcrypt_decrypt(): Key of size 15 not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported in \include\class.misc.php on line 51PHP Strict Standards: Non-static method Misc:() should not be called statically in \include\class.mailfetch.php on line 346PHP Warning: mcrypt_decrypt(): Key of size 15 not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported in \include\class.misc.php on line 51PHP Strict Standards: Non-static method Misc:() should not be called statically in \include\class.mailfetch.php on line 346PHP Warning: mcrypt_decrypt(): Key of size 15 not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported in \include\class.misc.php on line 51PHP Strict Standards: Non-static method Cron:() should not be called statically in \include\class.cron.php on line 40PHP Strict Standards: Non-static method Ticket:() should not be called statically in \include\class.cron.php on line 30PHP Strict Standards: Non-static method TicketLock:() should not be called statically in \include\class.cron.php on line 31PHP Strict Standards: Non-static method Cron:() should not be called statically in \include\class.cron.php on line 41PHP Strict Standards: Non-static method Sys:() should not be called statically in \include\class.cron.php on line 35PHP Strict Standards: Non-static method Sys:() should not be called statically in \api\cron.php on line 21So

the first question (which I'd have asked in a v1.6 category if there was one

is) - is there likely to be an easy way to fix this without upgrading? This would buy me some time to get more familiar with the system, figure out if any mods were installed, line up some support in case the database stuff is beyond my skillset, etc...Otherwise, can we reasonably upgrade from 1.6 ST directly to 1.9, or should we do it in stages?Thanks very much!Deborah

ntozier

You should probably downgrade from 5.6 to 5.5. There are a few known issues that have been posted about at github. You should shut off Strict Standards in your php.ini. PHP recommends that it be off on production servers. 1.6 is ancient at this point and no longer supported. PHP has changed a lot of things since 1.6 came out and a lot of the code is now deprecated in the newer versions. I personally have osTicket running If it were me I would just upgrade to 1.9 directly. There are a LOT of new features. Also make sure that you back up your database first.

deborahfitchett

Thanks very much! Will definitely shut off Strict Standards, and will have a go at the upgrade. Am a little hesitant to downgrade PHP just because it's taken us a while to iron out all the kinks in the first place, but good to know that if we have problems it may be something to try.