#32692: Django 3.2 automatic AppConfig discovery breaks projects working in
3.1.8
-------------------------------+--------------------------------------
Reporter: Manel Clos | Owner: nobody
Type: Bug | Status: closed
Component: contrib.admin | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Manel Clos):
Hi Carlton, I agree, but I'd also need to modify STATICFILES_DIRS, and
FIXTURES_DIRS, and maybe something else.
In the end it would be better to modify the AdminConfig documentation as
Marius suggested, even when this was previously working correctly up to
3.2.
Based on the tested workaround in the description, what about this?
https://github.com/manelclos/django/commit/c5da1ff59d6d53dc25cf503be9d59c1f825fb10a
--
Ticket URL: <https://code.djangoproject.com/ticket/32692#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.6203f2736c733e3bad52f51463ffc8fc%40djangoproject.com.
