Hello,
We are experiencing a critical issue with the EventON Bookings addon that is currently affecting our ticket sales workflow.
Context:
We are using EventON with the following addons:
* EventON (core)
* Event Tickets
* EventON Bookings
* EventON Variations
This setup has worked correctly in the past, allowing us to:
* Create multiple date/time slots
* Display them in the calendar view
* Let users select a slot and proceed to purchase via WooCommerce
Current issue:
When the Bookings addon is active:
* The booking slots fail to load correctly in both:
* Event page
* Popup (lightbox) view
* The purchase flow breaks:
* The popup does not fully open or freezes
* The “Add to Cart” / “Buy Tickets” buttons do not appear or stop working
* In some cases, the interface becomes unresponsive
When Bookings is disabled, everything works correctly:
* Events load normally
* Ticket purchase works without any issue
Additional details:
* We updated Event Tickets to version 2.5.6
* We tested Bookings versions 1.4.7 and 1.4.8 → same issue
* Variations works correctly on its own (without Bookings)
* WooCommerce checkout works correctly (used daily for concerts)
Important:
This issue also affects previously working events when new booking slots are added.
Conclusion:
The problem seems to be a compatibility issue between:
* EventON Bookings
* Event Tickets / Variations
* Possibly recent updates or frontend behavior (AJAX / popup)
We need:
* Confirmation of compatibility between current versions
* Known issues related to Bookings + Tickets + Variations
* Recommended configuration for using Bookings with WooCommerce checkout
* Any required settings to ensure proper slot loading and purchase flow
This is urgent as it is blocking ticket sales.
Thank you in advance for your help.
Best regards,
- Apr 27,2026 AT 9:09AM - 2 months agoHello,
Could you update Variations add-on and check again?
Please also try updating Seats add-on as well.
To update eventon addons: You can download latest eventon addons from
. Then you can go to your website, deactivate old addon and install new one and activate then delete the old addon.
will further explain the process. Also you can follow us on twitter to get real-time announcements on updates!
I have updated ticket variations & options and deactivated Seats but it still makes the same error.
The purchase buttons for products using the Bookings add-on are also not working. Please note this is very urgent, as many customers are contacting us and are currently waiting for a solution. Thank you for your help with resolving this issue.
Regards
/wp-admin page is empty for me.
When I try to login using /wp-login.php I get this error:
Error: las cookies se han bloqueado debido a un resultado inesperado. Para obtener ayuda, por favor, revisa esta documentación o inténtalo en los foros de soporte.
But I’ve tried multiple browsers and it shows the same error.
I ve been updating and working on the web and finally I have just recovered a backup from last night. Now you can access.
Thank you very much
Hello,
I wanted to send you an update on the issue we have been experiencing, as we have now been able to isolate the problem more precisely.
We had a critical issue on our website affecting EventON ticket sales with seating maps. The main symptoms were:
TypeError: undefined is not an object (evaluating 'BUS.templ[OPT.part]')
The error pointed to:
eventon_functions.js
Specifically around the line where EventON tries to compile an internal template:
template = Handlebars.compile( BUS.templ[ OPT.part ] );
During troubleshooting, we tested several possible causes:
After restoring the backup, the problem persisted as long as the latest version of EventON Ticket Variations & Optionswas active.
We then tested by deactivating EventON Ticket Variations & Options, and the seating map loaded correctly again.
Since this addon is essential for us — we need customers to select a seat and then choose between ticket types such as General and Reduced — we could not leave it disabled.
We then reverted EventON Ticket Variations & Options from version 1.1.16 to version 1.1.12.
After reverting to 1.1.12, everything started working again:
So the issue appears to be specifically related to EventON Ticket Variations & Options 1.1.16 in combination with our current EventON / Tickets / Seats setup.
Our current working setup is:
Could you please check whether there is a compatibility issue or bug in Ticket Variations & Options 1.1.16, especially related to seating maps and the internal BUS.templ[OPT.part] template handling?
Thank you for your help
Best regards
Also EventOn Bookings 1.4.8
Since you use Avada you need to go to EventON > Diagnose > enable Disable saving all Fusion/Avada related data into events.
I did, but, for example, ”ESCUELAS PÍAS / ENTRADA GENERAL Y REDUCIDA (VISITA LIBRE)” still has the issue.
In my newly created event variations do work:
https://arsmagna.live/events/test/
It seems that because of Avada your old events aren’t saving correctly, so that’s why they don’t work.
I also cannot enable Troubleshooting Mode:
https://arsmagna.live/wp-admin/site-health.php?tab=troubleshoot
Could you please try the instructions mentioned in this
?
I am also going to escalate this ticket to development to help in here. Please allow us some time to address this, and we truly appreciate your patience. Thank you for being a valued EventON customer!
Please help me
Hello,
A quick additional update.
After reverting EventON Ticket Variations & Options from version 1.1.16 back to 1.1.12, the seating map initially worked again. However, the issue came back shortly afterwards.
We discovered that the newer version 1.1.16 had not been completely removed from the site. It had only been deactivated/uninstalled, but it was still present in the plugins area/server. At some point, WordPress appeared to switch back to the newer version, so 1.1.12 became inactive and 1.1.16 became active again.
Once we fully deleted version 1.1.16 and left only Ticket Variations & Options 1.1.12 installed and active, the seating map, ticket type selection, cart and checkout started working correctly again.
So, for our current setup:
There is still one remaining issue: EventON Bookings is not working correctly. The booking form is displayed, and the ticket type selection appears, but when trying to add a booking to the cart, it does not pass the booking/product correctly to WooCommerce cart.
Best regards,
Hello,
Thank you for reply. Please check this.
One important clarification: we already tried recreating the affected Escuelas Pías booking event from scratch yesterday, but the issue still remained. The booking form displayed correctly, the date/time slot could be selected, and the General/Reduced variation selector appeared, but the booking still did not pass correctly to the WooCommerce cart.
So I do not think the issue is only caused by old Avada/Fusion data stored in the original event.
Current findings:
The issue seems more specifically related to the combination of:
Could you please ask development to check whether Bookings is fully compatible?
The key problem is: the booking/date/time and ticket type can be selected, but the final selection is not correctly added to the cart.
Best regards,
Hello,
We have another important update.
When EventON Bookings slots are enabled, the add-to-cart button remains stuck in a loading/processing state and never completes.
In the browser console we see this JavaScript error:
Uncaught TypeError: Cannot read properties of undefined (reading 'undefined')
The error points to:
evobo_script.js
Specifically around:
draw_blocks
So it seems that the Bookings script is trying to process/draw the selected booking blocks, but some expected internal data is undefined.
The visible behaviour is:
Because customers are already asking for available dates, we urgently need a stable workaround or fix.
For now, we may have to stop using Bookings and create normal EventON ticketed events per date, but we would appreciate your development team checking this evobo_script.js / draw_blocks error as soon as possible.
Best regards
Kindly update to the latest version of booking addon 1.4.9
that will resolve this issue.