I see for this registration 4 entries, all with their own ticket.
4 in total, the primary user registered the 3 other tickets with the additional registrants name.
Could that be the problem?
That’s not a problem. But if you want it named to registrant and not just the one who purchased the ticket, you have to go to your event -> then check the personal information under the questions for additional registrants. https://monosnap.com/file/Y4Esz0vYocdT2nzV0ronICaFQZ14l7
If you want separate tickets for all four registrations then you need to activate the “Questions for Additional Registrants”. Then at the checkout, it will ask for the information of more than one person as per the number of tickets.
Hi
Now I use the extra attendee information questions.
Any other suggestion how to resolve my issue that the registrant only sees 1 ticket purchased however it should be 4?
The reason the My Events section is only showing 1 ticket there is that it shows registrations that are related to the current user based on the registrant details. Its showing you YOUR registrations, the registrations in that group are linked to other contacts (the regisrant info didn’t match yours during registration) so they aren’t included.
However, it is possible to include those registrations using a different template:
Warning: Undefined property: wpdb::$use_mysqli in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-includes/class-wpdb.php on line 768 Warning: Cannot modify header information – headers already sent by (output started at /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-includes/class-wpdb.php:768) in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/modal_survey/modal_survey.php on line 2847 Warning: Cannot modify header information – headers already sent by (output started at /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-includes/class-wpdb.php:768) in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/modal_survey/modal_survey.php on line 2848 Warning: session_start(): Session cannot be started after headers have already been sent in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
That’s from WordPress 6.4 and is being thrown within the Model Survey plugin, it is something they will need to fix (or if there is an update for that plugin that may have fixed it already).
The warning related to Event Espresso there:
Warning: session_start(): Session cannot be started after headers have already been sent in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
Is happening because of the other warnings being output to the page.
(Side not, you should set your site not to display errors on a production site. Log them, but don’t display them on te front end as it prevents issues like this being visible to your users)
Warning: Undefined property: wpdb::$use_mysqli in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-includes/class-wpdb.php on line 768 Warning: session_start(): Session cannot be started after headers have already been sent in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
Warning: Undefined property: wpdb::$use_mysqli in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-includes/class-wpdb.php on line 768
This ‘error’, is a warning saying that something is using some code like $wpdb->use_mysqli and now in WP 6.4 they have removed that property.
Warning: session_start(): Session cannot be started after headers have already been sent in /customers/1/4/9/de-vriendenkring.eu/httpd.www/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
This warning is from Event Espresso trying to start a session, you can’t start a session when something has already been sent to the browser… the first warning above is being sent to the browser, which prevents EE from creating a session and this warning is thrown.
This means the warning from EE is happening because of the first warning (which isn’t related to EE).
The support post ‘[ESPRESSO_MY_EVENTS] ticket count not correct’ 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.
Support forum for Event Espresso 3 and Event Espresso 4.