Repository navigation
Commit 690fe5c
committed
Upcoming, theme pages and the sitemap render per request, not from the build
The Docker build has no backend. Because /upcoming no longer read searchParams,
Next prerendered it at build time, so the first five minutes after every deploy
served "Upcoming dates are unavailable"; /upcoming/[theme] served "no dates"
(and a noindex robots tag), and the sitemap listed only the six fixed pages
until its hourly window passed. That is also why the last two deploys were
rolled back: the deploy's /upcoming probe polls for data-upcoming-count and
never saw it.
All three now use force-dynamic. Their data reads keep their 60-second cache,
and dynamicParams=false still 404s politics and natural-disasters. Verified in
a local production build: /upcoming has data-upcoming-count="72", the finance
page lists 72 rows, the sitemap has 43 URLs (33 events, 2 themes, 2 year
pages), /upcoming/politics is 404, and an event page is indexable.1 parent 3eda816 commit 690fe5c
3 files changed
Lines changed: 11 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
15 | 18 | | |
16 | 19 | | |
17 | 20 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
12 | | - | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
13 | 16 | | |
14 | 17 | | |
15 | 18 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
18 | | - | |
19 | | - | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| |||
0 commit comments