From 2e83afb28b11ffe609c5af5b8a15d6345863bfff Mon Sep 17 00:00:00 2001 From: Konrad du Plessis Date: Wed, 22 Apr 2026 04:24:57 +0200 Subject: [PATCH] Fix: replace multi-line {# #} comment with single-line form MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit My previous commit (fb1a8a2) added a multi-line explanatory comment using Django's {# ... #} syntax, which is single-line only. The comment therefore rendered as literal text at the top of every page. This is the second time this session I've made this exact mistake — lesson for next time: always render a page on the dev server and grep the response body for '{#' after template changes, even one-liners. Verified locally this time: leak count = 0. Co-Authored-By: Claude Opus 4.7 (1M context) --- core/templates/base.html | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/core/templates/base.html b/core/templates/base.html index 72c2631..205e0d4 100644 --- a/core/templates/base.html +++ b/core/templates/base.html @@ -24,12 +24,8 @@ - - {# `deployment_timestamp` is provided by core.context_processors.project_context — - it's injected into every template so the browser (and any CDN in front of - the app) sees a fresh URL whenever the process restarts. The old template - used `request.timestamp` which doesn't exist on Django request objects and - always fell back to a fixed '1.0' — meaning CDNs cached the CSS forever. #} + + {# deployment_timestamp comes from core.context_processors.project_context #} {% block extra_css %}{% endblock %}