|
Joost
|
May 11, 2022 at 10:20 am
Since a week or two we regularly get an error (“Your site has a technical problem”) when saving an event. Most of the event details are actually saved, but for instance the event location is not.
The WP error details are:
Foutdetails
===========
An error of the type E_ERROR is caused on line 453 of the file /home/plukdelief/domains/plukdeliefde.nl/public_html/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php. Foutmelding: Uncaught InvalidArgumentException: The "edit_tickets" array is invalid therefore the event can not be updated. in /home/plukdelief/domains/plukdeliefde.nl/public_html/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php:453
Stack trace:
#0 /home/plukdelief/domains/plukdeliefde.nl/public_html/wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php(285): espresso_events_Pricing_Hooks->_update_tickets(Object(EE_Event), Array, Array)
#1 /home/plukdelief/domains/plukdeliefde.nl/public_html/wp-content/plugins/event-espresso-core-reg/admin_pages/events/Events_Admin_Page.core.php(1055): espresso_events_Pricing_Hooks->datetime_and_tickets_caf_update(Object(EE_Event), Array)
#2 /home/plukdelief/domains/plukdeliefde.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php(1026): Events_Admin_Page->_insert_update_cpt_item(25603, Object(WP_Post))
#3 /home/plu
Any idea what could be wrong? And of course, how to fix it?
kind regards,
Joost
|
|
Tony
|
May 11, 2022 at 11:37 am
Hi there,
Can you open up an event where this normally happens and take a screenshot of the ‘Event Tickets & Datetimes’ section before you click update, please?
THen add that here:
https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots
|
|
Joost
|
May 11, 2022 at 1:04 pm
Hi Tony,
This is the screenshot: https://www.plukdeliefde.nl/wp-content/uploads/2022/05/screenshot-EE.png
The related event is: https://www.plukdeliefde.nl/events/polyborrel-schiedam/
The ticket menu is on purpose not shown on the event page.
Kind regards, Joost
|
|
Tony
|
May 13, 2022 at 4:35 am
Hi Joost,
Thank you for the screenshots, this section: https://monosnap.com/file/nzgdyT3xYOORX72wozbDghKSLvfn7u
Is not correct.
Every event within Event Espresso should always have at least 1 ticket on that event, that’s why you’re getting the fatal above, EE is trying to process the tickets and there should always be at least one but on your event you have none.
Ok, a couple of checks on the site.
Go to Event Espresso -> Pricing, on the ‘Default Pricing’ tab, what do you see? (screenshot)
Then on the Price Types tab, what do you see there? (Again screenshot)
|
|
Joost
|
May 23, 2022 at 11:30 am
Hi Tony,
Indeed, I’ve checked the events that generated the error message. If I add a ticket to them. The error dissapears. These are the screenshots you requested:
https://www.plukdeliefde.nl/wp-content/uploads/2022/05/Knipsel2.png
https://www.plukdeliefde.nl/wp-content/uploads/2022/05/Knipsel3.png
I guess you’re looking for a default price. We have none defined.
What is puzzling me is that we use EE for 7 years now. We’ve always had events that require no tickets. We never paid attention to adding a ticket for those events. So apparently something changed in the EE code? Or the default has changed? Frankly, I’d expect EE to robustly handle this kind of exceptions.
|
|
Tony
|
May 23, 2022 at 2:41 pm
The problem is Event Espresso 4’s whole registration system is based around tickets so I don’t see how the above could work at all.
So apparently something changed in the EE code?
Not as far as I am aware, the relationship between events, tickets, datetimes and price have been constant pretty much through EE4’s lifespan.
Or the default has changed?
Again, not as far as I am aware, but you’ve stated you never had tickets on the events either way, so the default wouldn’t have mattered?
All events require a ticket, all registrations require tickets, as mentioned EE’s entire system revolves around tickets and their relationships.
Frankly, I’d expect EE to robustly handle this kind of exceptions.
You would expect EE to handle an exception stating that something it requires to function is missing? I’m not sure how we would be able to do that?
EE has always required a ticket within an event, the default price I asked about is what is used to generate that initial ticket. That is now missing/has been removed, we don’t provide a UI to remove it, because again, it’s required.
|
|
Joost
|
May 24, 2022 at 3:05 am
Hi Tony,
I guess it’s a slight difference in perspective. We use EE as an event system. An event may or may not need tickets. To me, that is consistent with the backend option to show the ticket menu or not. And to me it feels odd that even if you decide not to show the ticket menu, you still need to define a ticket. It’s strange we never encountered this before in 7 years. But now at least I understand how to circumvent the error.
|
