Thanks for the report! Forgot to update the schema files 😞
I think this would be a good time to keep all schema changes in the migrations module, so we don't have to worry about this in the future. While I work on a fix, to clarify, the workaround is to first run this database query:
Describe the bug
V2 migrations (altering the
appcontenttable) is not applied during init-db; migrations table claims it is V2 though.
Steps to reproduce (if necessary)
V2 migrations were run and appcontent has title and content_type columns.
Version or last commit:
update appmigrations set version=1;
The text was updated successfully, but these errors were encountered: