id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
31592	"Reverting Django 3.1. to Django 3.0.6 raises ""binascii.Error: Incorrect padding""."	אורי	nobody	"I upgraded to Django 3.1a1 and ran migrations. I also created my own migration because of the change from `from django.contrib.postgres.fields import JSONField` to `from django.db.models import JSONField`. My own migration was generated automatically:

{{{
# Generated by Django 3.1a1 on 2020-05-14 16:25

from django.db import migrations, models
import speedy.match.accounts.models


class Migration(migrations.Migration):

    dependencies = [
        ('match_accounts', '0006_auto_20200121_1731'),
    ]

    operations = [
        migrations.AlterField(
            model_name='siteprofile',
            name='diet_match',
            field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.diet_match_default, verbose_name='Diet match'),
        ),
        migrations.AlterField(
            model_name='siteprofile',
            name='relationship_status_match',
            field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.relationship_status_match_default, verbose_name='Relationship status match'),
        ),
        migrations.AlterField(
            model_name='siteprofile',
            name='smoking_status_match',
            field=models.JSONField(default=speedy.match.accounts.models.SiteProfile.smoking_status_match_default, verbose_name='Smoking status match'),
        ),
    ]
}}}

Most of the things worked with Django 3.1a1 except a few things which I will report later. But when trying to use Django 3.0.6 again, I ran the following commands:

{{{
./manage_all_sites.sh migrate auth 0011
./manage_all_sites.sh migrate match_accounts 0006
}}}

Then,  after running my websites with Django 3.0.6, I received an error message:

`Incorrect padding`

I can't run my websites locally without deleting the database completely including all users. I didn't find any way to fix the database to run it with Django 3.0.6."	Bug	closed	Core (Other)	3.1	Normal	invalid			Unreviewed	0	0	0	0	0	0