Bug: Determine best method to import an old (2.x) database/eql file
Reported by dleffler | May 14th, 2012 @ 09:28 PM | in 2.0.9 (closed)
This may not necessarily be a problem, but when having a current database (version) and them importing an older eql backup, the system will then hold the OLD database version and flag it for an upgrade...this is probably NOT a bad thing as the data may need to be converted/updated.
Comments and changes to this ticket
-
expNinja August 11th, 2012 @ 11:39 PM
- State changed from “open” to “resolved”
(from [2f729fd56042b8b756c2979f6d3f5dab72f9ab35]) Makes import an old (2.x) database/eql file more intuitive with instructions for failing to import all tables, how properly displays error messages, adds importing sample database from theme if available with a fallback to the system sample [#604 state:resolved] https://github.com/exponentcms/exponent-cms/commit/2f729fd56042b8b7...
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