Support

August 14, 2018 at 2:05 pm

We currently have a lot of ticket options, as we have many different tickets, and the tickets change prices frequently during a long-running promotion period. I understand that the current interface is fairly KISS, and very responsive, with all needed information in one place, but when you have as many tickets as us, the form field count grows beyond what standard servers are configured for. Granted, we control the server, but we can’t keep raising the post field limit…

It would be fantastic to have either a separate Ticket Configuration Page, or perhaps only generate the actual fields on the HTML page when the ticket configuration panel is opened (probably easiest).

We go in over the course of the year and add specials by splitting tickets (as there is currently no way to add promotions per item) and this becomes unwieldy fairly quickly (hide expired tickets option?).

As we do this after saving and creating the event, the tickets already exist, and it would be fairly trivial to just not generate the ticket configuration fields until we need them, and leave them up if their values have changed (need to be posted). This would be… fairly awesome.

Thoughts?