You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a view returns one of the status codes (400, 403, 404, 500), a default Django error view is invoked, but these views (with the exception of 404) do not include context variables provided by TEMPLATES['OPTIONS']['context_processors'].
As a result, the names of the portal and program (provided by the context processor portal_and_program_names) are not included in the title or at the top of the page (see coldfront.templates.XXX.html).
Option 1: Customize the views to include at least these pieces of context. This would likely involve copying a lot of the original view code.
Option 2: Pre-generate the XXX.html files (e.g., in Ansible) to have the name hard-coded. However, these templates extend the base template and load static content, so this may not be feasible.
Note that DEBUG must be False to test this.
The text was updated successfully, but these errors were encountered:
When a view returns one of the status codes (400, 403, 404, 500), a default Django error view is invoked, but these views (with the exception of 404) do not include context variables provided by
TEMPLATES['OPTIONS']['context_processors']
.As a result, the names of the portal and program (provided by the context processor
portal_and_program_names
) are not included in the title or at the top of the page (seecoldfront.templates.XXX.html
).Option 1: Customize the views to include at least these pieces of context. This would likely involve copying a lot of the original view code.
Option 2: Pre-generate the
XXX.html
files (e.g., in Ansible) to have the name hard-coded. However, these templates extend the base template and load static content, so this may not be feasible.Note that
DEBUG
must beFalse
to test this.The text was updated successfully, but these errors were encountered: