Django 3.2 breaks django-multisite: The SITE_ID setting must be an integer

[digodude]

After upgrading to Django 3.2 and using django-multisite 1.9.0 the development django runserver doesn't pass a new test:

ERRORS:
?: (sites.E101) The SITE_ID setting must be an integer

[erimeilis]

Yep, and if you use SITE_ID = int(SiteID(default=1)) instead, than you'll get:

env/lib/python3.9/site-packages/multisite/middleware.py", line 46, in init
raise TypeError('Invalid type for settings.SITE_ID: %s' %
TypeError: Invalid type for settings.SITE_ID: int

[pfouque]

Hi, i didn't tried yet but there is a fix for that issue in parent project : shestera@1ec217d

[erimeilis]

Hi, i didn't tried yet but there is a fix for that issue in parent project : shestera@1ec217d

Hello! It seems to eliminate problem with SITE_ID, but another one comes, - 404 for every site.

[marksweb]

Ah you found my fix! If that fix doesn't work for you (@erimeilis) or you'd rather stick to the main releases, you can also use a django setting which I'd forgotten about when patching this new check.

The django setting SILENCED_SYSTEM_CHECKS will avoid this problem.
https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-SILENCED_SYSTEM_CHECKS

[mellertson]

I undertstand using SILENCED_SYSTEM_CHECKS will quiet the error message. But, I'm just curious if another solution has been found for this issue?

[mellertson]

I found that doing SITE_ID = int(os.environ.get('SITE_ID', 1)) fixed the issue with Django version 4.2. Hope that helps someone.

[kotrotko]

mellertson It works for me, thank you))