Add old database fix scripts to migration process
Reported by dleffler | May 3rd, 2011 @ 03:06 PM | in Beta 3
Several anomolies in the old 0.9x database can prevent all the data from migrating successfully. Can appear as modules not showing up in aggregation, etc...). These existing scripts would be executed or included as a part of the save migration database settings action.
Comments and changes to this ticket
-
expNinja May 4th, 2011 @ 12:39 AM
- State changed from “open” to “resolved”
(from [670b6675ab34e0c5531de1fa8939dd572b9f3c03]) Added some error checking and fixes prior to migration of old database.
Now gives immediate feedback on unusable connection parameters. Runs 4 checks & fixes on old database prior to migration that aids migration (esp for module aggregation). Also makes the migration process more of a wizard since you move to the next step after setting old database parameters.
[#167 state:resolved] https://github.com/exponentcms/exponent-cms/commit/670b6675ab34e0c5...
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
People watching this ticket
expNinja
Tags
Referenced by
-
167
Add old database fix scripts to migration process
Now gives immediate feedback on unusable connection param...