Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

1.9.0 to 1.9.1 upgrade problems, suggestions

Hey guys,

The upgrade from 1.9.0 to 1.9.1 aborted due to a timeout. Now the upgrader throws an error in the logs and each time I resolve that error it finds another one. An example:
[core]: Upgrader Error

[ALTER TABLE `ost_filter` ADD `topic_id` int(11) unsigned NOT NULL default '0' AFTER `form_id`] Duplicate column name 'topic_id'

My suggestion would be to add a WHERE NOT EXISTS or something like that to the SQL query so an existing table or a half finished upgrade doesn't kill the whole installation.

Maybe you could also catch the error and log it but still continue. If the end result is really not working, you could implement other checks to see if the newly added tables behave correctly.

Also, an auto backup would be much appreciated.

Comments

  • There are no database changes between 1.9 and 1.9.1... so the upgrader wouldn't have run. (I just performed the upgrade again on another site just to make sure that I was missremembering.
  • Well, I had version 1.9.0 but it seems that the upgrader ran the database upgrades from 1.8.9 (?).

    Is there a method to override the upgrader manually?
  • The only time that I have ever seen the upgrader trigger was when it needs to.  So if it needed to then you didn't have 1.9.0.  As a side note there is not and never has been a version 1.8.9.  There is no way to override the upgrader manually.  Well I guess you could run the sql comments manually if you wanted to. /include/upgrader/streams/core

    You would have to look through and figure out which ones you need to run based on the actual version of the database.
Sign In or Register to comment.