Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] /affiliations and 404 error handler serve raw unrendered Django/Jinja template source code

Aperta
#88 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@tarunagnihotri534 ci sta già lavorando.

Dal 8/10/2026.

  • #89 di @tarunagnihotri534 — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
1/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
django, html
Ambito
backend

Direzione di ricerca

Inspect the /affiliations route and the production 404 handler, along with the affiliations.html and 404.html templates mentioned in the report. Check how each response is served and rendered; verify /affiliations displays rendered content and invalid routes return a rendered 404. A linked pull request (#89) is already open, so this work appears to be underway.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

When visiting the /affiliations page (linked in the site footer under ABOUT & LEGAL) or triggering a 404 error on any invalid route (such as /sitemap.xml or /some-nonexistent-page), the web server serves the raw, unrendered template source code rather than executing the Django rendering pipeline.

Visitors see literal bracketed template tags ({% extends "base.html" %}, {% block title %}, {{ requested_path }}), unstyled typography, and no navigation header or footer.


Confirmation of Related 404 Behavior

As suspected, this issue affects both the public /affiliations route and the production 404 error handler:

  • https://alphaonelabs.com/affiliations: Returns HTTP 200 OK, but the body is the unrendered template affiliations.html.
  • https://alphaonelabs.com/sitemap.xml: Returns HTTP 404 Not Found, but the body is the unrendered template 404.html (displaying literal {{ requested_path }}).
  • https://alphaonelabs.com/any-invalid-url: Returns HTTP 404 Not Found with the exact same unrendered template syntax.

Steps to Reproduce
Case A: The /affiliations Route
  1. Navigate to https://alphaonelabs.com/.
  2. Scroll to the footer under ABOUT & LEGAL and click Affiliations (or directly open https://alphaonelabs.com/affiliations).
  3. Observe the top and bottom of the viewport.
Case B: The 404 Error Handler
  1. Navigate to https://alphaonelabs.com/sitemap.xml or any non-existent path like https://alphaonelabs.com/nonexistent-test-page.
  2. Inspect the rendered response.

Expected vs Actual Behavior
For /affiliations:
  • Expected: A fully rendered HTML document extending base.html, complete with brand styling, standard navigation header (site-navbar), dark mode styles, and the footer.
  • Actual: The raw template source is served as plain text/HTML (HTTP 200 OK), displaying:
    {% extends "base.html" %}
    {% block title %}Affiliations - Alpha One Labs{% endblock %}
    {% block meta_description %}Organizations and initiatives affiliated with Alpha One Labs.{% endblock %}
    {% block body_class %}min-h-screen flex flex-col bg-white text-gray-900 dark:bg-black dark:text-gray-100 overflow-x-hidden{% endblock %}
    {% block content %}
    ...
    {% endblock %}
    
    
Image Image
Lingua principale
HTML
Stelle
3
Fork
28
Merge medio
17h 41m
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di alphaonelabs/learn

Tutte le issue di alphaonelabs/learn

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.