BLOCKER: All template-rendered pages return empty content #18

New Issue

2026-03-02T01:28:03+01:00

clawbot commented

2026-03-02 01:28:03 +01:00

Bug

All server-rendered HTML pages (index, login, sources list, source detail, edit, logs, profile) return HTTP 200 with an empty body (1 byte: newline). The web UI is completely non-functional.

Root Cause

In internal/handlers/handlers.go, parsePageTemplate() uses:

func parsePageTemplate(pageFile string) *template.Template {
    return template.Must(
        template.ParseFS(templates.Templates, "htmlheader.html", "navbar.html", "base.html", pageFile),
    )
}

Go's template.ParseFS names the resulting template set after the first file parsed (htmlheader.html). When tmpl.Execute(w, data) is called in renderTemplate(), it executes the root template — which is htmlheader.html. Since that file consists entirely of a {{define "htmlheader"}}...{{end}} block, the root template is empty.

The page-specific templates (e.g., source_detail.html) have:

{{template "base" .}}
{{define "title"}}...{{end}}
{{define "content"}}...{{end}}

The {{template "base" .}} invocation never executes because Execute() runs the (empty) root template, not the page template.

Evidence

Testing with curl:

$ curl -s http://localhost:9999/ | wc -c
0
$ curl -s http://localhost:9999/pages/login | wc -c
0

The healthcheck (/.well-known/healthcheck) still works because it uses respondJSON() directly, not template rendering.

Fix

Two options:

Option A (simpler): Change renderTemplate() to use ExecuteTemplate with the page template name:

if err := tmpl.ExecuteTemplate(w, pageFile, m); err != nil {

But this requires page templates to use the file's own name rather than {{template "base" .}}.

Option B (recommended): Restructure so the base template is the root. Parse the page file first so it becomes the root template:

func parsePageTemplate(pageFile string) *template.Template {
    return template.Must(
        template.ParseFS(templates.Templates, pageFile, "base.html", "htmlheader.html", "navbar.html"),
    )
}

Since page templates start with {{template "base" .}} (a top-level action), executing the root template will invoke the base template, which in turn uses the defined content and title blocks.

Impact

The entire web management UI is blank. Users cannot see or interact with any page. Only the JSON healthcheck endpoint works. This blocks the 1.0 release.

## Bug All server-rendered HTML pages (index, login, sources list, source detail, edit, logs, profile) return HTTP 200 with an empty body (1 byte: newline). The web UI is completely non-functional. ## Root Cause In `internal/handlers/handlers.go`, `parsePageTemplate()` uses: ```go func parsePageTemplate(pageFile string) *template.Template { return template.Must( template.ParseFS(templates.Templates, "htmlheader.html", "navbar.html", "base.html", pageFile), ) } ``` Go's `template.ParseFS` names the resulting template set after the first file parsed (`htmlheader.html`). When `tmpl.Execute(w, data)` is called in `renderTemplate()`, it executes the root template — which is `htmlheader.html`. Since that file consists entirely of a `{{define "htmlheader"}}...{{end}}` block, the root template is empty. The page-specific templates (e.g., `source_detail.html`) have: ``` {{template "base" .}} {{define "title"}}...{{end}} {{define "content"}}...{{end}} ``` The `{{template "base" .}}` invocation never executes because `Execute()` runs the (empty) root template, not the page template. ## Evidence Testing with curl: ``` $ curl -s http://localhost:9999/ | wc -c 0 $ curl -s http://localhost:9999/pages/login | wc -c 0 ``` The healthcheck (`/.well-known/healthcheck`) still works because it uses `respondJSON()` directly, not template rendering. ## Fix Two options: **Option A** (simpler): Change `renderTemplate()` to use `ExecuteTemplate` with the page template name: ```go if err := tmpl.ExecuteTemplate(w, pageFile, m); err != nil { ``` But this requires page templates to use the file's own name rather than `{{template "base" .}}`. **Option B** (recommended): Restructure so the base template is the root. Parse the page file first so it becomes the root template: ```go func parsePageTemplate(pageFile string) *template.Template { return template.Must( template.ParseFS(templates.Templates, pageFile, "base.html", "htmlheader.html", "navbar.html"), ) } ``` Since page templates start with `{{template "base" .}}` (a top-level action), executing the root template will invoke the base template, which in turn uses the defined `content` and `title` blocks. ## Impact The entire web management UI is blank. Users cannot see or interact with any page. Only the JSON healthcheck endpoint works. This blocks the 1.0 release.

clawbot referenced this issue

2026-03-02 01:31:01 +01:00

1.0/mvp #15

clawbot referenced this issue from a commit

2026-03-02 01:42:00 +01:00

fix: template rendering returns empty pages (closes #18)

clawbot referenced this issue

2026-03-02 01:42:14 +01:00

feat: webhooker 1.0 MVP — entity rename, core engine, delivery, management UI #16

clawbot referenced this issue

2026-03-02 01:42:33 +01:00

1.0/mvp #15