Core Template Not Extending Project Template As Expected

[wesleyboar]

Progress

• Core-CMS task/GH-168-update-template-inheritence-with-django-solution
  ↑ Core-CMS task/GH-168-update-template-inheritence
• solution below is off of old main; redo it off of latest main
  ↑ Core-CMS-Resources GH-168-update-template-inheritence

Summary

A CMS project with a page using a Core template does not load Project's custom assets.

Prerequisites

• Have a CMS project built with custom project assets, like example-cms (easiest to test¹).

¹ Because it's site.css has a yellow background (as of the creation of this ticket).

Steps

1. Create a page (A), and choose the template "Fullwidth" (or whichever loads example-cms/templates/fullwidth.html).
2. Create a page (B), and choose a template "Homepage (for Portal)" or "Guide(: …)".
3. Load page (A).
4. Load page (B).

Expected Result

1. Page (A) does load example-cms/css/build/site.css.
2. Page (B) does load example-cms/css/build/site.css.

Actual Result

1. Page (A) does load example-cms/css/build/site.css.
2. Page (B) does not load example-cms/css/build/site.css.

Background

This was discovered on https://cep.tacc.utexas.edu/ at the time of creating this ticket.

Direction

Problem:
The {% extends "fullwidth.html" %} code in a project template is not inheriting project fullwidth.html template. Instead, it is inheriting the core fullwidth.html template.

Solution Ideas:

• ❌ For settings.py's DIRS, instead of listing custom project root, list each custom project's template directory (like is done for settings.py's INSTALLED_APPS).
• 🤔 The Django solution may be to use APP_DIRS to overwrite from an app's template directory (which is disabled in our code).