The user lunelson reports that their user_event webhook only includes the first three user_fields, despite having a fourth field configured. They are using Discourse version 2.6.0.beta2. simon responds that all fields should appear in the webhook payload and asks about the configuration, noting that it shouldn’t affect the issue. lunelson clarifies that the fields are not set to appear on the user card or public profile, and observes that the fourth field is also missing from the sign-up modal, suggesting a possible limitation in how fields are handled in the UI or webhook payload.
I’ve just created a new “confirmation” type User Field (the fourth user field we have configured), hoping to track changes to this field through webhooks;
However I’m finding that our user_event Webhook payloads are only coming through with the first three user_fields values—the fourth (newly created) one is not present. Am I missing something?
Thanks @simon. The fields are configured as follows: most of them aren’t relevant to show on user card or public profile, so those options are un-checked. I’m also finding that only the first three in visual order here actually appear in the sign up modal. Whichever way I order them, the fourth one gets cut off