-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown column 'config' in 'field list' on Craft 2 -> 3 upgrade #5391
Comments
I seem to be able to coax it into working by setting a UPDATE: it got a little further but still barfed looking for a |
This exact issue is resolved now on the |
I'm getting this same error updating from 3.3.3.20 to 3.4. Should I open a new issue? |
Same for me! |
Seems like this issue occurs after migrations fail due failure of changing the project config because of read-only mode:
|
Can either of you find that error in your |
I had the same thing, but then updated to the latest 3.4x and all was well |
I'm on dev environment so I don't think it's in read-only mode. Does this help or would you like the entire file?
|
For me it was in
This was on the first run of the migration. When running the migration again it was:
|
I think I got it: When running the
This fails for me because on cms/src/services/ProjectConfig.php Lines 1706 to 1723 in ad53b26
This fails because the migration to move the project config to the EDIT: I commented out the lines from |
@laurabennett Any chance you can send us your |
@msiemens When cms/src/migrations/m190913_152146_update_preview_targets.php Lines 21 to 26 in ad53b26
Is that not the case for you? You just have |
@msiemens Please just revert to Craft 3.3 and a pre-update database backup. There’s a high likelihood that something didn’t get migrated properly for you, and hacking around the errors is just going to cause more issues down the road. |
I always upgrade Craft and run the migrations on the dev environment first and then sync the Strangely enough, another project where I ran the upgrade with the same setup worked without issues. |
@msiemens How are you doing that? |
Using |
Alright I believe we’ve gotten to the bottom of this. We believe everyone experiencing the missing We’ve just released Craft 3.4.0.1 with a fix for the If you have experienced an error updating to 3.4 already, you must restore your database using a database backup from before updating to Craft 3.4, and then reattempt the update, going straight to 3.4.0.1 this time. |
@brandonkelly I still experiencing some issues when trying to update from
Some more details:
thanks in advance for your help |
@leobauza As I said in my last comment,
So you need to figure out what the original error was. If you’re not sure, please restore your database to a pre-update backup, and reattempt the update. Pay attention to the original error you get, and look for it in |
I had to bring an old Craft 2 database into a site that has been upgraded to Craft 3, and hit a "column not found" error. This issue was the only relevant one in the first page of my search engine results so sharing what worked in case it helps others: # import db and then
./craft migrate/all
./craft update
./craft migrate/all # was prompted to do this when I tried running `./craft project-config/apply`. ymmv
./craft project-config/apply and then |
@olets If you send the Craft 2 database backup over to support@craftcms.com, we can take a look. |
@brandonkelly I'm all set but thank you! Unless you're especially interested in looking at it |
Steps to reproduce
craft migrate/all
to start upgradeAdditional info
The text was updated successfully, but these errors were encountered: