Upgrade docs

JRogers

Could someone please point me to some upgrade docs that are current? The docs on the wiki are so out of date, it's sad. For example:Once you've overwritten the files, rename config.php to ostconfig.php (config.php is found in root osTicket directory).Well, there is no config.php, and the actual config file is ost-config.php, not ostconfig.php.So, I saved my own ost-config.php and dropped it back in after uploading the contents of the upload directory. Then I went to the site for the web installer to do its thing. It prompted me for my help desk URL and the DB information, like a new install. This should already be there, since my ost-config.php file is there.Is there a more current version of the upgrade procedure?Thanks.Jack

JRogers

Seems I may have stumbled onto the right procedure, and the upgrade is now in progress.Jack

JRogers

And now it's completed.I found a "setup" directory on the server, so I went to http:/setup and it recognized the previous installation. Then I simply followed the prompts.I don't know why it didn't work the first time, unless I somehow didn't get redirected to the correct setup page.My upgrade issue is resolved, but the docs really do need updating. If there's a more current version somewhere else, please let us know.Jack

ntozier

My upgrade docs are outdated. :(But I think that they are better than the wiki ones.http://www.tmib.net/upgrading-osticket-1812-current-19rc

JRogers

They are definitely better.To be honest, I did not overwrite my existing osticket directory. Since there's no separate "upgrade" bundle, no old files are required. So I start clean, as follows:Put the contents of the "upload" directory into a brand new "osticket.upgrade" directory.Got a DB backup.Copied my ost-config.php to the osticket.upgrade/include directoryRenamed "osticket" to "osticket.old", and then osticket.upgrade to "osticket" (this allows an easy backout if needed)Pointed my browser to http:/osticket/setupFollowed the promptsIncidentally, I always use the "--add-drop-table" option with mysqldump. It drops and creates every table before putting the data in it. That way, there are never any data conflicts.Jack

ntozier

Thanks for the feedback. I'll take it under consideration when I re-write the doc. :)

Chefkeks

* Renamed "osticket" to "osticket.old", and then osticket.upgrade to "osticket" (this allows an easy backout if needed)

We solved this in a different way... We have a directory named "osticket" on our server which is basically just a symbolic link to the real directory in the background e.g. "osticket_1.9.5.1".That way we can e.g. easily switch between versions (especially when no database upgrade was needed) to compare the old and the new version of the php files with the same database.And don't worry we take backups before such actions (apart from our normal "every 2 hour" backup of the database)