search

dancerfly / django-brambling

Event website manager, specifically designed for dance weekends or other events with multiple simultaneous tracks of classes.
BSD 3-Clause "New" or "Revised" License
11 stars 3 forks source link

Check payment cutoff edge case #526

Open melinath opened 9 years ago

melinath commented 9 years ago

Right now, hypothetically, if an organization decides to start accepting check payments after setting up an event, the event will end up in a weird state where check payment is allowed, but there's no actual postmark date set.

I think this is unlikely to be a problem any time soon, and I also think the proper solution is to implement a similar system as for #521 – i.e. to have a field for selecting from a range of options (Always, 1 week, 1 month, custom date), defaulting to 1 week, and then update the underlying value whenever the event is created / has its date change (but only display the field if check payment is allowed.)

harrislapiroff commented 9 years ago

I'm actually not sure this is an edge case. It seems pretty easy (and like it might turn out to be pretty common) for an organizer to set up their event before realizing they have to enable payment options on the Organization instead. In which case they would go back and enable payment options after creating the event.

melinath commented 9 years ago

From a user:

I set up to allow payment by check, but when I get to the last screen is tells me to select a payment option ... but no options are displayed. Looks like I can't continue exploring without doing actual transactions or setting up accounts with payment services???

I think they ran into this case?