You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I debugged it a bit. Maybe it's not related to the docker setup, so I don't know if offtopic.
The SQL query leading to the error:
SELECTspecialrelations.IdAS id,
specialrelations.IdRelationAS IdRelation,
members.Username,
specialrelations.TypeAS Type,
specialrelations.CommentAS Comment,
specialrelations.ConfirmedAS Confirmed
FROM
specialrelations,
members
WHEREspecialrelations.IdOwner=1ANDspecialrelations.IdRelation=members.IdANDmembers.Statusin ('Active', 'ActiveHidden', 'ChoiceInactive', 'OutOfRemind', 'Pending')
ORDER BYmembers.UsernameASC
Unfortunately the error is catched and not given to frontend. I've connected to the DB and executed it manually, leading to the error:
Unknown column 'specialrelations.Type' in 'field list'
The column is missing, I've checked the migrations and can't find it there. Only occurrence of specialrelations is the modernize table comments1 migration (link):
Did I miss some migration command?
Re-applying the test database did not fix it:
$ docker-compose exec php sh -c "php bin/console test:database:create --drop --force"
The text was updated successfully, but these errors were encountered:
After a clean install using docker the edit profile page is showing an error:
Coming from: #219 (comment)
I debugged it a bit. Maybe it's not related to the docker setup, so I don't know if offtopic.
The SQL query leading to the error:
Unfortunately the error is catched and not given to frontend. I've connected to the DB and executed it manually, leading to the error:
The column is missing, I've checked the migrations and can't find it there. Only occurrence of
specialrelations
is the modernize table comments1 migration (link):Did I miss some migration command?
Re-applying the test database did not fix it:
$
docker-compose exec php sh -c "php bin/console test:database:create --drop --force"
The text was updated successfully, but these errors were encountered: