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 Rolling Events | Event Espresso - Staging Server
It’s possible. What you could do is create an event that starts on march 1st and runs through nov 31st. Then sell the tickets like any other event. The ticket scanner app will accept/reject the ticket based on whether it has already been scanned. The attendee entry in the attendee reports will mark be marked as attended when the ticket is scanned.
If you need to set registrations limits for each date, then I’d suggest using the recurring events manager to create a series of events (one event for each date).
For people who want to purchase a ticket, but do not have a date in mind, we are using the EE Groupon add-on with gift certificates (http://www.suburbanmedia.net/wordpress-plugins/wp-gift-cert) that we issue on the site . Customers purchase the certificate and then use the certificate code in the Groupon entry field when registering for the session event.
We have to add the Groupon/Gift Certificate code manually, so it is not ideal, but our gift certificate business is small. You could also add the transaction ID from the rolling event to the Groupon codes and have the customer us that for registering on the day and not bother with the certificate.
Viewing 2 reply threads
The support post ‘Rolling Events’ 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.