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
Close a session | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Close a session

Close a session

Posted: January 20, 2014 at 10:32 pm

Viewing 5 reply threads


Monica Reina

January 20, 2014 at 10:32 pm

I’ve got a single event with 3 sessions- they’re the same event repeated three times during the day. One session is pretty much full now.

If I delete it as a ticket option- is this going to cause a problem with the one’s who’ve already registered? IS there a way to suppress just that session from the Event Page dropdown? This is Event Espresso – 3.1.36.1.P and WordPress 3.8. http://www.fcpworks.com/special_event/

Thanks!


Dean

  • Support Staff

    •

January 21, 2014 at 4:50 am

Hi Monica,

Deleting it should not cause any issues UNLESS you update the attendee in the admin. Then it will realise the ticket type is missing and it will revert to the first ticket type on the event.

Ideally if it can be avoided, don’t delete it, as we haven’t fully tested the repercussions of deleting it.

Currently the only workaround is to use 3 events, one per ticket type.

EE4 will rectify that by allowing limits per ticket type (a feature I am very much looking forward to!)


Monica Reina

January 21, 2014 at 11:20 am

I ended up changing the name of the ticket to WAITLIST and leaving it as an option. So far this seems to be working. +1 for session limits as an upcoming feature.


Monica Reina

January 21, 2014 at 11:22 am

So to clarify- if I now go back and update any aspect of an attendee- i.e. fixing their email address or adding some notes and hit update- they’ll get the updated session name on their ticket? I.e. it will appear as if they’re waitlisted.

But if I don’t touch the attendee they will continue to see the original ticket before the name was changed to waitlisted?

Just want to make sure I don’t confuse anyone.


Sidney Harrell

  • Support Staff

    •

January 21, 2014 at 11:34 am

Correct. The ticket option name that appears on the ticket is what is pulled out of the attendee record in the database. So if the attendee is not updated in the admin, then that ticket option name will be what the attendee saw when they were registering. If you do accidentally change a ticket option name on the attendee, it is possible to go into the database and change it back if you are comfortable using phpMyAdmin or the Adminer plugin.


Monica Reina

January 21, 2014 at 3:14 pm

Thanks Sydney very good info to have.
Viewing 5 reply threads

The support post ‘Close a session’ 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.

The original Forum description...

Status: closed

Updated by Monica Reina 11 years ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server