Returns Fatal Error on activation

  • tried ver 1.0 via download to ftp, download to upload and when activating it returned a fatal error.

    Using current version of thesis 1.8

Viewing 15 replies - 1 through 15 (of 17 total)

  • yerp… same here.

    Plugin Author kbm

    (@kbm)

    Hello Mike and eisham,

    I would like to reproduce and resolve your issues right away. If you would do me the great favor of providing me with some more data, I will investigate and resolve these issues as soon as I can:

    • Your PHP version<
    • Your WordPress version
    • Your theme name – eisham, are you also using Thesis?
    • Relevant error messages, either in the browser or your server log.
    Thread Starter Mike Mueller

    (@mikemueller)

    No worries!

    PHP version is 5.2.14
    WP Version is 3.1.1

    Fatal error: Cannot redeclare class OAuthException in /home/vasvcfk/public_html/wp-content/plugins/official-google-site-verification-plugin/external/php-client/external/OAuth.php on line 24

    Plugin Author kbm

    (@kbm)

    Thanks a lot for the feedback, that was enough information to be helpful. I made a change to the plugin that will most likely resolve your issue. Would you mind downloading the latest version of the plugin and trying again?

    I just tried installing the plugin just now and am getting a http500 server error when I click on start verification. I am running WP 3.1.1 and PHP version 5.3.6

    Plugin Author kbm

    (@kbm)

    dmcglathery: What was the URL of the page serving the HTTP 500 error? Thanks.

    Hello,
    i receive this error:

    Fatal error: Uncaught exception ‘Exception’ with message ‘The Google PHP API Library needs the CURL PHP extension’
    in /var/www/mysite/wp-content/plugins/official-google-site-verification-plugin/external/php-client/apiClient.php:22 Stack trace: #0
    /var/www/mysite/wp-content/plugins/official-google-site-verification-plugin/googleSiteVerification.php(34): require_once() #1 /var/www/mysite/wp-admin/plugins.php(149): include(‘/var/www/chicch…’) #2 /var/www/mysite/wp-admin/plugins.php(151): plugin_sandbox_scrape(‘official-google…’) #3 {main} thrown in /var/www/mysite/wp-content/plugins/official-google-site-verification-plugin/external/php-client/apiClient.php on line 22

    why?

    Thread Starter Mike Mueller

    (@mikemueller)

    Just had a chance to use the new version and it worked like a charm!
    5 stars!

    Plugin Author kbm

    (@kbm)

    Mastone:

    The plugin needs a special software library to work properly, the CURL PHP extension. The plugin won’t work if the library isn’t available. You could install PHP with CURL support, or ask your administrator to install support for it.

    Failing that, you can use our fine Verification user interface to get a verification META token, and place that in the <head> tag of your theme’s header.php file. This is the exact same process that this verification plugin automates.

    I just tried it as well, and got this error:

    “Verifying your blog… failed, due to an error:

    Error calling https://www.googleapis.com/siteVerification/v1/webResource?verificationMethod=META&alt=json: (400) The necessary verification token could not be found on your site.”

    PHP Version: 5.2.15
    WordPress Version: 3.1.1
    Theme Version: Catalyst 1.1.2
    Child Theme Version: Dynamik 1.1

    Thanks in advance for any help ??

    I just installed through the Add Plugin admin UI and get a different, and strange to me, error after clicking the Start Verification button:

    Fatal error: Uncaught exception 'apiIOException' with message 'HTTP Error: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed' in /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/io/apiCurlIO.php:126 Stack trace: #0 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(191): apiCurlIO->makeRequest(Object(apiHttpRequest)) #1 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(171): apiOAuth->requestRequestToken('https://billsays...') #2 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(89): apiOAuth->obtainRequestToken('https://billsays...', '4db5d4c755eff') #3 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification in /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/io/apiCurlIO.php on line 126

    My server has curl installed:

    curl -V
curl 7.19.7 (i386-sun-solaris2) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 libidn/1.15 libssh2/1.2.2
Protocols: tftp ftp telnet dict http file https ftps scp sftp
Features: IDN Largefile NTLM SSL libz

    PHP -v: PHP 5.2.12 (cli) (built: Feb 15 2010 15:49:19)

    Note that my site was verified a year ago, according to the Webmaster Tools link provided previously in this thread. Not sure if that matters.

    Plugin Author kbm

    (@kbm)

    It looks like the cURL can’t verify the authenticity of the certificate for Google’s HTTPS server. Your cURL installation may be using an outdated root certificate bundle:

    https://kb.ucla.edu/articles/how-do-i-update-root-certificates-in-apachephpcurl-environment

    I hope that helps!

    I decided to verify the ‘old fashioned’ way: through Google Webmaster Tools, which worked fine. This plug-in seemed like a good idea, and I’m glad it works for some folks; however, I’ve already deleted it.

    Hello I just installed the plugin, but I can not activate it because it generates a fatal error

    this is the error that gives me:”Fatal error: Call to undefined function sys_get_temp_dir() in /var/www/vhosts/sitename/httpdocs/wp-content/plugins/official-google-site-verification-plugin/external/php-client/config.php on line 53″

    Plugin Author kbm

    (@kbm)

    Hello msabirm, go ahead and try the latest version of the plugin and see if that helps. I added a bit of additional code to handle the differences between PHP 5.2.0 and PHP >5.2.1

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Returns Fatal Error on activation’ is closed to new replies.