Rafał Pitoń

Only solution that comes to mind is moving `profile_fields` from HStore to JSONB, which is standard and has constant OID in PostgreSQL (and it's clients). But then what guarantee there...

@jeroenbakker-atmind I've found a new lead for what can cause this issue. Can you please tell me what memory limits are set in your docker configuration?

I've couldn't reproduce this, but there are two possibilities now I would like to check: - Django caches wrong object ID (`OID`) for HStore extension for current connection, which results...

I'm unable to reproduce this, but I've added logic that will catch when this bug happens and will print error message with debug data that will help me investigate this...

Thank you for reporting this! With data I've gathered so far, it seems there's a bug in Django where on rare occasions it fails to register HStore extension for database...

Plugin territory

Hey, thanks for offering help here. I was thinking about implementing reports only after I've [simplified user permissions](https://misago-project.org/t/simplifying-user-permissions/1097/) but that's not a blocker. My plan for this feature was to...

> About the models you suggest, why do you think to make reason separate from report? Because that way you have cheap filtering by standard report reason in potential admin...

> Ah, ReportReason are the category of a report ? Correct, basically those: > Submitted: When a user create the report > Accepted: When an administrator accepted the report and...

My current idea for this is to have extra flags on user model: - `requires_user_verification`: if `True`, user needs to verify their e-mail address - `requires_admin_verification`: if `True`, admin needs...