Fatal error 1.2.0

  • Resolved grupete

    (@grupete)


    4 years, 10 months ago

    Fatal error update 1.2.0

    wp-content/plugins/google-site-kit/includes/Core/Authentication/Clients/OAuth_Client.php. Mensaje de error: Uncaught Error: Class ‘Google\Site_Kit\Core\Authentication\Clients\Google_Proxy_Client’ not found in /wp-content/plugins/google-site-kit/includes/Core/Authentication/Clients/OAuth_Client.php:184
    Stack trace:
    #0 wp-content/plugins/google-site-kit/includes/Core/Modules/Module.php(631): Google\Site_Kit\Core\Authentication\Clients\OAuth_Client->get_client()
    #1 /wp-content/plugins/google-site-kit/includes/Core/Modules/Module.php(567): Google\Site_Kit\Core\Modules\Module->setup_client()
    #2 wp-content/plugins/google-site-kit/includes/Core/Modules/Module.php(440): Google\Site_Kit\Core\Modules\Module->get_client()
    #3 wp-content/plugins/google-site-kit/includes/Core/Modules/Module.php(233): Google\Site_Kit\Core\Modules\Module->execute_data_request(Object(Google\Site_Kit\

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

  • @grupete thanks for your report!

    Could you share from which version of Site Kit did you update?

    Thread Starter grupete

    (@grupete)

    @reneesoffice I was with version 1.1.4 and the recent automatic update of 1.2.0 jumped the error. I deleted it and reinstalled it but it continues with the error, the site goes down.

    @grupete thanks for the reply.

    Are you able to provide your Site Health information so we can see if anything could be conflicting?

    If you could safely deactivate your plugins or install Site Kit on another site to see if this issue persists there that might help. In any case, we’ll work on pinpointing the issue with more info about your setup.

    The plugin version 1.2.0 could not be activated because it triggered a fatal error.

    Warning: include(/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/vendor/composer/autoload_classmap.php): failed to open stream: No such file or directory in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 26

    Warning: include(): Failed opening ‘/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/vendor/composer/autoload_classmap.php’ for inclusion (include_path=’.:/opt/alt/php73/usr/share/pear’) in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 26

    Warning: include(/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/third-party/vendor/composer/autoload_classmap.php): failed to open stream: No such file or directory in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 28

    Warning: include(): Failed opening ‘/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/third-party/vendor/composer/autoload_classmap.php’ for inclusion (include_path=’.:/opt/alt/php73/usr/share/pear’) in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 28

    Warning: array_merge(): Expected parameter 1 to be an array, bool given in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 28

    Warning: require(/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/third-party/vendor/autoload_files.php): failed to open stream: No such file or directory in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 53

    Fatal error: require(): Failed opening required ‘/home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/third-party/vendor/autoload_files.php’ (include_path=’.:/opt/alt/php73/usr/share/pear’) in /home/a12345/domains/mysite.xyz/public_html/wp-content/plugins/site-kit-wp-1.2.0/includes/loader.php on line 53

    Plugin Support James Osborne

    (@jamesosborne)

    @softfully Can you please open a new support topic from where we can assist you.

    Ok visit at: https://www.ads-software.com/support/topic/triggered-a-fatal-error-10/

    It says: This post has been held for moderation by our automated system and will be manually reviewed by a moderator.

    A hard refresh of the browser (Shift + Command + R on Mac) to clear the browser cache resolved this fatal issue after updating the Site Kit Plugin for me.

    Plugin Support James Osborne

    (@jamesosborne)

    @grupete Did you have any success with the latest version of the plugin after following the suggested steps? If not can you download and install this mini plugin and install it as you would any other WordPress plugin?

    What you are encountering may be an OpCache issue. The plugin will reset OpCache after you access the Site Kit admin panel. You can find out more about the issue here.

    @grupete I’m following up to see if you had a chance to try the above and if it helped resolve the error?

    Plugin Support James Osborne

    (@jamesosborne)

    @grupete As we didn’t receive a response I will mark this as resolved. Feel free to open a new support topic if you continue to encounter issues.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fatal error 1.2.0’ is closed to new replies.