Error Journal

Running log of errors encountered, root causes identified, and resolutions applied.

Purpose

This journal tracks errors that occur during development and deployment, along with their root causes and solutions. The goal is to prevent repeating the same mistakes and to provide a reference for troubleshooting similar issues.

Entry Format

### Error Title
**Date:** YYYY-MM-DD
**Issue:** Brief description of the problem
**Root Cause:** What actually caused it
**Resolution:** How it was fixed
**Prevention:** How to avoid it in the future

Entries

Template Mismatch / Shadow Directory

Date: 2026-06-07
Issue: Changes to index.html were not appearing on the live website at http://localhost:5050.
Root Cause: A redundant nested directory structure existed: /home/vincent/quality_small_engine_mock/quality_small_engine_mock/. The running Flask process was serving files from this "shadow" directory instead of the intended root directory.
Resolution:
1. Identified the conflicting PID
2. Terminated the existing Flask processes
3. Removed the redundant nested directory
4. Restarted the server from the correct root directory
5. Verified the fix by checking that content was now present
Prevention: Avoid creating nested project folders with the same name during initialization or git clones. Use ls -R to audit directory structures if content mismatches occur.

WordPress Migration Error

Date: 2026-05-22
Issue: Content lost due to premature DNS change before backup.
Root Cause: Migration instructions told user to change DNS before backing up WordPress.com site.
Resolution: DNS reverted to WordPress.com, attempting recovery. See [[Migration-Post-Mortem]] for full details.
Prevention: Always backup before DNS changes. Test on internal IP first.

Jinja2 Pluralization Syntax Error

Date: 2026-06-21
Issue: 500 Internal Server Error on second-brain-server initial launch.
Root Cause: {{ pages | length | pluralize }} — pluralize is not a built-in Jinja2 filter.
Resolution: Patched to {{ 's' if pages | length != 1 }}.
Prevention: Test Jinja2 templates on first launch. Use built-in filters or register custom filters.