TOPIC: Major issues with fields w. selection limits

Fields with selection limits are still not properly working in 2.7.1c while this feature has been introduced in version 2.6.9 already.

There were some little improvements in the 2.6.9 on this buggy functionality and now with 2.7.x we have big regression as you can have multiple bookings on same field (in a group booking and even on single booking) altough you have a selection limit defined.
Furthermore in a single registration the user cannot see what he has selected before when he want to change his registration at a later stage.
Even the administrator in the backend cannot see what a user has selected
(tested with drop-down lists with fee option) while on group registrations for every person you can see what was selected.

I have raised official tickets for those issues even during Beta phases on 2.7.0 early November - but so far no support on this.

As of situation today this functionality cannot be used at all which is causing highest frustation.

I totally agree with internetty66 on this one, I have already reported this feature not functionning properly and just submitted a new ticket as the problem is still there on 2.7.1c.

It is indeed very frustrating as the selection limit feature was the one thing that made me choose DT Register instead of other registration extensions

Exactly, this makes the difference between DT Register and other event registration components for Joomla and it is key functionality for me and my customers.
I very much appreciated the fact that such nice features have been implemented - but then I would expect that at least the key functions are working fine.
I can understand when there are some little issues on a new release. But the fields with selection limits have been introduced in 2.6.9 already as said before - and I have raised at least two tickets at that time and was very patient as I knew 2.7.0 will come out soon. I have now waited more than half a year and was very very disappointed when I started my tests being part of the Beta program and I realized that situation was even worse than before.
I understand that major issues on 2.7.0 and its general stability had to be fixed - but now we have a dozen of point releases for 2.7.x and I would now much appreciate if Nathan and his team would work on this issue.
For me it is definitely not a minor issue as the functionality with fields w. selection limits simply does not work and can therefore not used.
My threat is just to share my view with others while I started with a support ticket and the hope it will be fixed - but nothing and even my updates are not being acknowledged.

In 2.6.9, some bugs have been fixed and I was always surprised that only 5% of the problems have been reviewed while I am wondering whether a complete registration cycle including single/group registrations with changes and cancellations are being tested.

I really hope that Nathan and his team will now spend some time on this critical issue and fix it once and for all - not partially but completely !!!

So far no single update from DTReg team on my support ticket nor on my threat.

Including 2.6.9 issues I am waiting now more than half year on the solution of the problem with fields and selection limits - but no signal when this showstopper issue will be fixed.

I really hope that there will be more users putting pressure on DTH - because there is no acceptable workaround available.

I am normally not an aggressive guy and always calm and patient ...but this is just frustrating and makes me very angry.

No response from DTH on my tickets .....and I will post it here every week now.

I'll help bump this...I can't get selection limits to work either. I have an event occurring this weekend and all of my lodging options are actually sold out, but they are still selectable in the registration page. I even dropped the limits to "1" just to see if anything would change, and it doesn't.

What is the point of loading selection limits into the system if it is going to allow overbooking anyway?

Scott