Problem
Conventions aren't required to use the same event proposal form layout. When an event proposal is cloned from one convention to another (e.g. via the "clone" button), any form sections/fields that exist in the source convention's form but not in the target convention's form are silently dropped — there's no warning, and the data is gone.
Reported case
A user cloned a proposal from Intercon to Summer LARPin. Summer LARPin's proposal form doesn't include a "physical requirements" section, so that data was silently lost on clone. The user didn't notice until later.
Proposed fix
Rather than just warning once via a banner (which is easy to dismiss and miss, as happened here), capture any data that can't be copied into the target form in a new JSONB field on the cloned proposal, and surface it through a dedicated UI element that lets the user view and copy/paste individual field values into wherever makes sense in the new form (e.g. a free-text field, a note to organizers, etc.). This preserves the data instead of just flagging its loss, and gives the user a way to actually recover it.
Reported via Discord, 2026-07-22.
Problem
Conventions aren't required to use the same event proposal form layout. When an event proposal is cloned from one convention to another (e.g. via the "clone" button), any form sections/fields that exist in the source convention's form but not in the target convention's form are silently dropped — there's no warning, and the data is gone.
Reported case
A user cloned a proposal from Intercon to Summer LARPin. Summer LARPin's proposal form doesn't include a "physical requirements" section, so that data was silently lost on clone. The user didn't notice until later.
Proposed fix
Rather than just warning once via a banner (which is easy to dismiss and miss, as happened here), capture any data that can't be copied into the target form in a new JSONB field on the cloned proposal, and surface it through a dedicated UI element that lets the user view and copy/paste individual field values into wherever makes sense in the new form (e.g. a free-text field, a note to organizers, etc.). This preserves the data instead of just flagging its loss, and gives the user a way to actually recover it.
Reported via Discord, 2026-07-22.