mirror of
https://codeberg.org/PostERG/xamxam.git
synced 2026-06-25 16:19:19 +02:00
Documents the 'can't access property main, n.status is undefined' crash in FilePond 4.32.12. Root cause: vendor code in filepond.min.js has a property name mismatch — createResponse objects use .code but the load-file-error handler reads .status. When action.status is undefined, the view writers crash. Proposes Option B (custom load function) as the cleanest fix.
1.3 KiB
1.3 KiB
TODO
HTMX v2 Migration
Reference: docs/autosave-system.md → "HTMX v2 Migration Plan" section.
contenus-edit.php(pages): Addhx-*attrs, addovertype:changedispatch in OverTypeonChangecontenus-edit.php(form_help): Addhx-*attrs, addovertype:changedispatch in OverTypeonChangeapropos-groups-form.php(contacts): Addhx-*attrs onlycontenus-edit.php(sidebar_links): Addhx-*attrs only- Add
handleAutosaveResponse()shared handler +htmx:beforeRequestloading state - Delete
autosave.js - Fix backend
$isAjaxdetection: also recognizeHX-Requestheader (page.php, apropos.php, form-help.php) - Form-help inline editors: add OverType toolbar + HTMX auto-save + remove save buttons
- Markdown cheatsheet modal: reusable dialog on all OverType editors
FilePond crash on TFE upload forms
- Analyze root cause →
docs/filepond-crash-analysis.md - Partial fixes (Content-Type headers, onerror cleanup, load object) — insufficient, crash still reproduces
- Replace
server.loadwith custom function to bypass FilePond's buggyload-file-error→DID_THROW_ITEM_INVALIDdispatch (see analysis doc, Option B) - Implement
destroyFilePondsIn()pre-destroy abort (defense in depth)