Deleting sets, chapters or levels manually via Django Admin can cause problems with the ExtendedUser

[ampled]

I'm pretty sure this problem happens because the extendeduser uses OneToOneFields to relate a user to a Set/Chapter/Level. This could probably easily be fixed by reworking the "Current X"-fields in ExtendedUser to ForeignKey instead. However, this could cause problems with existing data in the database.