#44640 introduced a new column to #__action_logs_users
. When logging into the backend in 5.3, the default setting tries to log that login and this might introduce a problem. Specifically, if your database is not up-to-date (for example still on 5.2), that column might not be there and this results in a fatal error. Normally I would then try to open the database view and click the fix button, however the fatal error leads to the user not being logged in and the attempt to load the database view (or accessing the database.fix
task directly) just results in a redirect to the backend login page again. So this means it is impossible to get around this error without manual intervention in the database.
Labels |
Added:
No Code Attached Yet
Release Blocker
bug
|
thanks @richard67 I added it to the agenda
I've prepared 2 alternative PRs to fix this issue.
As long as I haven't tested these PRs myself and completed testing instructions, I will leave them in draft status and this issue open.
The latter PR could possibly be improved so that certain kinds of notifications still are sent in order to get notified when someone uses your user account without your knowledge.