|
Alex Stott
|
October 10, 2013 at 8:54 am
Sorry to have to post again, but the previous thread I started is now locked: https://eventespresso.com/topic/attendee-limit-not-modified-upon-purchase/
I was wondering how things were going with the issue that I raised there about attendee numbers not being modified correctly?
Many thanks for your help.
|
|
Sidney Harrell
|
October 10, 2013 at 1:03 pm
We are still working on it. We will update this thread when we have a solution. Thanks.
|
|
Alex Stott
|
October 17, 2013 at 4:12 am
Thank you Sidney, I realize it’s hard to put a timescale on problems that have yet to be fully investigated, but a fix would be appreciated, as this is causing significant issues for my client. Thanks again for your support.
|
|
Dean
|
October 17, 2013 at 4:51 am
Thanks for your feedback Alex. We are working to resolve this issue, but unfortunately it isn’t a simple fix and will require some core code edits. It is in our queue to do, and we have noted to update this post when it has been resolved and tested.
|
|
Alex Stott
|
October 25, 2013 at 4:09 am
Hi Dean, I appreciate this is an issue that requires a core change and is therefore not an immediate fix, but it has been two months since this was raised and this is causing immensely difficult issues for my client.
Is there any chance of a stop-gap solution or a way to work around this issue?
Many thanks for your time.
|
|
Dean
|
October 25, 2013 at 4:54 am
Hi Alex,
Thanks for getting back to us. The developers have recently reviewed this ticket and unfortunately a fix will not be possible in version 3.X due to the database structure, I am really sorry about that.
We have added a warning message into version 3.1.36 to advise people regarding using time slots and group registrations.
|
|
Alex Stott
|
October 25, 2013 at 4:59 am
Hi Dean, thank you for your reply. This is absolutely catastrophic for my client, what would the feasibility of switching to EE4 be? (I’m assuming this is not a problem in EE4?)
|
|
Dean
|
October 25, 2013 at 5:19 am
Hi Alex,
I fully understand that. From the current development version of EE 4, this feature no longer exists in the same way. Instead, it will allow you to create numerous tickets, rather than time slots, and limit the number of each ticket.
Feasibility of switching depends on your current set up. EE4 will be released as a bare bones product, a few basic gateways, and little to no addon support.
It will also require a fresh database, as it is a complete re-write and is not compatible with the 3.X database structure.
I also cannot say at this time, what features, including the ticket limitation, will be available in the initial release.
Sorry for being so vague, but as it is still under very active development, things change at a moments notice.
|
