Catachable fatal error

  • Resolved Pewit

    (@pewit)


    8 years, 6 months ago

    We are using EventBrite for event booking and I was under the impression that we needed to install the Eventbrite Plugin (and Keyring) to embed the booking form in the website.
    Subsequently, I discovered that EB uses an iFrame and no plugin is required, so I removed both EB and Keyring plugins.
    The latest update to WP has caused the website to crash showing the following error:
    Catchable fatal error: Argument 1 passed to Keyring_Service::set_token() must be an instance of Keyring_Access_Token, boolean given, called in /home/fgggayms/public_html/wp/wp-content/plugins/eventbrite-api/inc/class-eventbrite-api.php on line 31 and defined in /home/fgggayms/public_html/wp/wp-content/plugins/keyring/service.php on line 300

    Needless to say, there is no plugin folder plugins/keyring or plugins/eventbrite-api.

    Questions
    – Where is the code that’s causing this error?
    – Why don’t the plugins which were removed using the WP Admin console uninstall correctly?
    – How do I restore the site and remove all trace of Keyring and Eventbrite plugins?

    Paul
    Admin, gaygames.org

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Pewit

    (@pewit)

    PING!!!!!!!!!!!!

    Does anyone read this support forum?

    Plugin Author Automattic

    (@automattic)

    Hi Pewit,

    Removing the plugins normally should certainly eliminate them; if there are still folders for the plugins in your wp-content/plugin folder, they can also be removed manually (by FTP, for example).

    The other possibility is that you have theme code that’s trying to use those plugins (which are now nowhere to be found)? When you removed the plugins, how did you go about displaying events on the site, with the Eventbrite ticket widget?

    Plugin Author Automattic

    (@automattic)

    Closing; just open a new thread if you’re still having issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Catachable fatal error’ is closed to new replies.