Support

Home Forums Event Espresso Premium PHP fatal error in EEH_Schema.helper.php

PHP fatal error in EEH_Schema.helper.php

Posted: February 20, 2017 at 8:38 am


David Dadekian

February 20, 2017 at 8:38 am

I’ve received this error several times in the past few days, as recently as this morning:

[20-Feb-2017 13:42:51 UTC] PHP Fatal error: Call to a member function start_date() on a non-object in /home/sounds9/public_html/eatdrinkri.com/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Schema.helper.php on line 44

I’m running the most the most recent version 4.9.30.p. Thank you.


Josh

  • Support Staff

February 20, 2017 at 8:54 am

Hi David,

Do you know which page on your website triggers the fatal error?


David Dadekian

February 20, 2017 at 8:56 am

Unfortunately, no, that’s the full line of info from the error_log file. Is there an EE log?


Josh

  • Support Staff

February 20, 2017 at 9:26 am

There’s a way to turn on EE logging, but if you turn the EE logging on it may not point to the page that’s causing the error.

What appears to be happening is there’s a page somewhere on your site that’s trying to load an event, but that event does not have a primary date time.


David Dadekian

February 20, 2017 at 9:48 am

Hmm, I have no idea what that could be. I have five current events, all with dates and times.


Josh

  • Support Staff

February 20, 2017 at 9:56 am

It may be an event that’s not current. Like for example if there’s a page on the front end of the website that’s trying to loading information about an event that’s in the trash.


David Dadekian

February 20, 2017 at 10:45 am

I don’t see anything like that, but I’ll try to figure that out. Thanks.


Tony

  • Support Staff

February 21, 2017 at 5:07 am

Hi David,

This will happen if you preview an event before it has been saved as draft or published.

So for example if you go to Event Espresso -> Events -> Add Event.

Give the event a title (say ‘example event’) and then use the permalink to preview the event.

The datetimes have not been created for the event yet as it has not been saved so there is no primary datetime and that error is thrown. Once you save/publish the event the datetimes are created and the error will no longer be thrown.

So have you recently been creating new events and previewed one of them?


David Dadekian

February 21, 2017 at 2:13 pm

No. I have no draft events and I haven’t viewed any non-saved events recently. It’s possible an employee did, though I don’t see anything new and I got the error three more times today.


Tony

  • Support Staff

February 22, 2017 at 4:03 am

In the next version of EE we have included some code to prevent the fatal error from happening (the function will check for a valid datetime, if there isn’t one it will not output any details from EEH_Schema).

So that will prevent the error I mentioned and should prevent the fatal error on your site however other than the above scenario this is not something we have been able to reproduce so I’m not sure why you’re getting the error on your site.

I can give you some steps you can use to help narrow down the Event that is causing this if you are comfortable working with PHP?

On most of my test sites I uses a snippet similar to this in my theme’s functions.php file: http://www.stumiller.me/sending-output-to-the-wordpress-debug-log/

It’s just a way to write to the error log but the above will only write to the log if WP_DEBUG is enabled. To enable WP_DEBUG I use THIS to log errors within /wp-content/debug.log but not display the errors on the page.

If you add that to your site you can then add something like this:

if(! $event->primary_datetime() instanceof EE_Datetime) {
	write_log($event);
}

Within \core\helpers\EEH_Schema.helper.php on line 27, above the $template_argshttp://take.ms/N3Jzs

Now what will happen is under the condition that fatal error would be thrown on your site, it will write the $event variable values to the debug.log file which means you can see the EVT_ID and EVT_name that is throwing the error – http://take.ms/Wlytw

Run through the steps I posted above to get the fatal error to be thrown so you can confirm its working, then just wait for another instance of the error to be thrown and check the log file to see which event causes it.

Your modifications to EEH_Schema.helper.php will be lost when you update Event Espresso and the fix we are including will be used but it does not show why the error is being thrown, it just prevents it from happening the above is just an option for finding the cause.

The support post ‘PHP fatal error in EEH_Schema.helper.php’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Tony 2 years, 4 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!