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
-
-
dleffler June 3rd, 2012 @ 12:19 PM
- Assigned user set to “dleffler”
- Milestone set to “2.0.8”
- Milestone order changed from “180” to “0”
-
dleffler July 27th, 2012 @ 01:17 PM
- Milestone changed from “2.0.8” to “2.0.9”
- Milestone order changed from “9” to “0”
-
dleffler August 3rd, 2012 @ 02:53 AM
- State changed from “open” to “resolved”
- Milestone order changed from “3” to “0”
We'll close this one out. Best to KEEP the version of the saved database intact. The upgrade should NEVER assume anything and run through all the upgrade scripts based on the db version.
-
dleffler August 11th, 2012 @ 02:44 PM
- State changed from “resolved” to “open”
I'll reopen this to do the following:
- we'll report the eql stored version at the end, with a link to perform an immediate upgrade...this might be performed automatically via the version check process?
- we'll also suggest they might want to 1) install the older version (with a link to downloads), 2) re-import the eql file, then 3) install the current version and do an upgrade to bring in/convert any deprecated tables.
This is necessary since we are deprecating some old 1.0 defintions so those tables are no longer available, therefore can't be imported.
-
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
dleffler
expNinja