You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that #3470 introduced a bug where, if your event doesn't have any configured options under [[staff_event_shirts]], you will not be able to add any attendees to the database.
Obviously this is a problem, but the other problem is that we use the text in the options under [[staff_event_shirts]], and due to the implementation of integer enums those options' text can't be changed. So if I set a default of, say, "No Event Shirts" = string(default="0"), and add a config option called Two Staff Shirts = 0, I will have c.STAFF_EVENT_SHIRT_OPTS be populated with [(0, 'Two Staff Shirts'), (0, 'No Event Shirts')]
This is not ideal.
The text was updated successfully, but these errors were encountered:
Update: we found later that I had actually written [[staff_event_shirt]] in the singular. This was correct, since that's the style of other sections (otherwise you'd get variable names like c.SHIRTS_OPTS), but then later I forgot. Whoops!
It turns out that #3470 introduced a bug where, if your event doesn't have any configured options under
[[staff_event_shirts]]
, you will not be able to add any attendees to the database.Obviously this is a problem, but the other problem is that we use the text in the options under
[[staff_event_shirts]]
, and due to the implementation of integer enums those options' text can't be changed. So if I set a default of, say,"No Event Shirts" = string(default="0")
, and add a config option calledTwo Staff Shirts = 0
, I will havec.STAFF_EVENT_SHIRT_OPTS
be populated with[(0, 'Two Staff Shirts'), (0, 'No Event Shirts')]
This is not ideal.
The text was updated successfully, but these errors were encountered: