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
Can’t edit event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Can’t edit event

Can’t edit event

Posted: June 29, 2013 at 11:25 am

Viewing 6 reply threads


Joël van de Pol

June 29, 2013 at 11:25 am

I encounter a problem when trying to edit an event. Some of the options are not saved. This occurred when trying to change the seating plan (somehow I managed to change it by choosing no seating plan first, saving and then changing it to another seating plan). AND it occures when trying to change the option “Anmeldeinformationen für zusätzliche Teilnehmer?”, and I couldn’t find a way to make it work. I REALLY need to change this options, so please help me with a fix.


Seth Shoultes

  • Support Staff

    •

June 30, 2013 at 12:25 am

Hi Joël,

So the “Additional Attendee Registration info?” option is not saving, correct? I believe that is the way the seating chart system was built. Because the system needs to have the information for each seat assigned to a ticket.

It is possible to remove this limitation, but it takes a bit of custom development at this time. However, I believe there is an option to copy the first attendees details into each additional seat, which can be used as a work around.


Joël van de Pol

June 30, 2013 at 3:45 am

And where is that option?


Joël van de Pol

July 1, 2013 at 7:17 am

Can you please tell me which files to modify to remove this limitation? I can’t find the according functions.


Joël van de Pol

July 2, 2013 at 11:48 am

Okay, I managed to make customized versions of event_espresso_additional_attendees() and event_espresso_add_attendees_to_db() to solve this problem. Another problem is that confirmation mails are send out to every attendee. As the data of the secondary attendees is just copied from the first, the person who registers will get multiple confirmation mails, which is confusing. This should all be resolved in future releases.


Sidney Harrell

  • Support Staff

    •

July 3, 2013 at 7:40 pm

Adding this should make it so that only the primary attendee gets the confirmation email:

link to gist: https://gist.github.com/sidharrell/5924285


Joël van de Pol

July 8, 2013 at 6:35 am

Thanks. That didn’t work, but I resolved the problem by writing a customized email_by_session_id function.
Viewing 6 reply threads

The support post ‘Can’t edit event’ 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 Joël van de Pol 11 years, 6 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server