-
-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to delete account #1802
Comments
What is the error that you are getting ? To find out what the error is, turn on debug mode and collect as many error messages as you can as outlined in our Troubleshooting guide. |
Oddly when I flip the bit on for debug it works? 🤔 |
@JoshStrobl Huh... could it have possibly been a cache error ? Does it work if you turn debug mode back off ? If not, debug mode may be allowing the error to be ignored for some reason 🤔, still check the log files as outlined in the Troubleshooting guide just in case. |
Exceptions should be logged in the |
I think it may be related to polls: Logs
|
@JoshStrobl Does it work if you disable reflar/polls ? By the way, I edited your comment to put the log in a spoiler, so one doesn't have to do so much scrolling. |
@datitisev Not really an option at the moment. This is an in-production deployment, can't really go around disabling stuff nilly willy. I hope you understand. |
@JoshStrobl I was able to reproduce this after installing reflar/polls, creating a discussion with a poll with the user I was going to delete, and then deleting that user, all with debug mode off. If you could make an issue in ReFlar/polls about it, that'd be great. It has something to do with having a reference to the deleted user, it doesn't seem to be handled properly. As this is not a core problem, I'm closing the issue. |
Bug Report
Current Behavior
Attempted to delete (not suspend) user account. It just returns a notification that "something went wrong"
Steps to Reproduce
Expected Behavior
Account delete would function as intended so I could enforce GDPR's Right to Erasure without having to resort to MariaDB queries.
Environment
The text was updated successfully, but these errors were encountered: