What happened?
When community-base v0.5.8 or later is linked into DTC and Django uses its default local settings, uv run python manage.py check reports community_base.studio.E001 for the site's Studio adapter. The same check passes under website.settings.test, which the maintained CI commands use. The problem is limited to local-settings behavior, but it prevents plain manage.py check and manage.py test commands from reaching their checks/tests.
Steps to reproduce
- In a DTC checkout, link or install community-base v0.5.8 or later.
- Run
uv run python manage.py check (manage.py defaults to website.settings.local).
- Observe
community_base.studio.E001 for community_base/studio/base.html.
- Compare with
uv run python manage.py check --settings=website.settings.test, which passes with warnings only.
Expected behavior
The DTC Studio template chain is treated consistently across local and test settings. Resolve whether the local template loader should use the adapter at templates/community_base/studio/base.html or whether the block probe should account for its reachable nested blocks. Keep the check capable of rejecting a genuinely incompatible shell.
Context
The shared check first appears in community-base v0.5.8. The maintained package consumer CI and DTC course suite pass with test settings. Coordinate with the existing Studio shell work in #377 if it resolves the same template contract.
What happened?
When community-base v0.5.8 or later is linked into DTC and Django uses its default local settings,
uv run python manage.py checkreportscommunity_base.studio.E001for the site's Studio adapter. The same check passes underwebsite.settings.test, which the maintained CI commands use. The problem is limited to local-settings behavior, but it prevents plainmanage.py checkandmanage.py testcommands from reaching their checks/tests.Steps to reproduce
uv run python manage.py check(manage.py defaults towebsite.settings.local).community_base.studio.E001forcommunity_base/studio/base.html.uv run python manage.py check --settings=website.settings.test, which passes with warnings only.Expected behavior
The DTC Studio template chain is treated consistently across local and test settings. Resolve whether the local template loader should use the adapter at
templates/community_base/studio/base.htmlor whether the block probe should account for its reachable nested blocks. Keep the check capable of rejecting a genuinely incompatible shell.Context
The shared check first appears in community-base v0.5.8. The maintained package consumer CI and DTC course suite pass with test settings. Coordinate with the existing Studio shell work in #377 if it resolves the same template contract.