From 489dd157b6b136941db3ef6b6ea00a67d2149adf Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Wed, 5 Apr 2023 20:41:34 +0100 Subject: [PATCH] context processor documn link --- core/context.py | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/core/context.py b/core/context.py index 1f49290..e410fd6 100644 --- a/core/context.py +++ b/core/context.py @@ -6,14 +6,17 @@ from troggle.core.models.troggle import Expedition in the processing of Django templates This seems to mean that every page produced has bundled in its context the complete 'settings' and -the expedition class object, so all templates can doe queries on Expedition. +the expedition class object, so all templates can do queries on Expedition. https://betterprogramming.pub/django-quick-tips-context-processors-da74f887f1fc If it is commented out, the logbookentry page goes crazy and the screws up all the site_media resultions for CSS file s! Seems to be necessary to make {{settings.MEDIA_URL}} work. Which is obvious in retrospect. + +It is VITAL that no database operations are done in any context processor, see +https://adamj.eu/tech/2023/03/23/django-context-processors-database-queries/ """ def troggle_context(request): return {"settings": settings} - return {"settings": settings, "Expedition": Expedition} +# return {"settings": settings, "Expedition": Expedition}