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 Bug in Seating Chart Selection | Event Espresso - Staging Server
When a seat is purchased, we receive confirmation from WordPress that seat is purchased, however, the seat is still being shown on seating chart as being available and open. Payment was even charged to the buyer, but their seat is still available. How can we resolve this asap. It has happened to multiple buyers. With seat still being available we are receiving multiple buyers of same seat, and receiving multiple confirmation emails of same seat being purchased (each buyer is being charged for the same seat.)
If you click to select a seat in some cases, the seat sells, but still shows available on the seating chart. Examples of some seats that have already sold are go to “Section Side Right” (far right scroll) and see seats CC374, CC373 and BB374, BB373 (rows 2 (BB) and 3 (CC) in “Section Side Right” all the way to the right of that section. Thanks!
Sorry for the delay. I logged into your site and noticed that you have a caching plugin installed on your WP site. So, what is probably happening, is the page with the seating chart is being cached and serving up an outdated version of the seating and possibly the old data. I would highly recommend turning off caching on the seating chart page, or disabling the caching plugin all together.
Viewing 4 reply threads
The support post ‘Bug in Seating Chart Selection’ 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.