2

For this particular quandary, this worked: Add this line to the top of the SQL file: SET FOREIGN_KEY_CHECKS = 0; Source: http://devot-ee.com/add-ons/support/stash/viewthread/5700 If you see this problem and the above solution doesn't work, check this thread as well: http://devot-ee.com/add-ons/support/stash/viewthread/10311


1

You can find an outline of what is needed in the answer to a similar question asked a few months ago. expression engine upgrade from 2 to 3 to 4 HTH.


1

Never ever do direct EE1 to EE3. First of all upgrade EE1 to EE2. That will make necessary changes to your database. (Remember change all the plugins with EE2 version otherwise backend and/or frontend may crash.) After upgrading it to EE2, upgrade your server then upgrade site to EE3. Remember to: Always take a backup copy of your site. Its good to ...


1

The true answer is unfortunately "no". There have been some attempts in this vain by EE addon developers and there may be some "creative" solutions out there but there is not anything that I'm aware of which makes this process easy.


1

The closest I have seen to something like this is detailed in a blog post: "Deploying ExpressionEngine based site" by Krasimir Tsonev. He outlines steps to log all queries in an environment, writing them to files. The queries can then be run, as migrations, by executing the saved queries on your other environment's database. Scroll down to the "Database ...


Only top voted, non community-wiki answers of a minimum length are eligible