PHP Fatal Error Crashing Site

Home Forums Ticket Products Event Tickets Plus PHP Fatal Error Crashing Site

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #1361081
    Derek
    Participant

    The site has been going down intermittently. Often it comes back on its own others times requires restart. I’ve found this error and think it may be related given the times its happening. Using php 7.1, it is suppose to write the time in america/chicago and some other errors are but this one shows as UTC. Dont know if its trying to use a older version of php it was upgraded from 5 around 2 years ago.

    [09-Oct-2017 12:11:40 UTC] PHP Fatal error: Uncaught Error: Class ‘Tribe__Tickets__Shortcodes__User_Event_Confirmation_List’ not found in C:\inetpub\wwwroot\wp-content\plugins\event-tickets\src\Tribe\Main.php:555
    Stack trace:
    #0 C:\inetpub\wwwroot\wp-content\plugins\event-tickets\src\Tribe\Main.php(179): Tribe__Tickets__Main->user_event_confirmation_list_shortcode()
    #1 C:\inetpub\wwwroot\wp-includes\class-wp-hook.php(298): Tribe__Tickets__Main->plugins_loaded(”)
    #2 C:\inetpub\wwwroot\wp-includes\class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array)
    #3 C:\inetpub\wwwroot\wp-includes\plugin.php(453): WP_Hook->do_action(Array)
    #4 C:\inetpub\wwwroot\wp-settings.php(325): do_action(‘plugins_loaded’)
    #5 C:\inetpub\wwwroot\wp-config.php(98): require_once(‘C:\\inetpub\\wwwr…’)
    #6 C:\inetpub\wwwroot\wp-load.php(37): require_once(‘C:\\inetpub\\wwwr…’)
    #7 C:\inetpub\wwwroot\wp-blog-header.php(13): require_once(‘C:\\inetpub\\wwwr…’)
    #8 C:\inetpub\wwwroot\index.php(17): require(‘C:\\inetpub\\wwwr…’)
    #9 {main}
    thrown in C:\inetpub\wwwroot\wp-content\plugins\event-tickets\src\Tribe\Main.php on line 555

    #1361236
    Derek
    Participant

    Looks like the UTC time stamp is the syslog writing it instead of the php.ini.

    I’ve noticed another message in the log related to events, it gives a huge out put of client information so I’m only including the start of it:

    wordpress database error got a packet bigger than ‘max_allowed_packet’ bytes for query insert into ‘wp_postmeta’ (post_id’, ‘meta_key’, ‘meta_value’) values (28950, ‘_transient_tribe_attendees’…..

    #1361767
    Andras
    Keymaster

    Hey Derek,

    Thanks for reaching out! I’m sorry about this issue you are experiencing.

    To be able to give you better support could you please share your system information with me?

    Also, you should be able to set your reply private, where you can safely share the other message you mentioned. The private replies are only visible to you and the support team.

    Thanks and cheers,
    Andras

    #1364389
    Derek
    Participant

    This reply is private.

    #1364451
    Andras
    Keymaster

    Hi Derek,

    Thanks for sharing that.

    errors […] shows as UTC

    I believe this is independent of your WordPress site setting. It likely is a server setting. So no matter what timezone your WordPress site is set to, this error log will take the setting from the server (or always uses UTC). No need to worry about this.

    I don’t see anything unusual in your sysinfo so we’ll need to dig further.

    We do have some errors reported coming from php 7.1. Though didn’t see anything similar to this, it could be caused  by that.

    We can do couple of things here:

    • Run a conflict test: please deactivate all plugins except for the calendar and ticket ones and check if you are still getting the error. If no errors, then activate woocommerce, then the other plugins one-by-one.
    • Try to switch to a different php version, i.e. 7.0 and try there
    • I will try to set up a php 7.1 test environment to check, this will take some time though

    Let me know if you find anything, and I’ll get back to you as soon as I have something.

    Cheers,
    Andras

    #1364602
    Derek
    Participant

    This reply is private.

    #1365189
    Andras
    Keymaster

    Thanks Derek, let me know when you have that virtual server up.

    Meanwhile I’ll try to ask for a second pair of eyes to take a look at this.

    Cheers,
    Andras

    #1365275
    Andras
    Keymaster

    Derek, I also got the recommendation to try to increase the max_allowed_packet size in mysql.

    This article might help:

    https://dev.mysql.com/doc/refman/5.7/en/packet-too-large.html

    Andras

    #1365352
    Derek
    Participant

    This reply is private.

    #1365845
    Andras
    Keymaster

    Thanks for reporting back!

    Wow, that sounds like a major cleanup. I do hope it will help.

    Nonetheless I stay at your disposal if you would need further assistance, and I’m looking forward to hear about your progress.

    One note I’d like to make, if there is no movement in the thread for 3 weeks, then it will be automatically closed. If this should ever happen and you still need help, then simply open a new thread and reference this one. Me or one of my colleagues will pick it up and help you out.

    Cheers,
    Andras

    #1365881
    Derek
    Participant

    This reply is private.

    #1366404
    Andras
    Keymaster

    Hi Derek,

    Sorry to hear that it’s not fully working yet, but it looks hopeful. At least the Calendar seems to be working now.

    Since this is marked resolved I am going to close this ticket, but if you need anything else related to this topic or another please create a new ticket and we’ll be here to help.

    Cheers,
    Andras

    PS: If you like our plugins, and you didn’t yet do so 🙂 we would be happy to receive a review in the wordpress.org repository. Thanks!
    https://wordpress.org/support/view/plugin-reviews/the-events-calendar/
    https://wordpress.org/support/view/plugin-reviews/event-tickets/

    PS2: We’d be also grateful if you would give us feedback on your satisfaction with support. Just click on one of the classy looking emojis below. 🙂 If you can spare a few words, that’s even better. Doublethanks!

     

Viewing 12 posts - 1 through 12 (of 12 total)
  • The topic ‘PHP Fatal Error Crashing Site’ is closed to new replies.