Skip to content

Title: Create missing 500.html error template to fix crashing server error handler #75

Description

@komalharshita

Title: Create missing 500.html error template to fix crashing server error handler

Problem:
app.py registers a 500 error handler that calls render_template("500.html"), but the file templates/500.html does not exist in the repository. When any unhandled server error occurs (e.g. a malformed projects.json, a missing import, or a runtime exception), Flask will attempt to render the missing template and immediately raise a TemplateNotFound exception on top of the original error, producing a completely blank response or a second uncaught exception. This makes debugging production errors impossible and was also reported by a contributor in issue #66 which only mentions the 500 handler — this issue focuses on the missing template file itself.

Proposed Solution:
Create templates/500.html following the exact same visual structure as the existing templates/404.html:

  • Same navbar, same .error-page container class
  • Error code displayed as 500
  • Heading: "Something Went Wrong"
  • Subtext: "An unexpected error occurred. Please try again or contact us if the problem persists."
  • "Back to Home" button linking to /
  • Must link to static/style.css for consistent styling

Files Likely Affected:

  • templates/500.html (create new)

Estimated Difficulty: Beginner

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions