Closed shennyg closed 3 years ago
Same issue here!
Thanks for reporting this. Just fixed for the next release.
To get the fix early, change your craftcms/cms
requirement in composer.json to "dev-develop as 3.6.9"
and run composer update
.
Craft 3.6.10 is out now with a fix for this.
I am still experiencing this issue when trying to upgrade from 3.6.1 to 3.7.0 (as it applies previous migrations in turn). No idea how to skip 3.6.9 and go straight to 3.6.10, if it is indeed fixed...
@andymakkolli Yeah it resurfaced in 3.7.0, sorry about that.
We just released 3.7.1 with a fix (225f24e53c00635fd282ca565a6c83e7c59a401c). You’ll need to restore a database backup from before the 3.7 update, then composer-update to 3.7.1 and this time it should work.
Description
Upgrading from 3.6.7 to 3.6.9 doesn't create the required
Table::PROJECTCONFIGNAMES
/ 'projectconfignames' table early enough.It's failing here: https://github.com/craftcms/cms/commit/1dee096ba7b5cb277d3768ac41c174b211ea5858#diff-e39eae0845ed5714c6f2c936b244be3dfe3818075cc4b02f200edae0d0889cf3R1693-R1696 because this migration cannot be run: https://github.com/craftcms/cms/commit/1dee096ba7b5cb277d3768ac41c174b211ea5858#diff-92ced046c1bcc6b20dd555c2895b8224861305f8e396378c54ffb00f7efc9527
Steps to reproduce
If you manually add the table:
Migrate runs but fails:
Additional info