Custom Fields - Quantity Not Tracking Correctly

Tuan Pham Ngoc wrote: Hi Jet

I must be honest that so far, this feature is not used by many of our customers. This is also difficult to fix, I think. However, a bug is a bug and I need to fix it.

If you can give me the time to the end of this month (as I have to do other developments as well), that would be OK. We will fix and solve the issue

Certainly. I look forward to the update.

I have done something similar for a family reunion (cabins / rooms) and here is how I did it:
Each cabin was a category.
Our original plan was that each room was an event, each room had the capability to hold 6 people.
(Yes, this was a lot of setup, but in the end it worked quite well)
People could register for a room in a cabin, say they had a family of 4. This would allow 2 more registrants in that room.
If the new registrant had, we'll say a family of 3, it would not allow that registration, but if 2 more came along, it would. We eventually decided that we didn't want that, so we had each room with a capacity of 1 - Individual registrations only. This would now book the whole room (all 6 beds) to one person (their family). This way, a family of 4 wouldn't get another family of 2 registering for the same room. (I know, we were all related, so that shouldn't have been a problem, right? Well.... you never know.)
Now, for the cost... we had a custom field, a list: How many adults will be in the room? (kids were free) with a selection of 1-6, with the corresponding cost.
So, when someone would register for a room, it was an individual registration, they chose how many adults were in the room, and were charged accordingly. (You had to include yourself when counting how many adults - this was not how many additional adults, it was how many total adults were going to be in the room.)
So, my menu would bring them to the top cabin category, and the sub categories were each cabin, in each sub category were each of the rooms in the cabin. It worked out well as we didn't care if all 6 beds were taken / charged for - where we were, the venue gave us the cabins and only charged us for each adult that stayed.
Hope this helps! Let me know if you have any questions on this method.

This is causing some issues on my end also, would love to see its fixed / patched up for the moment

From what I tried this Quantity function of the Custom Fields still does not work.

If I rebuild the example of the manual with an event with a Quantity value set to 8 man and 8 woman I can register as many man I want as long as both values are not reached. Only when both values are 8 (OR MORE) the event is unavailable for new registration.

This is not the function as you would expect from the manual....

From the moment I have 8 man I only want woman to be able to register or the other way around and the event should be unavailable when both are at 8.

Hello Frank

That sound not right to me. Unless you are logging in using a super admin account, you should not be allowed to register more than 8 mans (with your setup)

Tuan

Bottom line is, if two people are in the registration screen and the first one clicks submit and takes the last custom field value, if a two minutes late the second user clicks submit, it should not let the second user check out / should return an error.

Just checking if this is something that was resolved or a solution to circumvent could be suggested? I too seem to be having an issue with registrants (in a similar timeframe) booking an even and selecting last available item from a quantity custom field. 

The idea that when one registrant is choosing a particular quantity item there is some restriction until booking is finalised and submitted sounds good. But it doesnt seem to be in play yet within Events Booking as I am still experiencing the issue.

Any updates on the situation, help or suggestions would be greatly appreciated. 

Actually, there is no good solution for this problem. I would suggest to use Ticket Types instead eventbookingdoc.joomservices.com/plugins/ticket-types

It has better validation. And another improvement to prevent over booking is that you can go to Events Booking -> Configuration, find the config option Count Awaiting Payment Registration Time (Minutes) and set it to 2 minutes for example

It will then count registrants from that 2 last minutes while validating the remaining capacity. It could reduce the change of overbooking, but of course, it is still not perfect

Tuan