Fatal Error Suddenly Appeared

  • Resolved charmedchicken

    (@charmedchicken)


    2 days, 4 hours ago

    I went to log into my website after working on it just fine last night and received fatal errors:

    An error of type E_ERROR was caused in line 162 of the file /home/(directory)/(URL)/wp-content/plugins/event-tickets/common/src/Common/Libraries/Harbor.php. Error message: Uncaught Error: Call to undefined method Tribe__PUE__Checker::is_key_valid() in /home/(directory)/(URL)/wp-content/plugins/event-tickets/common/src/Common/Libraries/Harbor.php:162 Stack trace: #0 /home/chiclezd/petgriefpathfinder.com/wp-includes/class-wp-hook.php(341): TEC\Common\Libraries\Harbor->register_legacy_licenses() #1 /home/(directory)/(URL)/wp-includes/plugin.php(205): WP_Hook->apply_filters() #2 /home/(directory)/(URL)/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/harbor/src/Harbor/Legacy/License_Repository.php(32): apply_filters() #3 /home/(directory)/(URL)/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/harbor/src/Harbor/Legacy/License_Repository.php(76): TEC\Common\LiquidWeb\Harbor\Legacy\License_Repository->all() #4 /home/(directory)/(URL)/wp-content/plugins/event-tickets/common/vendor/vendor-prefixed/stellarwp/harbor/src/Harbor/Legacy/Notices/License_Notice_Handler.php(75): TEC\Common\LiquidWeb\Harbor\Legacy\License_Repository->all_inactive() #5 /home/(directory)/(URL)/wp-includes/class-wp-hook.php(339): TEC\Common\LiquidWeb\Harbor\Legacy\Notices\License_Notice_Handler->display() #6 /home/(directory)/(URL)/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #7 /home/(directory)/(URL)/wp-includes/plugin.php(522): WP_Hook->do_action() #8 /home/(directory)/(URL)/wp-admin/admin-header.php(313): do_action() #9 /home/(directory)/(URL)/wp-admin/index.php(137): require_once('/home/chiclezd/...') #10 {main} thrown

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Dimitris Pantazis

    (@dpantazis)

    2 days, 4 hours ago

    hey @charmedchicken,

    Can you help us a bit more with some information ? What were you doing when you received the error ?

    Have you by any chance any customization where you overwrite the default Tribe__PUE__Checker implementation ?

    The more details you can provide us for us to reproduce, the faster we will fix it.

    Thank you,
    Dimi

    Thread Starter charmedchicken

    (@charmedchicken)

    2 days, 4 hours ago

    Error appeared immediately after logging into wp-admin. AFAIK I wasn’t doing anything.

    No customization to that item.

    I did add a custom line in the <head> tag using the free WP Code plugin last night to add some information for formr forms, but then did quite a bit more updates creating a page/adding content/etc. and never received any error messages.

    Plugin Author Dimitris Pantazis

    (@dpantazis)

    2 days, 4 hours ago

    Ok thank you. Is that error consistent ? So you get it every time if you do a specific set of actions ? Or was it just a one off ?

    if it is consistent, all that you are doing is just opening your wp-admin to receive it ?

    Thread Starter charmedchicken

    (@charmedchicken)

    2 days, 3 hours ago

    It has been consistent this afternoon. I simply type in (url)/wp-admin and hit enter in my browser and I get the fatal error message and email from wordpress. I have to go into recovery mode with both event tickets and the events calendar plugins deactivated in order to access my admin site. (Note I also made a post on the events calendar so you’d have a record on both plugins.)

    Plugin Author Dimitris Pantazis

    (@dpantazis)

    1 day, 9 hours ago

    Hey @charmedchicken,

    Latest release is meant to also address the issue you faced.

    Could you please confirm ?

    Thank you!

    Thread Starter charmedchicken

    (@charmedchicken)

    1 day, 8 hours ago

    Yes. I have upgraded both plugins and it allowed me to exit recovery mode without an additional fatal error. Thanks.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.