TOPIC: Bug with Limits for a Conditional Field

Okay ... this is going to be tricky to explain, but I will try.

I have a campout event that will have two choices for folks to lodge - a group camp or off-site. The group camp has a limit of 250. The overall event has a limit of 425. Now, to set this up, I took a hint from your video and used a conditional field asking if registrants wanted to stay in the group camp. The conditions are Yes|No. I set the limits to 250|0 (the 425 limit for the overall campout is set in the general event capacity). Now...

If they choose "Yes" - I have it set to call another conditional textual field with some details pertaining to staying in the group camp.

If they choose "No" - I have it set to call another conditional field asking where they will be lodging (since it is not in the group camp).

Now, here is the potential bug in the software that might need addressing unless I am missing something. When the limit of 250 is filled on the "Yes" option, the "Yes" option no longer shows up (working as intended). The only option that shows up is the "No" option (again working as intended). However, it now incorrectly calls the conditional textual field with some details pertaining to staying in the group camp that was assigned to the "Yes" option (not working as intended - I don't think). It is like it based those options on an option 1 and option 2 in the code and since there was no option 1 now available (as it was limited out), it moved option 2 into option 1's spot, so that the next level of conditional fields will inadvertently lead to the wrong option.

Does that make sense? If not, i guess I can take the time to set it up on the demo server for your review.

What I need, and hopefully with the same diligent service you have been providing, is a solution to this. I have just a few more days to get this event registration rolling. That solution can come in either 1) a better way to set this up or 2) a fix so that the options call the right conditional field when a limit is reached.

BTW, my original intent is to also include a third option on this field, "waiting list." Since I couldn't figure out how to make a conditional field call up when a limit is reached, I had to leave it static as a third option with a textual about it when selected. However that is messed up too by the bug I described before. Is there a way to have a conditional field show up when a limit is reached?

Thanks again for your great support. Hopefully this is helping you make your great software better while you address all of these wild scenarios.

Sincerely,
Jonathan

Just a quick update. I managed a work around for this, as a result of having to change a few things up anyway, but the problem still exists.

Jonathan