Front end browser throws error of “Internal error. Please try again later.” after selecting service and worker that has no more slots available in month selected in calendar widget.
Back end server error is thrown:
[Tue Aug 30 19:00:55.114813 2022] [php:notice] [pid 355914] [client 126.96.36.199:52206] B\xc5\x82\xc4\x85d Incorrect DATE value: ‘-00-01’ bazy danych WordPressa podczas wykonywania zapytania SELECT * FROM wp_ea_connections WHERE \n\t\t\tlocation=1 AND \n\t\t\tservice=14 AND \n\t\t\tworker=15 AND \n\t\t\tday_of_week LIKE ‘%Tuesday%’ AND \n\t\t\tis_working = 1 AND \n\t\t\t(day_from IS NULL OR day_from <= ‘-00-01’) AND \n\t\t\t(day_to IS NULL OR day_to >= ‘-00-01’) wys\xc5\x82anego przez do_action(‘wp_ajax_nopriv_ea_month_status’), WP_Hook->do_action, WP_Hook->apply_filters, EAAjax->ajax_month_status, EAReport->get_available_dates, EAReport->get_whole_month_slots, EALogic->get_open_slots, W3TC\\DbCache_WpdbNew->query, W3TC\\DbCache_WpdbInjection_QueryCaching->query, W3TC\\_CallUnderlying->query, W3TC\\DbCache_WpdbNew->query, W3TC\\DbCache_WpdbInjection->query, W3TC\\DbCache_WpdbNew->default_query, referer: https://poradniabraincare.pl/umow/
Indicating use of wrong date notation like day_from <= ‘-00-01’.
Way to reproduce:
- Open reservation applet and select service + worker that has no more available slots for month displayed
In our case:
- open https://poradniabraincare.pl/umow.
- In Usługa select “Integracja sensoryczna”
- In Specjalista select “Terapeutka Manuela”
- Observe Internal Error popup
Hi, I have tried two times with that combination and other one and I was able to book appointment. Do you still have that issue, can you please check again?
Thank you for checking on our system. While you were testing I was also checking and noticed another error in the log of apache. Apparently it wasn’t Easy Appointment causing the problem per se rather than W3 Total Cache plugin.
I disabled the W3TC and it all works fine now. Still wonder what one has to do with the other but anyways.
I am sorry I wasted your time on something that wasn’t in fact EA fault. I swear I didn’t see the other log entry before.