-
-
Notifications
You must be signed in to change notification settings - Fork 724
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
[BUG] - deleted users recipes causing listing to error #4210
Comments
Please provide accurate version info, from the settings page. |
I have updated the report with the sha |
@michael-genson is this a households bug? 2nd last line of the logs references |
This isn't a household bug exactly, looks like an issue with deleting users (as mentioned in the initial comment) A recipe's So TL;DR it's a broader issue with deleting users not being handled properly. Similar/same issue: #3171 @russell were you able to get this sorted for your instance? |
Yes, I cheated and modified the database. The SQL is in the report, i left it there in case another user encounters the same issue and isn't sure what to do. |
I encountered the same issue. Recipes were created using a local user, but later switched to oauth for authentication and removed the original user. Restarting the container threw the same error as described. I fixed it using the same method described by @russell where I just manually changed the IDs for recipes in the database made by the deleted user to a user that exists. |
Closing in favor of #3171 |
First Check
What is the issue you are experiencing?
500's when visiting the main recipe listing.
Steps to Reproduce
ok, i think it was caused by me deleting a user. In the past, i had been using regular users, but then i switched to oauth, when i did that for what ever reason (something went a bit awry) i deleted my user and recreated it.
I was able to fix my installation, by running an update against the recipes table to take ownership of the recipes
Please provide relevant logs
Mealie Version
0eb3e3f
Deployment
Docker (Linux)
Additional Deployment Details
No response
The text was updated successfully, but these errors were encountered: