Group definition can be corrupted with non-existant pads in its definition
Description of the bug
I am not the one who experienced the bug, so I'll try to explain the most accurately with the informations I gathered (I'm the one who fixed manually the bug in the database though).
From what I was explained, a pad was created in a group, and then quickly removed just after. It ended up with the pad that was indeed removed from the database. However, the group still had the pad as a member, which shouldn't happen.
This resulted in a broken group page: the page couldn't be loaded anymore from what I was told, and only did lead to an empty, white page.
What should be the normal behavior?
A pad removal should accurately remove it from the group too. Also, in case, such corruption still happen again, it shouldn't prevent from loading the group page, which could also for example help to fix it from the user interface rather than having to dive in an horrible database.
What is the current behavior?
Group becomes corrupted and can't be accessed anymore
Do you have a hint about the bug resolution?
A group should only contain existing pads, so maybe having a way to check this. And if this kind of corruption still happens, maybe have a way to still render the group page with a broken pad URL and the way for a user to remove it (or when rendering the page, check every pad, and if it's not found, purge it from the database.