See #3635
There were some workarounds introduced here to stop empty_fields errors.
Those errors should've not happened in the first place, they are basically the result of data that doesn't fit our definitions, however we currently cannot introduce migrations, therefore: workarounds.
Once the database migration system is done:
Revert the workarounds (i.e. mainly the changes to the fields.py file), fix any action that writes wrong data and, if necessary, write a migration to fix the broken data in the database.
See #3635
There were some workarounds introduced here to stop empty_fields errors.
Those errors should've not happened in the first place, they are basically the result of data that doesn't fit our definitions, however we currently cannot introduce migrations, therefore: workarounds.
Once the database migration system is done:
Revert the workarounds (i.e. mainly the changes to the fields.py file), fix any action that writes wrong data and, if necessary, write a migration to fix the broken data in the database.