doctrine/DoctrineMigrationsBundle

option enable_profiler breaks the new site

masz opened this issue · 2 comments

masz commented

Tested on new installation (full) 5.3.3

  • extended db version number "serverVersion=mariadb-10.4.20" in .env
  • created a new Controller with maker
  • created a new Entity with maker
  • command line: diff generated, migration executed (all fine)

Browser Test:
"The metadata storage is not up to date, please run the sync-metadata-storage command to fix this issue."

It works without "enable_profiler" option in doctrine_migrations.yaml (db reads/writes are fine as well)

Do you have any suggestion what may be wrong here?

goetas commented

@masz did you try to discover which commands is trying to run doctrine? which fields are not up to date?

masz commented

@goetas thanks for the hint, my docker setup was overriding the env vars without "mariadb-" in serverVersion.