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 Seating Plan add on and upgrade | Event Espresso - Staging Server
We are currently running Event Espresso (version 3.1.33.3.P). We are about to add the Seating Plan add on. Should we upgrade to EE4 while we are working on the site? We are using the following add-ons:
– Calendar
– MailChimp Integration
– Members Addon
– Multi Event Registration
– Ticketing
We also just wanted to check that when a particular seat is booked, that seat number does show in the e-ticket.
No. If you require all of those add ons, upgrading to EE4 will not work for you, as it does NOT support EE3 add ons and there are NO EE4 addons available currently.
The only one you would be ok with is Multi Event Registration as EE4 contains pretty much all of that plugin built in.
Regarding the ticket, the seat number is automatically added – http://take.ms/JYCMF
Yes, I would recommend keeping up to date with the latest version if possible so that would be 3.1.36.4 currently.
Viewing 4 reply threads
The support post ‘Seating Plan add on and upgrade’ 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.