Support

September 19, 2023 at 2:41 pm

Hi there,

We don’t provide support for custom code so I need to clarify that the above is not something we provide support for, reviewing custom code to fix bugs within that code would also not be covered under general support.

To get your app working you need to start by first fixing this request:

https://www.jazzyyc.com/wp-json/wp/v2/eventFeatured?1695154625

Notice how when you load that page its throwing a critical error, that’s what you need to start with.

You mentioned you fixed the above, but your code still isn’t correct.

Fatal error: Uncaught TypeError: Argument 1 passed to EE_Event::pretty_active_status()

Is happening because your code is running:

EEH_Event_View::event_active_status($post->ID, $echo);

When $echo hasn’t been defined, so its passing NULL and EE_Event::pretty_active_status() needs either true or false.

Anywhere you have this:

EEH_Event_View::event_active_status($post->ID, $echo);

Change it to be:

EEH_Event_View::event_active_status($post->ID, false);

(You declare $echo = true in one of your functions, but that means your echoing out the value to the page and again, that’s not something you want for these requests so set them to use false regardless)

If your code is still the same from above then fixing both instances of EEH_Event_View::event_active_status() as above will either get your page working again, or show you another fatal error.

i managed to fix the cronfeed issue, but now getting this in the front end

You fixed it? It’s still broken on the live site on the request sent by the app.

September 20, 2023 at 2:14 am

Could this have been related to the event espresso 5 update? Because the App was working perfectly before I did this

Sort of.

Your code was using EE_Event::pretty_active_status() incorrectly and one of the parameters being passed was NULL.

PHP is/was ‘loosely typed’, meaning if a function expects a specific type, say an int or bool (true/false) value but you passed in a string or null, PHP will carry on and try to convert/guess what the value should be.

PHP8+ adds much stricter typing within PHP and within PHP8 incorrect types start to throw fatal errors rather than just guessing what it should be (overall this is a good thing, being loosely typed is one of the reasons PHP has a ‘bad’ reputation within the developer community), so within Event Espresso we have started tightening our type declarations and that’s what you have run into here. Passing values to functions that aren’t expected causes problems, setting the type declarations prevents those but means you must use the function correctly or you’ll get fatal errors.

So yes, it’s partially due to the update but the root cause is not using the function correctly.