Bug: need to do install tables before running upgrade scripts from slingbar
Reported by dleffler | March 15th, 2013 @ 02:04 PM | in 2.2.0beta1 (closed)
We need to ensure the tables exist before running selected upgrade scripts since this has already occurred in actual upgrade
Comments and changes to this ticket
-
dleffler March 15th, 2013 @ 02:06 PM
This MAY actually allow us to do an in-place upgrade instead of having to drop to the installer, though that method will still work. If that's the case, then we'll have to do something to make sure we do all the non-optional upgrades?
-
expNinja March 15th, 2013 @ 04:22 PM
- State changed from “new” to “resolved”
(from [7a1fc04dc9f7bd706c6895be7d9cb7ee0c37a8ee]) Running upgrade scripts from slingbar now first updates tables before running [#964 state:resolved] https://github.com/exponentcms/exponent-cms/commit/7a1fc04dc9f7bd70...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
expNinja