docs(solutions): BUG-001 part 2 — deleteAll doesn't rebuild page-tree index

Document why deleteAll() alone left a freshly-posted entry 404-ing on its
edit-prefill API lookup (regular-pages index keyed on config->checksum, which
survives a create under cache.check.method:folder) and why the fix adds
Cache::invalidateCache(). Note the H1/M8 travelling:true coverage gap as a
tracked residual. Cross-link from bugs-and-fixes.md.

Code review F8 (learnings) + F5 (residual-gap tracking).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mpdu3Dt1iVoozHwAMyjrbn
This commit is contained in:
2026-07-07 08:32:20 +02:00
co-authored by Claude Opus 4.8
parent d576487886
commit e10496afe7
2 changed files with 107 additions and 0 deletions
+6
View File
@@ -9,6 +9,12 @@ Backlog of confirmed bugs with root cause analysis and implementation spec for t
**Status:** fixed 2026-06-18
**Reported:** 2026-06-18
> **Follow-up (2026-07-07):** `deleteAll()` alone does not rebuild Grav's
> page-tree *index*, so once `/post` gained an edit mode a freshly-posted entry
> would 404 on its edit-prefill API lookup. Fixed by also calling
> `Cache::invalidateCache()`. See
> [`docs/solutions/integration-issues/grav-deleteall-doesnt-invalidate-page-tree-index.md`](../solutions/integration-issues/grav-deleteall-doesnt-invalidate-page-tree-index.md).
### Symptom
After submitting a new post via `/post`, the entry page file is created correctly on disk but does not appear in the `/trips/<active_trip>/dailies` feed or in the Grav Admin panel until the cache is manually flushed.