Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Change Number of Tickets | Event Espresso - Staging Server
We have volunteers register for events. They register for X tickets which is tracked by EE.
Sometimes we need to change X to Y or X to 0 if they cancel and we want to keep their record just in case.
Will not allow me to change to 0 – why?
Jonathan, the volunteer changes their mind and does not want to come now. As such, we should be able to change his NUMBER OF TICKETS from 1 to o. That would also add 1 to the total number of tickets still available
We cannot change to 0. We also have the horrible problem of lost registrants who are not longer in the system. I know this is an EE db error but I am concerned about upgrading. Would try it first on our test system but the license issue keeps coming up which I am sure your team has had enough of already
Thanks
Regarding the zero tickets. Currently that isn’t possible, the attendee either has a ticket or they are deleted from the event. I personally think having the ability to leave attendees who cancel in the database could be useful, and this has been added to the feature request list, but the timescale is far into the future.
The lost attendees is definitely a known bug and we advise anyone on 3.1.28.x to update now.
The licence issue on the test system is their because you only have one licence which will be attached to the main site. This doesn’t stop you from downloading the files and manually updating your test site via FTP.
Viewing 3 reply threads
The support post ‘Change Number of Tickets’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.