Bypass the Upgrade Screen

parabarbarian

We recently acquired a company that uses OSTicket and Plesk for its helpdesk ticketing system. I was able to get Plesk working, create a URL for support, and installed osticket 1.12 (only revision Plesk offers). I then successfully imported the original database from an sql export. Now the admin page insists I have to upgrade.

Can this upgrade demand be bypassed?

I found out the revision on the other system is 1.10. Were there some changes between 1.10 and 1.12 that could cause this? If so, how can I downgrade?

RBGE

parabarbarian It's not really upgrading osTicket as such, as you've already done that by setting up v1.12. All this is doing is upgrading the database schema so that it supports the new features available in 1.12, and cannot be bypassed (you'd get all sorts of errorts if you did!).
If you want to use the old database without upgrading the schema, you'd need to use osTicket v1.10 - bear in mind, however, that this is end-of-life and no longer supported.

parabarbarian

Dang! The database was exported from 1.10 . Does that mean it cannot be imported into 1.12?

RBGE

parabarbarian That's correct in that it can't be imported without 'upgrading' it. It doesn't actually upgrade the data as such, just updates the schema so it can support the features in 1.12. The only thing to watch for here is that a 1.12 database cannot be imported back into 1.10, but as long as you still have the original this should be fine.

stevland

parabarbarian

Always keep a backup of the old database pre-upgrade database for a little while, just in case.

But absolutely proceed with the database upgrade. 99.999% of the time you'll have nothing to worry about.