Added by Matt Hardy about 6 years ago
Hi
I have freshly installed 8.3.1, and this has switched to Postgres database.
When I try to delete a user, after the green success notification, the user sticks around.
I notice on my testing install, before we decided to give OP a try, it installed mysql.
We googled a bit and noted that there is a 'delayed_job' function, which apparently picks up tasks and actions them?
I would expect a user to be deleted, once deleted.
Hard to know if this is a bug, regression or expected behaviour ie. can't delete a user
Replies (1)
Update: Checked in Postgres >
SELECT * FROM delayed_jobs LIMIT 1000;
ie.
priority
0
attempts
0
handler
--- !ruby/object:DeliverInvitationJob
token_id: 20
run at
2019-03-20 20:46:13.790354
etc
There is also the delete user problem here:
ie.
handler
--- !ruby/object:DeleteUserJob
user_id: 9
So, the delayed_job table gives some evidence, the events are not being picked up.
Any idea on where to help solve this?
Thanks