In case anyone else has some problems with doing this upgrade like I did, here's what all I had to do.

  1. As always BACKUP YOUR DATABASE AND CODE. ? (I had to drop database and reupload application several times before figuring this out for two osTicket applications on our servers.)

  2. Download the latest 1.9.x that is stable.

  3. Download the latest 1.10.x that is stable.

  4. Download the latest 1.11.x that is stable.

  5. Upload your existing 1.6 application AS IS.

  6. import your existing database AS IS (if moving to a new server)

  7. Upload everything from the 1.9.x upload folder to start the upgrade process.

  8. Fix any fatal errors that you find in the logs. (I had to fix some call-time pass-by-reference and things like that in the 1.9.x release.

  9. Login to the /scp panel with an admin account and click upgrade. (if it fails repeat 6-7 and fix errors)

  10. If the process was successful, then repeat 7,8,9 for the 1.10.x release and then the same for 1.11.x release.

Hope this helps because I spent a few hours doing this for two different applications.

The one thing that I would add to this is that the upgrader is designed to work from 1.6ST to the version that you downloaded. If you are running a 1.6RC-# then you need to update to 1.6ST first. I've gone from 1.6ST to 1.9.x personally but have not personally tested going directly from 1.6ST to 1.11 but you should be able to do it. tmib.net has some of the tutorials that I have written for migrating from version X to version Y. I seem to recall that there are some extra files left over with some of the earlier ones.

    5 days later

    ntozier I was on 1.6ST so I'm not sure what breaks. I think going to 1.9.x and then to 1.11 works as well, to be extra safe, I'm going to 1.9, 1.10, 1.11 in succession. Would be interesting if someone else tested this as well.

      Write a Reply...