-
Notifications
You must be signed in to change notification settings - Fork 641
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
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fields.searchable' in 'field list' #3663
Comments
Rolled back the update, here are the affected packages:
|
I'm running into the same issue after an update. These are my craft packages:
after rollback to a working version again these are the affected packages:
|
I tried disabling SEOMatic before applying the update. The result is a slightly different error-message:
|
I think this can happen when you don’t revert the db completely after failing 3.1 migrations. |
I had the same issue when updating to Craft 3.1.1 last night from 3.0.30.2. It took down all of CraftCMS for our website.
|
Quite possible - for me the error occurred on the initial visit to /admin after running composer update, so I dunno if there were any migrations that had failed already. However I have found out that manually disabling all installed plugins, running composer update, going to /admin to let it "do it's stuff" and then manually re-enabling all plugins allows me to upgrade to 3.1. |
This error you mean? I ran a straight migration through my CI pipeline where the project is rebuilt from scratch via composer each time. The DB persists on an Amazon RDS instance but when I deployed the code with the new version of CraftCMS I ran into the aforementioned error. All Craft pages are now returning the same error and I am unable to even reach the CP. I can SSH into the server and fix this with a workaround, but that won't fly when this pipeline reaches prod of course. Edit - I do not think any migrations were run because I was unable to even reach the CP to run them. |
We are also facing this issue with the same error message. After some tests, we think it has to do with the new general config setting:
The moment this config is set to |
Same error here… |
+1 Experiencing this as well. |
Fixed the @boldenamsterdam The |
3.1.2 is out with the fix now. |
I'm getting this error after updating from craftcms/cms (3.0.36 => 3.1.21.1) Is there a work around? |
|
@mofman can you find the error in |
Hi Brandon, Sorry for the delay in getting this to you.
|
Thanks @mofman, just fixed that for the next release. To get the fix early. change your "require": {
"craftcms/cms": "dev-develop#147464d069dec9d23fa5f8045de6148f7470bbcd as 3.1.23",
"...": "..."
} Then run |
Description
After running a
composer update
I get the following error:If you need any files, stack-traces etc etc just say so - I'll be monitoring this issue for the next 5 hours or so :)
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: