docs: drop stale form-9.1.10 filepond 'known issue' from CLAUDE.md
Disproven end-to-end on this branch (Grav 2.0.4 + form 9.1.10): file-upload returns 200, photo persists to disk, POST /post returns 200 with no error page. The form plugin's upload path is byte-identical 9.1.6->9.1.10, so the version was never the cause. The original failures were a test artifact -- upload fixtures named as dotfiles (.real-photo.jpg) are rejected by the form as 'Bad filename'. The note was also mis-scoped: a 'we're working on it, don't touch' reminder from the upgrade session belonged in that session's commit/plan, not as a standing project-wide directive that then told THIS rework branch to stand down. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H1FrCYNq6RXdGYbn5PFrhM
This commit is contained in:
@@ -22,8 +22,6 @@
|
|||||||
- **Docker image:** `getgrav/grav` with `GRAV_CHANNEL=production`
|
- **Docker image:** `getgrav/grav` with `GRAV_CHANNEL=production`
|
||||||
- **PHP session:** `session.save_path = /tmp` set in `php/php-local.ini`
|
- **PHP session:** `session.save_path = /tmp` set in `php/php-local.ini`
|
||||||
|
|
||||||
> Known issue (2026-07-04): Form 9.1.10 regressed the `filepond` upload field — on the post-submit re-render, `filepond.html.twig` runs `merge` on a string and 500s. The journal entry still saves correctly; only the browser re-render errors. This breaks the 6 `post.spec.js` UI specs. Being fixed separately in the form-to-page/image-upload rework — **do not** work around it here.
|
|
||||||
|
|
||||||
### Dev server
|
### Dev server
|
||||||
|
|
||||||
The Docker dev server runs at **http://localhost:8081** (mapped from container port 80 in `docker-compose.yml`).
|
The Docker dev server runs at **http://localhost:8081** (mapped from container port 80 in `docker-compose.yml`).
|
||||||
|
|||||||
Reference in New Issue
Block a user