- Issue created by @kwfinken
- πΊπΈUnited States kwfinken Lansing, MI
For those facing a similar issuer, getting the container running again and clearing cache fixed the issue. It appears that in the update the cache was somehow not cleared. Unsure if there are other issues or not.
- π¬π§United Kingdom alexpott πͺπΊπ
Did you run config import before ensuring there are no database updates? After you update any code you need to ensure that database updates are run before doing anything like a config import.