feat(toilville): News and Latest read the site's own posts #144
No reviewers
Labels
No labels
build-dist
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Toilville/toilville-design!144
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/news-reads-real-posts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The News page and Home's "Latest" render the design canvas's four sample entries, and their "Read the post" links point back at the page they sit on. The site has 0 published posts and 38 drafts. Walking every link on all five live pages finds ten internal targets — the five pages and four in-page anchors — and not one article.
toilville/post-listnow reads the site's own published posts (toilville_rituals #416). The canvas's rows still ship as the block's static-mode content; they simply reach no reader.What this looks like on deploy: until something is published, the News page is its hero plus one line saying nothing is published yet, and Home's "Latest" is its heading plus the same line. That is the intent — the alternative is a page that implies articles exist — but it is a visible change to a live marketing site, so it deserves to be a deliberate merge rather than a surprise.
Scope
forgeblock_toilville.py— emitsource: recenton post-list.copy_coverage.py— the sample rows are copy the page deliberately does not render. Excluded rather than discounted: no floor was lowered. That file says twice that floors are a ratchet and that lowering one to green a build is the bug leaving by the door it came in. The exclusion is derived from the pattern, not listed in the gate, so it stays true when the canvas's samples change and disappears by itself if a page ever returns tostatic. The heading-join check takes the same exclusion — a title the page no longer renders cannot be joined wrongly either.render_pattern.php— post stubs returning nothing, which is what the live site would answer today.Testing
copy_coverage.py checkpasses every page and every sub-check, against the plugin branch that actually has the new render. Before the exclusion it failed exactly as predicted: the four sample titles reported as headings reading differently.build_surfaces.py checkclean, 327 tests pass, Gutenberg block validation clean on all five patterns.Impact Statement
Both lists stop showing articles that do not exist. Requires toilville_rituals #416 first — without it the plugin ignores
sourceand keeps rendering the sample rows, so the pages look as they do today rather than breaking. The copy gate enforces the same floors on everything except the rows the site deliberately no longer renders.