Bogue potentiel : les données des champs personnalisés sont effacées si certains champs changent

zogstrip · Août 14, 2026, 11:20

Merci pour ce rapport, il sera corrigé par

github.com/discourse/discourse

FIX: Stop the event builder from clearing typed custom fields (#42624)

main ← event-builder-custom-fields

merged 12:44PM - 14 Aug 26 UTC

ZogStriP

+112 -4

Previously, values typed into the event builder's custom fields were cleared as …soon as another field changed (location, image, name, …), and toggling between the compact and advanced screens could permanently revert them to stale values. This change commits custom field values through the form's `set` (a field's `@onSet` replaces FormKit's default write, so skipping it left the typed value out of the form data), replaces the `customFields` reference on every write (mutating inside the object never invalidated `compactInitialState`, so the compact screen served stale values back), and tracks `formData` (untracked, the advanced screen always reinitialized from the modal's construction-time snapshot). Reported in https://meta.discourse.org/t/potential-bug-where-data-in-custom-fields-is-cleared-if-certain-fields-change/410050

Sujet		Réponses	Vues
[API] data loss caused by changed behaviour of custom user_field update Bug	2	847	Décembre 20, 2017
Custom field casting affected by recent update? Development	5	1306	Août 25, 2020
Custom fields are not inserted with new ProseMirror editor Bug events	7	395	Octobre 29, 2025
What is the 'discourse post event allowed custom fields' setting for? Product Support events	3	520	Novembre 2, 2022
Event custom fields can only be lowercase Bug events , fixed	1	198	Juin 17, 2026

Bogue potentiel : les données des champs personnalisés sont effacées si certains champs changent

Sujets connexes