• Resolved aurumriviera

    (@aurumriviera)


    Hello!

    My webpage crashed a couple of days ago and i have narrowed that it was Site Kit. I deactivated the plugin and have tried to reactivate it – but it triggers a fatal error with the following message:

    Plugin could not be activated because it triggered a fatal error.

    Warning: require_once(/home1/phoenme3/public_html/wp-content/plugins/google-site-kit/includes/loader.php): Failed to open stream: No such file or directory in /home1/phoenme3/public_html/wp-content/plugins/google-site-kit/google-site-kit.php on line 109

    I have tried to uninstall the plugin, as suggested by other users, but it shows this error message:

    Deletion failed: There has been a critical error on this website.

    Are there other steps I can take?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi @aurumriviera,

    Thanks for getting in touch. Fatal errors, such as the one you’re encountering can be as a result of a number of things. In your case it may be possible there was a Site Kit file removed or missing somehow.

    In order to resolve this can you share whether your comfortable manually removing or renaming the Site Kit plugin directory? If so you’ll need FTP access, or alternatively you can access your file manager from your hosting control panel. The location of the Site Kit directory, which needs to be removed or renamed is “wp-content/plugins/google-site-kit“. If you’re not comfortable locting and removing/renaming this directory your hosting provider should be able to assist. Once removed or renamed you can then try to install the plugin once more.

    Let me know how you get on, or if you’re unsure of the above.

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

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

The topic ‘Plugin Fatal Error’ is closed to new replies.