Skip to content

Fix for django 3.2

Choose a tag to compare

View all tags
@vinitkumar vinitkumar released this 05 Jan 18:58
version-1.9.1
c9b87eb

Django 3.2 brings a check for SITE_ID that breaks the django-multisite completely. More info here: shestera#9

So, we need the latest django-multisite and at the same time need the fix for django 3.2. Trying fix from the upstream fork, in the hope that there is a new fix for the project released and we are not stuck with an incompatible patch.

Assets 2
Loading