Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
#88 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@tarunagnihotri534 ya está trabajando en esto.

Desde el 8/10/2026.

  • #89 de @tarunagnihotri534 — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
django, html
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
HTML
Estrellas
3
Forks
29
Merge medio
2 d 1 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de alphaonelabs/learn

Todos los issues de alphaonelabs/learn

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.