Reply to: tickets(387205)

Thank you. I have installed the version 4.9.8. Now it works fine.

But please check my home site. There i have featured events. If i click on one element i need many time to open it.

What can i do? Is it a bug?

Thanks for help.

Reply to: tickets(388195)

Downgrade to 4.9.7 worked and the error is gone: Filter and Main Calender working flawlessly again.

Reply to: tickets(388087)

Hi,

The first issue was really a bug. It wouldn’t load the calendars properly and that issue started suddenly, without changing any of the settings.

It was fixed by changing to the option “eventon content filter”.

Can you please help us to understand why this happened? Our client is requesting an explanation why this happened.

 

Thank you

Reply to: tickets(388195)

https://www.swisstransfer.com/d/c6e09a80-6cb9-4d0b-8bdc-acce23e15089

here is the complete log for ~20minutes

 

best,
K

Reply to: tickets(388195)

so i deep dived into this: the main calender has always the same problem in the frontend (not logged in). in the backend everything works “fine”. switching it to “list mode” in the frontend, does the trick, except for the search and filter. same error as in the “main calender”.

log always has the same fatal error:

[23-May-2025 08:38:41 UTC] PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, non-static method EVO_AJAX::restrict_unauthenticated() cannot be called statically in /var/www/vhosts/e***/wp-includes/class-wp-hook.php:324
Stack trace:
#0 /var/www/vhosts/e***/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#1 /var/www/vhosts/e***/wp-includes/plugin.php(517): WP_Hook->do_action()
#2 /var/www/vhosts/e***/wp-admin/admin-ajax.php(207): do_action()
#3 {main}
thrown in /var/www/vhosts/e***/wp-includes/class-wp-hook.php on line 324

is this a rights problem? any suggestions?

thanks in advance,
K

Reply to: tickets(388033)

Thank you so much for the explanation and your helpful suggestion! That’s incredibly kind of you. It’s great to know that this will be added as an option in the Ticket settings in the next version – that will make things much easier for us.

Thanks again for your excellent support!

Reply to: tickets(388250)

Hi

we have deactivated the Wordfence plugin on the staging site, so you should now be able to log in.

thanks

Ken