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
When we create an event and give it multiple offerings, we gain the ability to give each offering a unique name. When we do this though, every event we create has a name and the original name for the event becomes irrelevant yet is still required for the form to be saved.
The now irrelevant event name is not used anywhere else (to my knowledge) yet remains a required field meaning that if you simply click the toggle to offer multiple events, you're forced to manually enter dummy name data before you can create all the events. This should not be the case.
Since this is a UI decision, we should talk this over with Brian.
The text was updated successfully, but these errors were encountered:
This issue is modified in PR #1349, Multiple Offerings and Repeating Events Refactor with the input box being greyed out when the series toggle is toggled.
When we create an event and give it multiple offerings, we gain the ability to give each offering a unique name. When we do this though, every event we create has a name and the original name for the event becomes irrelevant yet is still required for the form to be saved.
The now irrelevant event name is not used anywhere else (to my knowledge) yet remains a required field meaning that if you simply click the toggle to offer multiple events, you're forced to manually enter dummy name data before you can create all the events. This should not be the case.
Since this is a UI decision, we should talk this over with Brian.
The text was updated successfully, but these errors were encountered: