Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade problem with 1.7.3 to 1.8 #949

Closed
alienzrcoming opened this issue May 25, 2014 · 3 comments
Closed

upgrade problem with 1.7.3 to 1.8 #949

alienzrcoming opened this issue May 25, 2014 · 3 comments

Comments

@alienzrcoming
Copy link

I've been trying to complete this upgrade and keep running into issues. A recap of my latest issue of the day follows. Did a 'git clone https://github.com/osTicket/osTicket-1.8 .', disabled the ldap plugin (bc this breaks auth after every upgrade attempt), copy over the files from the git cloned 1.8 source code, loaded up the upgrader, clicked 'Upgrade Now!', get this:

--snip
Fatal error: Uncaught exception 'Exception' in /var/www/osticket/include/class.orm.php:189 Stack trace: #0 /var/www/osticket/include/class.dynamic_forms.php(119): VerySimpleModel->save(false) #1 /var/www/osticket/include/class.dynamic_forms.php(133): DynamicForm->save() #2 /var/www/osticket/include/upgrader/streams/core/dad45ca2-61c9d5d7.task.php(15): DynamicForm::create(Array) #3 /var/www/osticket/include/class.upgrader.php(371): DynamicFormLoader->run(30) #4 /var/www/osticket/include/class.upgrader.php(122): StreamUpgrader->doTask() #5 /var/www/osticket/scp/upgrade.php(39): Upgrader->doTask() #6 {main} thrown in /var/www/osticket/include/class.orm.php on line 189
--snip

Debian Wheezy
MySQL 5.5
php 5.4

@greezybacon
Copy link
Contributor

@alienzrcoming are you able to continue the ugprade after this bug? This should be fixed, but should not prevent the upgrade from completing if manually continued.

@alienzrcoming
Copy link
Author

was unable to continue. i was unaware of any manual steps to take after this point. i finally gave up on 1.8 and was able to successfully upgrade to 1.9 after finding that it was listed as the new stable.

@greezybacon
Copy link
Contributor

Interesting. I've seen this before. Maybe the bug is specific to 1.8.x?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants