Welcome, Guest
Username: Password: Remember me

TOPIC: [ADDED] Eureaka! Why Minimum Group Registration should be 1!

[ADDED] Eureaka! Why Minimum Group Registration should be 1! 11 years 11 months ago #19308

  • global
  • global's Avatar
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 20
  • Thank you received: 0
We've run into a snag with no solution so far.

Because DT Register doesn't offer ticket types (I'll get to that), we have to use fee check box fields to give discounts for things like married couples.

This worked in the old system because you set how many were in your group, and it was always at least 2. On top of that, we would set the field NOT to appear if the group was higher than 9. The group discount kicked in at 10 members and the married couple check box would never appear.

Now that there's no way for the system to know how many members are in a group until checkout, the married check box ALWAYS shows. That's okay, if the system noticed that you had hit 10 members and gave you a message that the married discount would be dropped and the group discount would be used instead...but it doesn't.

Instead what happens is the married discount gets taken off for any of the first 9 members who checked the box, and then on the 10th and above the check box doesn't show up...but for that first 9, it isn't dumped, it is calculated in. This has forced us to create another event in the system (one for singles and groups under 9, one for groups above 10).

Then to complicated it further, there's a new option to allow groups of 1. This means an even more simplified registration...except again, because it's a "group" reg, that married couple discount appears. It's fine if it appears, but if a single person checks the box and then checks out, it should tell them that they cannot use that discount for a single user and then dump the discount off.

Back to my mention of ticket types. We in addition to these little fixes, I'd love to see DT Reg adopt a new "Ticket type" fuction where you can set up multiple TYPES of tickets (say, Adult, Youth, Child) with different base fees. You could even then tie field conditions to ticket types for more specific customization of the form.

In addition to a SINGLE ticket type, there could be an X-for-1 type. This could be used for a 2 for 1 married couple registration. The user clicks on "Married Couple" and instead of getting a single set of fields, they'd get TWO sets of fields on the same member reg page. No need for fee fields, or other crazy calculations.

Is this something other people would benefit from? Are we the only people offering couple discounts? Just curious.

thanks!

Please Log in or Create an account to join the conversation.

Time to create page: 0.245 seconds